[SOLVED] Why is BootCurrent: 0001 despite 0003 the default?

da99 · 2016-05-01 03:46:45

The Arch x64 install that I have is running smoothly.
However, I don't understand the following output:

Boot0001 (Linux Boot Manager) is always the "BootCurrent". Even though Boot0003 (arch HD) is the first
in the BootOrder. Does does mean there was an error in "GRUBX64.efi" and it loaded Boot0001/SYSTEMD-BOOTX64.EFI as the backup?
(I'm using systemd-boot.)

#> efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0003,0001,000B,0005,000D,000C,0002
Boot0001* Linux Boot Manager    HD(1,GPT,e0.... \SYSTEMD-BOOTX64.EFI)
Boot0002* UEFI: Built-in EFI Shell  VenMedia(5023...012)..BO
Boot0003* arch HD(1,GPT,e07236...921eed1e,0x800,0x100000)/File(\EFI\ARCH\GRUBX64.EFI)
Boot0005* Hard Drive    BBS(HD,,0x0)......BO
Boot000B* UEFI OS   HD(1,GPT,e07236...000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot000C* Unknown Device    BBS(11,,0x0)..GO..NO........y.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. 
Boot000D* UEFI: Generic STORAGE DEVICE 0272 PciRoot(0x...

Last edited by da99 (2016-05-02 21:04:59)

Lone_Wolf · 2016-05-01 21:03:23

wiki on systemd-boot wrote:

It will copy the systemd-boot binary to your EFI System Partition (esp/EFI/systemd/systemd-bootx64.efi and esp/EFI/Boot/BOOTX64.EFI - both of which are identical - on x64 systems) and add systemd-boot itself as the default EFI application (default boot entry) loaded by the EFI Boot Manager.

Maybe "default boot entry" is not equal to "first entry in bootorder list" ?

You could try manually selecting "arch HD" entry to verify if that changes BootCurrent value.

You're probably better off by checking https://www.happyassassin.net/2014/01/2 … work-then/

Last edited by Lone_Wolf (2016-05-01 21:07:08)

Arch Linux

#1 2016-05-01 03:46:45

[SOLVED] Why is BootCurrent: 0001 despite 0003 the default?

#2 2016-05-01 21:03:23

Re: [SOLVED] Why is BootCurrent: 0001 despite 0003 the default?

Board footer