Boot order repeating?

Johng · 12-26-2023, 04:25 PM

I have a system with two SSD (sda and sdb) and two HDD.
The main Kubuntu OS is on sdb2, with a couple of other os on the SSDs.
When booting, the system seems to double the booting sequence.
If I issue: sudo efibootmgr -v

Quote:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0005,0002,0001,0006,0007
Boot0000* ubuntu HD(6,GPT,)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* opensuse HD(1,GPT,)/File(\EFI\opensuse\grubx64.efi)
Boot0002* UEFI OS HD(6,GPT,)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0005* UEFI: ADATA SP900 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,65535,0)/HD(3,GPT,)AMBO
Boot0006* ubuntu HD(1,GPT,)/File(\EFI\Ubuntu\grubx64.efi)
Boot0007* ubuntu HD(6,GPT,)/File(\EFI\Ubuntu\grubx64.efi)

I have erased UUID from above for clarity.

Are these dregs from previous installs, and could I use efibootmgr to remove Boots 0000, 0001, 0002, 0005, and 0007?

Or is there another way to tidy up boot order?

syg00 · 12-26-2023, 06:58 PM

Yes, yes and no (well, you could reset the firmware, but that's a bit drastic).

Johng · 12-26-2023, 07:11 PM

If do, is it only affecting whether I can boot or not. I could resort to using a boot disc?

mrmazda · 12-27-2023, 12:21 PM

Quote:

Originally Posted by Johng

Code:

BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0000,0005,0002,0001,0006,0007
Boot0000* ubuntu HD(6,GPT,)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* opensuse HD(1,GPT,)/File(\EFI\opensuse\grubx64.efi)
Boot0002* UEFI OS HD(6,GPT,)/File(\EFI\BOOT\BOOTX64.EFI)
Boot0005* UEFI: ADATA SP900 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,65535,0)/HD(3,GPT,)AMBO
Boot0006* ubuntu HD(1,GPT,)/File(\EFI\Ubuntu\grubx64.efi)
Boot0007* ubuntu HD(6,GPT,)/File(\EFI\Ubuntu\grubx64.efi)

I see no duplicates.

syg00 · 12-27-2023, 11:15 PM

Quote:

Originally Posted by Johng

If do, is it only affecting whether I can boot or not. I could resort to using a boot disc?

Yes - if I understand the question correctly. The efibootmgr simply (!!) removes the entry from the NVRAM on the motherboard, the data for the distro in question is not affected (except it can no longer be directly booted).