Arch Linux

jones

Member

Registered: 2013-03-14

Posts: 276

[SOLVED] efibootmgr - Cannot set Boot0000* as the primary boot option

I just set Windows as the first boot option with efibootmgr.
I then wanted to set Linux as the first option again, but I am unable to.

Here is an example of the command I used to attempt and try to set Linux as number 1 again:

15:16 john@ArchLinuxT480s [~] $  sudo efibootmgr -o Boot0000*, Boot0001*, 0018,0019,0017,001A,001C,001D,001E,0001,0023
Malformed BootOrder orderBoot0000*,
                                     ^

Other attempts included variants of the order numberings:

sudo efibootmgr -o Boot0000, Boot0001, 0018,0019, ...
sudo efibootmgr -o 0000, 0001, 0018,0019, ...
sudo efibootmgr -o 00, 01, 18,19, ...

They all produce the same error (see at the end of the first code box).

Is there something wrong with the boot number?
How can I set Linux's systemd-boot as the first option again?

The boot manager is systemd-boot.
Also, to clarify the available boot options:

15:16 john@ArchLinuxT480s [~] $ sudo efibootmgr 
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001
Boot0000* Linux Boot Manager
Boot0001* Windows Boot Manager
Boot0010  Setup
Boot0011  Boot Menu
Boot0012  Diagnostic Splash Screen
Boot0013  Lenovo Diagnostics
Boot0014  Startup Interrupt Menu
Boot0015  Rescue and Recovery
Boot0016  MEBx Hot Key
Boot0017* USB CD
Boot0018* USB FDD
Boot0019* NVMe0
Boot001A* ATA HDD0
Boot001B* USB HDD
Boot001C* PCI LAN
Boot001D  Other CD
Boot001E  Other HDD
Boot001F* USBR BOOT CDROM
Boot0020* USBR BOOT Floppy
Boot0021* ATA HDD
Boot0022* ATAPI CD
Boot0023* PCI LAN

And some verbose output for the first 5 entries:

efibootmgr --verbose
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001
Boot0000* Linux Boot Manager	HD(1,GPT,922e28c3-64b4-4bad-986a-0f8a67bbf749,0x800,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0001* Windows Boot Manager	HD(1,GPT,922e28c3-64b4-4bad-986a-0f8a67bbf749,0x800,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}..._................
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)

Last edited by jones (2021-07-28 13:46:02)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,310

Re: [SOLVED] efibootmgr - Cannot set Boot0000* as the primary boot option

You shouldn't add spaces between the commas, and you can ommit superfluous fluff (excess 0 shouldn't matter but including the "Boot" text is definitely wrong):

efibootmgr -o 0,1

Last edited by V1del (2021-07-28 13:42:49)

jones

Member

Registered: 2013-03-14

Posts: 276

Re: [SOLVED] efibootmgr - Cannot set Boot0000* as the primary boot option

Thank you, V1del, that solved this thread.

The command that worked was:

efibootmgr -o 0000,0001,0018,0019,0017,001A,001C,001D,001E,0001,0023

Note: besides spaces, stars also do not work and have to be omitted. (The command did not work when I included the stars.)

Last edited by jones (2021-07-28 13:46:22)