Hi, I did a maintenance routine update (Leap 15.4), and on reboot, the machine did not boot the main system, but the auxiliary one. I couldn't boot the main one from its grub menu, another error. On entry, I run "efibootmgr -v" and I see that the "main-os" entry was not in the "BootOrder". So I edit it back, and reboot. I also did an update of this auxiliary system, which is running 15.2. So I get to boot the "main" system, then I reboot again, and choose in the "bios" to boot the auxiliary system to let it purge kernels. I run again "efibootmgr -v", by chance, and see that the order is, again, altered (sorry about line wrap):
Andor:~ # efibootmgr -v BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0003,0000,0001 Boot0000* main-os-secureboot HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\MAIN-OS\SHIM.EFI) Boot0001* auxiliary-secureboot HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\AUXILIARY\SHIM.EFI) Boot0003* UEFI OS HD(1,GPT,800b649f-a2e3-4dad-b2bf-b7ecc5ef11d8,0x800,0xfa000)/File(\EFI\BOOT\BOOTX64.EFI)..BO Andor:~ #
Who has put first the entry number 3? It can not boot, it contains an ancient BOOTX64.EFI. So I put it back: Andor:~ # efibootmgr --bootorder 0000,0001,0003 BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0000,0001,0003 Boot0000* main-os-secureboot Boot0001* auxiliary-secureboot Boot0003* UEFI OS Andor:~ # I will now send this email, hope to boot "main-os" and check again the boot order. -- Cheers / Saludos, Carlos E. R. (from Andor, using openSUSE Leap 15.2)