On 20/01/2023 at 03:51, Phil Turmel wrote:

On 1/15/23 06:31, Pascal Hambourg wrote:

quoted

Create EFI partitions on both new drives. Using RAID1 with metadata 
1.0 (superblock at the end) with EFI partitions is a hack (corruption 
may happen if the UEFI firmware or anything outside Linux RAID writes 
to any of them).
Create the RAID arrays for LVM and /boot.

(...)

FWIW, except for the raid of the EFI partitions, this is what I would 
do.

I did not suggest using RAID on the EFI partitions, I warned againt it.

I recommend *not* using any raid on your EFI partitions.  Make them all 
separate, so your BIOS can tell that they are distinct filesystems (raid 
would duplicate the FS UUID/label/CRC).

AFAICS on GPT, EFI boot entries contain only the partition UUID, not the 
filesystem UUID, so duplicate filesystem UUIDs should not harm.

Use a hook in initramfs-tools to make /boot/efi[2..N] match /boot/efi 
whenever kernels get installed/modified.

Why in initramfs-tools ? The initramfs has nothing to do with the 
bootloader installation nor the EFI partition so there is no need to 
resync EFI partitions on initramfs update (unless GRUB menu entries or 
kernel and initramfs images are in the EFI partition, which is not a 
great idea IMO). IMO the right place would be a hook called after the 
system configuration manager or the GRUB package runs grub-install, if 
that exists.