I’m trying to reinstall my bootloader but I’m having an issue (I’m using UEFI).
What I’ve tried so far:
Using the EndeavourOS live-usb, I mounted the root partition, /dev, /sys, /proc, and efi partition
Chrooted into root partition
entered “bootctl install”
My only problem is the last result of the command says “Failed to write ‘LoaderSystemToken’ EFI variable: No such file or directory”.
Perhaps the output of the following commands might give forum members experienced with systemd-boot some clues:
sudo parted -l
efibootmgr -v
and the content of /etc/fstab from your installed system.
Also using arch-chroot you wouldn’t need to mount /dev, /sys, etc.
Depending on your boot mode, you just need to mount your root partition and ESP in case of UEFI.
sudo parted -l output:
Model: JetFlash Transcend 64GB (scsi)
Disk /dev/sda: 63.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 1931MB 2041MB 110MB primary fat16 esp
Model: SAMSUNG MZVL21T0HCLR-00BL2 (nvme)
Disk /dev/nvme0n1: 1024GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat32 EFI System Partition boot, esp
2 274MB 290MB 16.8MB Microsoft reserved partition msftres
3 290MB 773GB 773GB ntfs Basic data partition msftdata
4 773GB 774GB 578MB fat32 boot, esp
5 774GB 1024GB 250GB ext4
efibootmgr -v output:
BootCurrent: 0002
Timeout: 0 seconds
BootOrder: 0007,0006,0001,0000,0003,2002,2003,2001
Boot0000* Fedora HD(1,GPT,cab29fb7-c976-4566-8cca-944f3ed32d87,0x800,0x82000)/File(\EFI\fedora\shim.efi) File(.䍒)
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 b7 9f b2 ca 76 c9 66 45 8c ca 94 4f 3e d3 2d 87 02 02 / 04 04 2e 00 5c 00 45 00 46 00 49 00 5c 00 66 00 65 00 64 00 6f 00 72 00 61 00 5c 00 73 00 68 00 69 00 6d 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 52 43
Boot0001* openSUSE HD(1,GPT,cab29fb7-c976-4566-8cca-944f3ed32d87,0x800,0x82000)/File(\EFI\opensuse\grubx64.efi)RC
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 b7 9f b2 ca 76 c9 66 45 8c ca 94 4f 3e d3 2d 87 02 02 / 04 04 38 00 5c 00 45 00 46 00 49 00 5c 00 6f 00 70 00 65 00 6e 00 73 00 75 00 73 00 65 00 5c 00 67 00 72 00 75 00 62 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 52 43
Boot0002* EFI USB Device (JetFlashTranscend 64GB) UsbWwid(8564,1000,0,20BBZT6KH2FGZVH)/CDROM(1,0x398c00,0x34a98)RC
dp: 03 10 2a 00 00 00 64 85 00 10 32 00 30 00 42 00 42 00 5a 00 54 00 36 00 4b 00 48 00 32 00 46 00 47 00 5a 00 56 00 48 00 53 00 / 04 02 18 00 01 00 00 00 00 8c 39 00 00 00 00 00 98 4a 03 00 00 00 00 00 / 7f ff 04 00
data: 52 43
Boot0003* EFI Hard Drive (S64NNX0RB06775-SAMSUNG MZVL21T0HCLR-00BL2) PciRoot(0x0)/Pci(0x6,0x2)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-BB-11-B4-5C-8E)/HD(4,GPT,a3dd64ec-a327-4d4c-b8e1-a8504adb5a3f,0x5a077801,0x1137ff)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 02 06 / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 25 38 bb 11 b4 5c 8e / 04 01 2a 00 04 00 00 00 01 78 07 5a 00 00 00 00 ff 37 11 00 00 00 00 00 ec 64 dd a3 27 a3 4c 4d b8 e1 a8 50 4a db 5a 3f 02 02 / 7f ff 04 00
data: 52 43
Boot0004* EFI PXE 0 for IPv4 (6C-24-08-18-1B-80) PciRoot(0x0)/Pci(0x1d,0x1)/Pci(0x0,0x0)/MAC(6c2408181b80,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 1d / 01 01 06 00 00 00 / 03 0b 25 00 6c 24 08 18 1b 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0c 1b 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 52 43
Boot0005* EFI PXE 0 for IPv6 (6C-24-08-18-1B-80) PciRoot(0x0)/Pci(0x1d,0x1)/Pci(0x0,0x0)/MAC(6c2408181b80,0)/IPv6([::]:<->[::]:,0,0)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 01 1d / 01 01 06 00 00 00 / 03 0b 25 00 6c 24 08 18 1b 80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 03 0d 3c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 / 7f ff 04 00
data: 52 43
Boot0006* Windows Boot Manager HD(1,GPT,cab29fb7-c976-4566-8cca-944f3ed32d87,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000035000100000010000000040000007fff0400
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 08 00 00 00 00 00 b7 9f b2 ca 76 c9 66 45 8c ca 94 4f 3e d3 2d 87 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 35 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0007* Linux Boot Manager HD(4,GPT,a3dd64ec-a327-4d4c-b8e1-a8504adb5a3f,0x5a077801,0x1137ff)/File(\EFI\systemd\systemd-bootx64.efi)
dp: 04 01 2a 00 04 00 00 00 01 78 07 5a 00 00 00 00 ff 37 11 00 00 00 00 00 ec 64 dd a3 27 a3 4c 4d b8 e1 a8 50 4a db 5a 3f 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot2001* EFI USB Device RC
dp: 7f ff 04 00
data: 52 43
Boot2002* EFI DVD/CDROM RC
dp: 7f ff 04 00
data: 52 43
Boot2003* EFI Network RC
dp: 7f ff 04 00
data: 52 43
I fixed it thanks, I just used arch-chroot instead of chroot and somehow the issue was resolved. Big thanks.
wait nevermind, I rebooted and I just see “Reboot to Firmware Interface” even though bootctl install went smoothly
Have a look here and check if your loaders are correctly configured:
https://wiki.archlinux.org/title/Systemd-boot#Adding_loaders
I don’t fully understand what I’m doing but here’s what I’ve tried so far:
What I wrote inside the endeavouros conf file:
title EndeavourOS Linux x86_64
efi /vmlinuz-linux
options root=dev nvidia-drm.modeset=1 ibt=off
After rebooting, I still run into the “Reboot to Firmware Interface” issue in systemd-boot
I would try something like
title EndeavourOS Linux x86_64
linux /vmlinuz-linux
initrd /intel-ucode.img ## or amd-ucode.img in case of AMD
initrd /initramfs-linux.img
options root=UUID=xxxx rw nvidia-drm.modeset=1 ibt=off ## replace xxxx with the UUID of the root partition
If you are using EOSes systemd-boot setup you shouldn’t be creating manual entries. That will just leave you with a mess.
It should be sufficient to arch-chroot in and run sudo reinstall-kernels
Thanks, I haven’t tried your solution but Dalto’s suggestion instead. But, I still really appreciate the help.
Huge thanks, this resolved my issue 
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.