On 13/09/2022 at 15:02, Reindl Harald wrote:
Am 13.09.22 um 14:47 schrieb Pascal Hambourg:
However you are right that you can get rid of the current /boot array;
I don't see the need for a separate /boot, its contents could be
included in the root filesystem.
and the initrd lives where?
chicken / egg
In the /boot directory, beside the kernel image. What's different with
the initrd ? I don't see any chicken & egg problem. If GRUB can boot the
kernel image and initrd from a separate /boot RAID array, it can do the
same from a root RAID array.
since finally the new machines in the next step only support UEFI and
the uefi-system partition can't live on a RAID it would end there
over time anyways
Software is not natively supported by EFI boot but there are a few
^^^
Oops ! I meant "software RAID".
tricks to set up a redundant EFI boot: create independent EFI
partitions on each disk, or create a RAID 1 array with metadata 1.0
(at the end of the partition) so that the UEFI firmware can see each
RAID partition as a normal EFI partition with a FAT filesystem.
sounds all not appealing
Yes, but I know no cleaner way to achieve UEFI boot redundancy, which is
desirable.
