Skip to content

fix: clarify partition labels #3855

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

Merged
merged 2 commits into from
Oct 18, 2024
Merged

fix: clarify partition labels #3855

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5b4de59
fix: clarify partition labels
pierreozoux Oct 18, 2024
0d47f80
Update bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx
bene2k1 Oct 18, 2024
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
4 changes: 2 additions & 2 deletions bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ Below is an example of how to define a partitioning schema with RAID and NVMe di

- Disks:
- Each disk is specified with its device path (e.g., `/dev/nvme0n1` or `/dev/nvme1n1`).
- Partitions are defined with labels like `swap`, `boot`, `root`, `data`, and an optional `uefi` partition for systems using UEFI.
- Partitions are defined with labels. The default value is `unknown_partition_label`, and possible values are: `uefi`, `legacy`, `root`, `boot`, `swap`, `data`, `home`, `raid`. Refer to the [API documentation](https://www.scaleway.com/en/developers/api/elastic-metal/#path-servers-install-an-elastic-metal-server) for full details.
- Each partition has a `number` and `size` in bytes.

- RAID (Optional):
Expand Down Expand Up @@ -224,4 +224,4 @@ If you prefer a simpler configuration without RAID or ZFS, you can remove the `r
"lvm": null
}
}
```
```