Systemd-boot is not present as a choice in BIOS

Hello,
I use dual boot on my laptop - EndeavourOS and Windows 10. Once after using the windows I restarted the computer (systemd-boot was on top in BIOS boot priorities) but it wasn’t there and it went direcly to the next thing in the row. Maybe I pressed something by accident or it could be fault of the windows, which I updated shortly before this. Honestly I don’t know and I am sorry for that.

I was able to boot into EOS through the option “Boot from EFI file” (or something similar sounding) in BIOS.

I also do have a live installation media by hand so it is not an issue from my side to use that.

Here are outputs from lsblk and efibootmgr if that is helpful:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0     4K  1 loop /var/lib/snapd/snap/bare/5
                                      /var/lib/snapd/snap/bare/5
loop1         7:1    0  63,4M  1 loop /var/lib/snapd/snap/core20/1974
                                      /var/lib/snapd/snap/core20/1974
loop2         7:2    0  63,5M  1 loop /var/lib/snapd/snap/core20/2015
                                      /var/lib/snapd/snap/core20/2015
loop3         7:3    0 349,7M  1 loop /var/lib/snapd/snap/gnome-3-38-2004/140
                                      /var/lib/snapd/snap/gnome-3-38-2004/140
loop4         7:4    0 349,7M  1 loop /var/lib/snapd/snap/gnome-3-38-2004/143
                                      /var/lib/snapd/snap/gnome-3-38-2004/143
loop5         7:5    0  91,7M  1 loop /var/lib/snapd/snap/gtk-common-themes/1535
                                      /var/lib/snapd/snap/gtk-common-themes/1535
loop6         7:6    0 267,8M  1 loop /var/lib/snapd/snap/openttd/1115
                                      /var/lib/snapd/snap/openttd/1115
loop7         7:7    0  40,8M  1 loop /var/lib/snapd/snap/snapd/19993
                                      /var/lib/snapd/snap/snapd/19993
loop8         7:8    0  40,8M  1 loop /var/lib/snapd/snap/snapd/20092
                                      /var/lib/snapd/snap/snapd/20092
loop9         7:9    0 157,8M  1 loop /var/lib/snapd/snap/spotify/67
                                      /var/lib/snapd/snap/spotify/67
loop10        7:10   0 158,5M  1 loop /var/lib/snapd/snap/spotify/68
                                      /var/lib/snapd/snap/spotify/68
sr0          11:0    1  1024M  0 rom
nvme0n1     259:0    0 476,9G  0 disk
├─nvme0n1p1 259:1    0   260M  0 part
├─nvme0n1p2 259:2    0    16M  0 part
├─nvme0n1p3 259:3    0 310,4G  0 part
├─nvme0n1p4 259:4    0   512M  0 part
├─nvme0n1p5 259:5    0     8G  0 part [SWAP]
├─nvme0n1p6 259:6    0 157,2G  0 part /var/lib/snapd/snap
│                                     /
└─nvme0n1p7 259:7    0   512M  0 part /efi
Timeout: 0 seconds
BootOrder: 0004,2001,3004,2002,0000,0003,0000,000C,2004
Boot0000* Windows Boot Manager	HD(1,GPT,e4ad1fb3-eae0-4c6d-a73f-0fc63dd6edf3,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0001* Windows Boot Manager	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0003* grub	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\grub\grubx64.efi)
Boot0004* debian	HD(1,GPT,e4ad1fb3-eae0-4c6d-a73f-0fc63dd6edf3,0x800,0x82000)/File(\EFI\debian\shimx64.efi)
Boot0005* Windows Boot Manager	HD(1,GPT,e4ad1fb3-eae0-4c6d-a73f-0fc63dd6edf3,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
Boot0009* Windows Boot Manager	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot000B* Windows Boot Manager	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot000C* EFI Hard Drive (INTEL SSDPEKNW512G8H)	PciRoot(0x0)/Pci(0x1d,0x4)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-00-00)/HD(4,GPT,9466b91e-c2a4-df4a-bb10-fb41dcfd0ecc,0x26d6b000,0x100000)RC
Boot0010* Linux Boot Manager	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\systemd\systemd-bootx64.efi)
Boot0011* Windows Boot Manager	HD(7,GPT,f8054be6-6697-ea4e-aaa8-dc838064113d,0x26e6b000,0x100000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot3004* Internal Hard Disk or Solid State Disk	RC

Thank you very much for any reponse in advance.

It is probably this one:

You can use efibootmgr to put it back in the boot order. Or you can just run sudo bootctl install from inside your install.

However, your EFI is a mess. Windows is there 6 times on 2 different disks. You also have entries for 2 other Linux distros. The boot order has duplicates and invalid entries in it.

You should really clean that up at some point.

1 Like