Re: Transferring an existing system from non-RAID disks to RAID1 disks in the same computer
From: Pascal Hambourg <hidden>
Date: 2023-01-21 20:04:24
On 21/01/2023 at 19:57, Reindl Harald wrote:
Am 21.01.23 um 19:52 schrieb Pascal Hambourg:quoted
On 21/01/2023 at 17:24, Reindl Harald wrote:quoted
Am 21.01.23 um 16:17 schrieb Pascal Hambourg:quoted
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 helpfulBarking up the wrong tree isn't useful either. EFI is not the culprit.but the root cause - cause and effect
No, EFI is not the root cause either. The root cause is carelessly storing stuff in the bootloader area as if it was part of the standard Linux filesystem. Guess what ? It is not. Even though the EFI partition contains a filesystem, it is not a part of the standard Linux filesystem and requires special consideration, just like the MBR, the post-MBR gap or the BIOS boot partition. You can blame Fedora for this. I blame Debian for this. I praise Ubuntu for managing multiple EFI partitions at last, and I do not often praise Ubuntu, believe me.
quoted
I did not find any information about where the kernel-selection is stored in this page.in /efi/loader/entries/
Weird, the wiki mentions /boot/loader/entries/.
quoted
Wol wrote:quoted
quick rsync in the initramfs or boot sequence to sync EFIs, then that's probably the best place.yeah, initramfs is fine because that's generated due kernel-install
Aren't you confusing the initramfs execution and generation ?
ok, my mistake: initramfs generation is fine because at that point everything is already there, the initrd is locate don the EFI and when that's finished is the point to sync a backup-ESP
But that's not enough, because other parts of the system may write to the EFI partition, so it does not completely solve the issue.