| 1 |
On Wed, 11 Mar 2015 07:45:54 +0100, Stefan G. Weichinger wrote: |
| 2 |
|
| 3 |
> yesterday I received a shiny new server for a client. |
| 4 |
> |
| 5 |
> It brings 4 x 1 TB SATA disks, is capable of UEFI and I started setting |
| 6 |
> it up. |
| 7 |
> |
| 8 |
> GPT partitioning, small partition(s) for the ESP, some swap, and bigger |
| 9 |
> partitions of type fd=raid for creating 2 mdadm-raids (rootfs and data) |
| 10 |
> with level 6. |
| 11 |
> |
| 12 |
> ok so far. |
| 13 |
> |
| 14 |
> Then I spent some hours fiddling with grub2, gummiboot et al to get that |
| 15 |
> box booting up fine. dracut doesn't assemble the rootfs-raid etc etc ... |
| 16 |
> -> fun |
| 17 |
|
| 18 |
I found this with a LUKS root filesystem, dracut doesn't automatically |
| 19 |
detect such devices any more, so speed up the boot. You need to specify |
| 20 |
rd.auto or rd.mdraid to force it. |
| 21 |
|
| 22 |
> even if I manage to have it booting via UEFI from /dev/sda1 or so ... I |
| 23 |
> still have this single point of failure as the vfat-partitioned ESP is |
| 24 |
> on one physical disk only. |
| 25 |
> |
| 26 |
> I would like to set it up in a way that it boots even when the /dev/sda |
| 27 |
> dies ... |
| 28 |
|
| 29 |
I generally set up boot on a RAID1 across all disks. You can still |
| 30 |
access individual disks in a RAID1 array, so you can set your computer |
| 31 |
to boot from sda1 then sda2 etc but mount /boot on the array, so all |
| 32 |
updates are pushed to all four disks. |
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Neil Bothwick |
| 37 |
|
| 38 |
I distinctly remember forgetting that. |
Archives