The bootloader(systemd-boot) is not in my UEFI boot entries

General system Newbie
1

So I tried to dual-boot EndeavourOS with Mint with systemd-boot with a custom /efi directory. The installation succeeded, but after rebooting my PC, there’s no systemd-boot entry.

Tried troubleshooting by searching though the internet but I got stressed because almost all of them didn’t work :frowning:

I reinstalled again, but with a little troubleshooting
After installation, I tried to run bootctl install --esp-path=boot
Output:

[liveuser@eos-2024.09.22 ~]$ sudo bootctl install --esp-path=boot
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/boot' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/boot/loader/random-seed' is world accessible, which is a security hole! ⚠
Random seed file /boot/loader/random-seed successfully refreshed (32 bytes).
Failed to write 'LoaderSystemToken' EFI variable: No space left on device
[liveuser@eos-2024.09.22 ~]$

And then I tried manually putting it to my UEFI using efibootmgr

[liveuser@eos-2024.09.22 ~]$ sudo efibootmgr --create --disk /dev/nvme0n1p4 --part 4 --loader '\EFI\systemd\systemd-bootx64.efi' --label "Linux Boot Manager" --unicode
Could not prepare Boot variable: No space left on device

Like what do you mean??? I gave it 4 gigabytes of storage??

image
image781×565 47.3 KB

Btw I’m new to EOS sooo if you need more information like the logs then ask me!
You guys is my only hope!

2

This just a hunch, but I think it means the UEFI (ie the nvram) is full, not the disk partition.

3

This looks totally wrong :slight_smile:

give the output of efibootmgr ,

as the first picture, you probably need to chroot but --esp-path=boot is also wrong ,
p4 mountmount is also wrong fstab reverd to /efi if its on endeavouros… how did you installed it , manual ?

4

Hehe… Anyways here it is

umar@LINUXMINT:~$ efibootmgr
BootCurrent: 0002
Timeout: 2 seconds
No BootOrder is set; firmware will attempt recovery
Boot0002* ubuntu	HD(1,GPT,84b4e641-30de-477a-bea3-caef5f03a2b0,0x1000,0x96000)/File(\EFI\UBUNTU\SHIMX64.EFI)0000424f
Boot0004* UEFI: SMI USB DISK 1100	PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/CDROM(1,0x536b20,0x51040)0000424f
Boot0005* UEFI: SMI USB DISK 1100, Partition 2	PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(2,MBR,0x4a514722,0x536b20,0x51000)0000424f
Boot0006* UEFI: PXE IPv4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(04421ad27870,0)/IPv4(0.0.0.00.0.0.0,0,0)0000424f
Boot0007* UEFI: PXE IPv6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(04421ad27870,0)/IPv6([::]:<->[::]:,0,0)0000424f
Boot000A* ubuntu	HD(1,GPT,84b4e641-30de-477a-bea3-caef5f03a2b0,0x1000,0x96000)/File(\EFI\UBUNTU\SHIMX64.EFI)0000424f
Boot000D* UEFI: SMI USB DISK 1100	PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/CDROM(1,0x536b20,0x51040)0000424f
Boot000E* UEFI: SMI USB DISK 1100, Partition 2	PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(2,MBR,0x4a514722,0x536b20,0x51000)0000424f

I’m new to systemd-boot and arch so sometimes I don’t know what I’m doing… Even chroot or something like that.

Forgot to say this but when I first installed it I chose “replace partition” and for the bootloader location(idk I don’t really remember) I chose “New”

5

as first no bootorder, , do you have ubuntu stil installed ?
those need to removed afterall…

but systemd-boot implentation is not all the same we do use scripts to automatize it a bit…
but now what is faster, fix it or reinstall… i would first get rit of ubuntu …
if ubuntu not exist :slight_smile:

i would reinstall it , boot must set to /efi if you do manuel

6

Yeah it is installed cuz I used boot-repair on mint earlier so that’s why the name is “ubuntu”

anyways do I REALLY have to uninstall mint? if yes then that’s fine for the sake of installing EOS

7

no , but you have to see which bootorder you use… u have double
then you can remove one entry that is double

8

Yep, morning eyes sure didn’t see the path w/o the /boot or /boot/efi. Good catch.