Am 21.01.23 um 16:17 schrieb Pascal Hambourg:
My point was that UEFI did not change the fact that "you cannot have
everything needed for boot on a RAID", so nothing new here.
useless nitpicking isn't helpful
my point in that bugreport is that i don't want to manually call
"backup-efi.sh" after kernel updates which are happening often on Fedora
kernel-install.sh is responsible for create the initrd and so on -
when i can tell that "call /scripts/backup-efi.sh" after you are done
my ESP partitions on both drives are always in sync
What is written in the EFI partition on kernel update in Fedora ? In
Debian, the EFI partition is written only on grub package update or when
running grub-install.
and where do you think is the kernel-selection stored?
https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
[root@srv-rhsoft:~]$ ls /efi/loader/entries/
insgesamt 16K
-rwxr-xr-x 1 root root 585 2023-01-15 12:46
3871a85f73dce2f522a1a97b00001bf2-6.1.6-100.fc36.x86_64.conf
-rwxr-xr-x 1 root root 651 2023-01-19 00:30
3871a85f73dce2f522a1a97b00001bf2-6.1.7-100.fc36.x86_64.conf
and no the 1:1000000 chance that a crash happens between isn't
relevant because the whole kenel-install/initrd dance isn't atomic at
it's own
Not my point. My point is that if secondary EFI partitions are updated
only during the boot sequence then they will be out of sync at the next
boot following an update of the primary EFI partition
nobody is takling about update it during the boot sequence
* kernel-install generates initrd and boot entries
* kernel-install needs a drop-in to run a script
after it's finished
* that script can rsync /efi/ to /efi-bkp/ or whereever
you mount the ESP on the second drive
* case closed - the ESP on both drives have the same
content and it just works
for now you need to rsync manually
