Skip to content

BYOI and multiple disks: unused disks may prevent boot #8837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
outtersg wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

BYOI and multiple disks: unused disks may prevent boot #8837

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-asia.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
Copy link
Member

@sbraz sbraz Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was definitely missing from the doc, thanks!

> 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.\
Copy link
Member

@sbraz sbraz Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member

@sbraz sbraz Jan 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @outtersg, I'm sorry I haven't had time to look into this yet. I haven't forgotten the PR or the issue you raised. I will look into it as soon as possible.

Copy link
Author

@outtersg outtersg Jan 25, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the following up!

Meanwhile I wreaked the machine twice, trying to make the second disk a gmirror of the first, and the third a rescue OS, in theory all 3 bootable: this didn't worked well, and I ended up with a (now stable) machine with only the data partition of disk1 gmirrored, and avoiding an ESP on disk3 (that seemed to prevent booting too).

The good news is I became somewhat "fluent" in using parted / gpart to quickly recover the machine (with the help of a customized MFSBSD image, HTTPS-hosted on my other Kimsufi and thus iPXE-reachable, that served as a FreeBSD rescue OS).
So even if the diagnosis is still difficult, at least the medication works well.

> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-au.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ca.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-gb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-ie.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-sg.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.en-us.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ There are some technical limitations linked to the use of physical products such
> [!warning]
> **About RAID:**
>
> - Hardware RAID is supported, if your server supports it, because it is configured before the image is deployed on disk.
>
> - 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.\
> 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.\
> For example, starting your server in rescue mode:\
> `parted --list` should return, on unused disks (`/dev/sdb`, `/dev/sdc`, etc.), at least a GPT table containing one partition (even untyped and empty).\
> Otherwise:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Deployment methods:**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-ca.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ Certaines limites techniques sont liées à l’utilisation de produits physique
> [!warning]
> **À propos du RAID :**
>
> - Le RAID matériel est pris en charge, si votre serveur le supporte, car il est configuré avant le déploiement de l'image sur le disque.
>
> - Bring Your Own Image (BYOI) ne prend pas en charge la configuration RAID logicielle au moment de l'installation, mais vous pouvez utiliser le service [Bring Your Own Linux (BYOLinux)](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux) pour le faire. Choisissez le type d'installation personnalisée le plus adapté : [Comparaison entre Bring Your Own Image (BYOI) et Bring Your Own Linux (BYOLinux)](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux).
>
> - Le RAID matériel est pris en charge, si votre serveur le supporte, car il est configuré avant le déploiement de l'image sur le disque.
> - Si vous restez sur une BYOI, l'image ne sera déployée que sur le premier disque, les autres disques seront laissés en l'état.\
> Cependant certaines cartes mères ne démarrent pas avec des disques non initialisés: si votre serveur ne répond pas au ping après installation, vérifiez le partitionnement des disques inutilisés.\
> Par exemple depuis la rescue Debian:\
> `parted --list` doit renvoyer pour les disques inutilisés (`/dev/sdb`, `/dev/sdc`, etc.) a minima une table GPT comportant une partition (même non typée, et vide)\
> Dans le cas contraire:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Méthodes de déploiement :**
Expand Down
10 changes: 9 additions & 1 deletion pages/bare_metal_cloud/dedicated_servers/bring-your-own-image/guide.fr-fr.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,17 @@ Certaines limites techniques sont liées à l’utilisation de produits physique
> [!warning]
> **À propos du RAID :**
>
> - Le RAID matériel est pris en charge, si votre serveur le supporte, car il est configuré avant le déploiement de l'image sur le disque.
>
> - Bring Your Own Image (BYOI) ne prend pas en charge la configuration RAID logicielle au moment de l'installation, mais vous pouvez utiliser le service [Bring Your Own Linux (BYOLinux)](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-linux) pour le faire. Choisissez le type d'installation personnalisée le plus adapté : [Comparaison entre Bring Your Own Image (BYOI) et Bring Your Own Linux (BYOLinux)](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image-versus-bring-your-own-linux).
>
> - Le RAID matériel est pris en charge, si votre serveur le supporte, car il est configuré avant le déploiement de l'image sur le disque.
> - Si vous restez sur une BYOI, l'image ne sera déployée que sur le premier disque, les autres disques seront laissés en l'état.\
> Cependant certaines cartes mères ne démarrent pas avec des disques non initialisés: si votre serveur ne répond pas au ping après installation, vérifiez le partitionnement des disques inutilisés.\
> Par exemple depuis la rescue Debian:\
> `parted --list` doit renvoyer pour les disques inutilisés (`/dev/sdb`, `/dev/sdc`, etc.) a minima une table GPT comportant une partition (même non typée, et vide)\
> Dans le cas contraire:\
> `parted /dev/sdb mkt gpt`\
> `parted /dev/sdb mkpart bios_grub 1049k 2097k`
>

**Méthodes de déploiement :**
Expand Down