Guide update - How to configure and rebuild software RAID #8252
Conversation
Jessica41
added
Do not merge yet
|
|
||
| The default RAID level for OVHcloud server installations is RAID 1, which doubles the space taken up by your data, effectively halving the useable disk space. | ||
|
|
||
| **This guide explains how to manage and rebuild software RAID after a disk replacement on your server in BIOS mode** |
There was a problem hiding this comment.
| **This guide explains how to manage and rebuild software RAID after a disk replacement on your server in BIOS mode** | |
| **This guide explains how to manage and rebuild software RAID after a disk replacement on your server in legacy boot (BIOS) mode** |
Internally, we refer to the boot mode as UEFI or legacy, not BIOS. I think BIOS could be misleading as the UEFI setup menu is still sometimes called "BIOS" or "BIOS setup".
|
|
||
| For **GPT** partitions, line 6 will display: `Disklabel type: gpt`. | ||
|
|
||
| For **MBR** partitions, line 6 will display: `Disklabel type: dos`. |
There was a problem hiding this comment.
I would not document MBR at all. We've entirely abandoned it for new installations. Only 3% of the installations done in 2024 were in this case and starting from July 2025 it's 0%.
|
|
||
| For **MBR** partitions, line 6 will display: `Disklabel type: dos`. | ||
|
|
||
| Still going by the results of `fdisk -l`, we can see that `/dev/md2` consists of 888.8GB and `/dev/md4` contains 973.5GB. If we were to run the mount command we can also find out the layout of the disk. |
There was a problem hiding this comment.
You should mention that it's only the case when booted to disk, not in rescue.
Also, mount's output is pretty verbose. I'd just keep lsblk's
| To check whether a server runs on BIOS mode or BIOS mode, run the following command: | ||
|
|
||
| ```sh | ||
| [user@server_ip ~]# [ -d /sys/firmware/efi ] && echo BIOS || echo BIOS |
There was a problem hiding this comment.
That should be moved at the beginning of the doc when you mention legacy/UEFI.
| Alternatively, the `lsblk` command offers a different view of the partitions: | ||
|
|
||
| ```sh | ||
| lsblk |
There was a problem hiding this comment.
Why no prompt here? Some other commands have [user@server_ip ~]#
| swap : ignored | ||
| ``` | ||
|
|
||
| We enable the swap partition: |
There was a problem hiding this comment.
| We enable the swap partition: | |
| We activate the swap partition: |
| swap : ignored | ||
| ``` | ||
|
|
||
| We enable the swap partition: |
There was a problem hiding this comment.
| We enable the swap partition: | |
| We activate the swap partition: |
| swapon /dev/nvme1n1p4 | ||
| ``` | ||
|
|
||
| We exit the Chroot environment with `Exit` and unmount all the disks: |
There was a problem hiding this comment.
| We exit the Chroot environment with `Exit` and unmount all the disks: | |
| We exit the chroot environment with `Exit` and unmount all the disks: |
| swapon /dev/sdb4 | ||
| ``` | ||
|
|
||
| We exit the Chroot environment with `exit` and unmount all the disks: |
There was a problem hiding this comment.
| We exit the Chroot environment with `exit` and unmount all the disks: | |
| We exit the chroot environment with `exit` and unmount all the disks: |
| mount /dev/nvme0n1p1 new | ||
| ``` | ||
|
|
||
| Next, we copy the files from the `old` folder to the `new` folder. Depending on your operating system, you will have a similar output. Here we are using debian: |
There was a problem hiding this comment.
I see in the next subsection where you perform the changes from the OS itself and not the rescue, you run the sync script. Surely it'd work in rescue too, did you try?
There was a problem hiding this comment.
@sbraz I did perform all these steps in rescue mode, I just forgot to add the prompt for rescue mode. Doing that in the next update. Thanks!
What type of Pull Request is this?
Description
Updating the guide to include the EFI partition
Mandatory information
This Pull Request shouldn't be merged before: Do not have a date.
This Pull Request content should be replicated for the US OVHcloud documentation : YES