BYOI and multiple disks: unused disks may prevent boot #8837
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the warning about RAID, tell about unitialized unused disks potentially preventing boot (see https://community.ovhcloud.com/community/fr/freebsd-en-cloudinit-marchait-en-mars-ne-marche-plus-en-decembre?id=community_question&sys_id=da84c34985353654476bb1da92914b4f for details) Reorder the RAID warning starting with the (short) hardware RAID section, and detail the complex case of soft RAID at the end
sbraz
reviewed
Dec 17, 2025
Member
sbraz
left a comment
sbraz
left a comment
There was a problem hiding this comment.
Thanks for the contribution, I'll report back as soon as I've been able to perform more tests on old legacy boot boards like yours.
| > | ||
| > - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk. | ||
| > - If you stay with BYOI, the image will only get deployed to the first disk, other disks will be left unmodified.\ | ||
| > However some motherboards will not boot with uninitialized disks: if your server does not respond to pings, please verify that your unused disks are minimally partitioned.\ |
Member
There was a problem hiding this comment.
I'd like to perform more tests before adding that sentence to the doc. I'll try to do it this week if I can.
| > - Bring Your Own Image (BYOI) does not support software RAID configuration at install-time, but you can use the service [Bring Your Own Linux (BYOLinux)](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux) for that. Choose the custom image method that fits your needs: [Bring Your Own Image (BYOI) / Bring Your Own Linux (BYOLinux), a comparison sheet](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux). | ||
| > | ||
| > - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk. | ||
| > - If you stay with BYOI, the image will only get deployed to the first disk, other disks will be left unmodified.\ |
Member
There was a problem hiding this comment.
That was definitely missing from the doc, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of Pull Request is this?
Description
As shown in a Community discussion with @sbraz about a BYOI install not working anymore,
the RAID-ready secondary disks that are left unmodified in a BYOI installation may prevent booting, with no hint on what is stuck (on a non-KVM machine).
This PR adds the minimal info to help detect and solve this problem.
Hesitations
<sup><sub></sub></sup>) were not as clean as one would hope: do OVH Docs have a way to reduce some paragraph's text size?Mandatory information
The translations in this Pull Request have been done using:
OVHcloud integrated translation LLM
Systran
Other tool (my hands and brain)
This Pull Request didn't require any translation.
This Pull Request can be merged as soon as possible.