Mercurial > hg > Blog
annotate content/Linux/software-raid-setup.md @ 112:cf31bf5fce72 default tip
Author of the blog post as mail header for efficient spam filtering
| author | Dirk Olmes <dirk.olmes@codedo.de> |
|---|---|
| date | Tue, 06 Sep 2022 07:04:11 +0200 |
| parents | 1d9382b0329b |
| children |
| rev | line source |
|---|---|
| 85 | 1 Title: Setting up a software RAID1 |
| 2 Date: 2017-07-12 | |
| 3 Lang: en | |
| 4 Tags: Gentoo | |
| 5 | |
| 6 I'm helping a friend to set up a machine with [Gentoo](http://www.gentoo.org). This will be a machine to host production applications and it is equipped with 2 identical hard drives. I will set up a [software RAID 1](https://raid.wiki.kernel.org). This has been a life saver on a similar machine before where one of the drives failed and we had no data loss and only minimal downtime during which the drive was replaced. | |
| 7 | |
| 8 One goal of the new setup is to remain bootable even if one of the drives fails. I had trouble accomplishing this in earlier setups so this time I tested the process locally on a virtual machine before setting up the real iron. | |
| 9 | |
| 87 | 10 The first step of the setup is partitioning the drives. The [handbook](https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks) suggests adding a small partition at the beginning of the drive to enable booting from a gpt partitioned drive. The `/boot` partition will be formatted using [ext4](https://en.wikipedia.org/wiki/Ext4) because the filesystem will remain bootable even if one of the drives is missing. The rest of the disk will be formatted using [xfs](https://en.wikipedia.org/wiki/XFS). To recap the layout: |
| 85 | 11 |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
12 :::shell |
| 85 | 13 Number Start End Size File system Name Flags |
| 14 1 1.00MiB 3.00MiB 2.00MiB grub bios_grub | |
| 15 2 3.00MiB 95.0MiB 92.0MiB boot | |
| 16 3 95.0MiB 8191MiB 8096MiB rootfs raid | |
| 17 | |
| 18 The second drive is partitioned exactly the same. | |
| 19 | |
| 20 Now let's create a RAID 1 for the boot partition: | |
| 21 | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
22 :::shell |
| 85 | 23 mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdb2 /dev/sdc2 |
| 24 | |
| 25 and for the rootfs: | |
| 26 | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
27 :::shell |
| 85 | 28 mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdb3 /dev/sdc3 |
| 29 | |
| 30 To maintain the RAID device numbering even after reboot, the RAID config has to be saved. This will be done by | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
31 |
|
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
32 :::shell |
| 85 | 33 mdadm --detail --scan >> /etc/mdadm.conf |
| 34 | |
| 35 Then create an ext4 filesystem on `/dev/md0` and an xfs filesystem on `/dev/md1`. Nothing noteworthy here. | |
| 36 | |
| 37 The observant reader will have noticed from the device names above that I'm testing my installation from a running system on `/dev/sda`. To save the hassle of going through the entire stage3 setup process I'm simply copying the running system to the newly created RAID filesystems. | |
| 38 | |
| 39 After chrooting into the new system some changes have to be made to the [genkernel](https://wiki.gentoo.org/wiki/Genkernel) config in order to produce a RAID enabled initramfs. In `/etc/genkernel.conf` set | |
| 40 | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
41 :::shell |
| 85 | 42 MDADM="yes" |
| 43 MDADM_CONFIG="/etc/mdadm.conf" | |
| 44 | |
| 45 Now we're set to build the kernel. | |
| 46 | |
| 47 While it's compiling, edit `/etc/default/grub` (I'm of course using [grub2](https://www.gnu.org/software/grub/manual/grub.html) for booting) and add | |
| 48 | |
|
98
1d9382b0329b
Specify the syntax on markdown blocks to avoid broken output that has class=err
Dirk Olmes <dirk@xanthippe.ping.de>
parents:
87
diff
changeset
|
49 :::shell |
| 85 | 50 GRUB_CMDLINE_LINUX="domdadm" |
| 51 | |
| 52 Setup grub on both devices individually using `grub-install /dev/sdb` and `grub-install /dev/sdc`. | |
| 53 | |
| 54 After the kernel has finished compiling, generate the proper grub config using `grub-mkconfig -o /boot/grub/grub.cfg`. | |
| 55 | |
| 56 Before rebooting the `fstab` has to be set up correctly. I prefer to use UUIDs for filesystems instead of device names - this is a bit more fault tolerant in case device numbering is mixed up. It was a main challenge to find an unambiguous UUID for the both RAID filesystems. There are a number of places to get a UUID from: `mdadm --detail`, `blkid`, `tune2fs -l`, `xfs_admin -u` and I'm sure I forgot more. The helpful guys at the [gentoo IRC channel](https://www.gentoo.org/get-involved/irc-channels/) pointed me in the right direction. Use `lsblk -f /dev/md0` to find a UUID that uniquely identifies the RAID and check using `findfs UUID=<uuid>`. | |
| 57 | |
| 58 After updating the `fstab` the system is ready for a first boot into the RAID setup. | |
| 59 | |
| 60 I tested failing drives by simply removing the first (or the second) drive from the virtual machine. The whole setup still boots off either drive. |