Merge pull request #7932 from ovh/fix/PUBM-42758

fix(bare_metal_cloud/partitioning_ovh): update known errors

Author: Y0Coss

pages/bare_metal_cloud/dedicated_servers/partitioning_ovh/guide.de-de.md

@@ -1,7 +1,7 @@
 ---
 title: 'OVHcloud API and Storage (EN)'
 excerpt: 'Find out what the OVHcloud API provides in order to customize the disks, hardware/software RAID and partitioning configuration during the server OS reinstallation'
-updated: 2025-02-25
+updated: 2025-06-04
 ---
 
 ## Objective
@@ -538,16 +538,14 @@ The following table gives an overview of well known customer errors and how to f
 
 |Error message|Details|Solution(s)|
 |---|---|---|
-|Some Linux distributions such as RHEL family OSes don't support those mountpoints / mountpoint reserved/managed by OVHcloud (`list forbidden mountpoints`). Please remove those mountpoints and restart an installation|- You have chosen `/boot/efi` as mountpoint. OVHcloud will create this partition automatically for you if your server needs one<br />- You have chosen a mountpoint that is symlinked on some operating systems. See [Filesystem Hierarchy Standard](https://refspecs.linuxfoundation.org/fhs.shtml) for more details.|- Choose another mountpoint for the partition or remove this partition from your partitioning layout|
-|Partition of type `t` with mountpoint `m` cannot fill the disk.|- You have chosen the `swap` partition to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)), we disallow this to avoid creating unnecessarily large `swap` partitions|- Set a fixed size for the `swap` partition|
-|Missing `/` partition. Please add a `/` partition in your partition scheme!|- Any Linux-based OS needs at least a `/` partition|- Add a `/` partition in your partitioning layout|
-|`message`. Please adjust partitions so that the `p` partition fits on `n` disk(s)|- You have chosen a partition with a RAID that requires a number of disks that your server can provide, but some disks are already full because of other partitions and/or this current partition|- If it is not already set on another partition, set the partition size to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api))<br />- Reduce the size of this partition so that it fits the disks<br />- Reduce the size of other partitions so that this partition fits the disks|
-|Error with MBR partition table: Partition `p` is larger than 2TiB and this server does not support GPT|- You have defined a partition with a size that exceeds 2TiB and you are trying to apply such partitioning to a server that doesn't support GPT|- Reduce the partition to a size less than 2TiB<br />- Apply this partitioning to another similar server that supports GPT|
-|Error with MBR partition table: partition `p` cannot end after 2 TiB (`interval stop`) and this server does not support GPT! OVHcloud also needs to add a `cloud-init size` cloud-init partition at the very end of the disk. Therefore all customer partitions must end before (2TiB - `cloud-init size`).|- We need to add a config-drive partition at the end of 1 disk on your dedicated server. The last partition of your partitioning will end after the 2TiB position on disk. So appending a config-drive partition after the last partition will start after 2TiB position on disk and you are trying to apply such partitioning to a server that doesn't support GPT|- Reduce the partition `p` size (or any other partition) so that the total sum of all partitions size is less than 2TiB<br />- Do not define a partition that fills the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)) for servers with disks bigger than 2TiB that don't support GPT|
-|`/boot` (or `/` if no `/boot` defined) partition cannot be larger than 2097151 MiB on this hardware|- GRUB partition cannot be larger than 2 TiB with this hardware RAID controller|- Create a separate `/boot` partition with a size less than 2TiB (1GiB should be enough)|
-|`/boot` (or `/` if no `/boot` defined) partition type cannot be `XFS`|- GRUB partition doesn't support `XFS` filesystem type on this Operating System. This is the case for most of debian-like OSes (debian, proxmox, ubuntu)|- Create a separate `/boot` partition with filesystem other than `XFS`<br />- Don't create a separate `/boot` partition but choose a filesystem other than `XFS` for the `/` partition|
-|`ZFS` partition already exists with zpool name `n`. Either choose another name for the `m` partition or set the same RAID level for all partitions within zpool `n`|Assigning multiple `ZFS` partitions to the same zpool name is possible: it means each dataset will be part of the same zpool. This is possible only if all the datasets (therefore the partitions defined via the API) have the same RAID level|- Set the same RAID level as on the existing `ZFS` partition which will be part of the same zpool<br />- Choose another zpool name: this partition will not be part of the same zpool<br />- Don't provide any zpool name: we will assign a default zpool name and this partition will not be part of the same zpool|
-|`Debian` does not provide a precompiled `ZFS` module and this server does not have enough memory to compile it. Please use a different file system|We always try to find the best balance between integration in OVHcloud ecosystem, hardware compatibility and reduced OS image size while providing an image that is as similar as possible as the official cloud-ready image provided by the software editor. `ZFS` module is not natively provided by the software editor, we don't want to make the image heavier for customer not needing `ZFS` and we want to offer a `ZFS`-ready OS with configured `ZFS` partitioning for customers who want it. Therefore `ZFS` module is compiled and installed during the OS reinstallation only for customers who ask for it. Since compilation requires memory in addition to that already used to run the rescue OS in memory, we have set the threshold at 8GiB to guarantee smooth operation and customer experience|- Remove all `ZFS` partitions or change their filesystems to something different than `ZFS`<br />- Choose another OS that natively supports `ZFS` filesystem such as Proxmox<br />- Use a server with 8GiB memory or more|
+|Partition of type `t` with mountpoint `m` cannot fill the disk.|You have chosen the `swap` partition to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)), we disallow this to avoid creating unnecessarily large `swap` partitions.|- Set a fixed size for the `swap` partition|
+|`message`. Please adjust partitions so that the `p` partition fits on `n` disk(s)|You have chosen a partition with a RAID that requires a number of disks that your server can provide, but some disks are already full because of other partitions and/or this current partition.|- If it is not already set on another partition, set the partition size to fill the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api))<br />- Reduce the size of this partition so that it fits the disks<br />- Reduce the size of other partitions so that this partition fits the disks|
+|Error with MBR partition table: Partition `p` is larger than 2TiB and this server does not support GPT|You have defined a partition with a size that exceeds 2TiB and you are trying to apply such partitioning to a server that doesn't support GPT.|- Reduce the partition to a size less than 2TiB<br />- Apply this partitioning to another similar server that supports GPT|
+|Error with MBR partition table: partition `p` cannot end after 2 TiB (`interval stop`) and this server does not support GPT! OVHcloud also needs to add a `cloud-init size` cloud-init partition at the very end of the disk. Therefore all customer partitions must end before (2TiB - `cloud-init size`).|We need to add a config-drive partition at the end of 1 disk on your dedicated server. The last partition of your partitioning will end after the 2TiB position on disk. So appending a config-drive partition after the last partition will start after 2TiB position on disk and you are trying to apply such partitioning to a server that doesn't support GPT.|- Reduce the partition `p` size (or any other partition) so that the total sum of all partitions size is less than 2TiB<br />- Do not define a partition that fills the disk (or partition with size 0 when defined within the [OVHcloud API](/links/api)) for servers with disks bigger than 2TiB that don't support GPT|
+|`/boot` (or `/` if no `/boot` defined) partition cannot be larger than 2097151 MiB on this hardware|GRUB partition cannot be larger than 2 TiB with this hardware RAID controller.|- Create a separate `/boot` partition with a size less than 2TiB (1GiB should be enough)|
+|`/boot` (or `/` if no `/boot` defined) partition type cannot be `XFS`|GRUB partition doesn't support `XFS` filesystem type on this Operating System. This is the case for most of Debian-like OSes (Debian, Proxmox, Ubuntu).|- Create a separate `/boot` partition with filesystem other than `XFS`<br />- Don't create a separate `/boot` partition but choose a filesystem other than `XFS` for the `/` partition|
+|`Debian` does not provide a precompiled `ZFS` module and this server does not have enough memory to compile it (8 GiB minimum required). Please use a different file system.|We always try to find the best balance between integration in the OVHcloud ecosystem, hardware compatibility and reduced OS image size while providing an image that is as similar as possible to the official cloud-ready image provided by the software publisher. The `ZFS` module is not contained in the official image. We don't want to make the image larger for customers not needing `ZFS` and we want to offer a `ZFS`-ready OS with configured `ZFS` partitioning for customers who want it. Therefore the `ZFS` module is compiled and installed during the OS reinstallation only for customers who require it. Since compilation requires memory in addition to that already used to run the rescue OS in memory, we have set the threshold at 8 GiB to guarantee smooth operation and customer experience.|- Remove all `ZFS` partitions or change their filesystems to something different than `ZFS`<br />- Choose another OS that natively supports `ZFS` filesystems such as Ubuntu or Proxmox<br />- Use a server with 8 GiB memory or more|
+|This operating system doesn't support `md` metadata version 1.2 for the `/` partition. Fallback to `md` version 0.90 is not possible because the `/` partition requires `x` MiB on every disk, exceeding the supported maximum of 4 TiB.|You have configured a `/` partition on top of a software RAID with an operating system that only supports `md` metadata version 0.9 for the `/` partition. Unfortunately this version of `md` metadata doesn't work when the size used per disk is larger than 4 TiB.|- Reduce the size of this partition so that it doesn't use more than 4 TiB per disk<br />- Disable software raid, by restricting OS installation to 1 single disk<br />- Choose another operating system|
 
 #### Input customer auto-fixing