Issue with boot order after switching to systemd-boot

Followed everything exactly as written in this tutorial (kernel-install method). Now, when I reboot, it says something like:

error: file ‘/@/boot/grub/x86_64-efi/normal.mod’ not found.
Entering rescue mode…
grub rescue> _

I don’t get it. Why did it work with my burner laptop, but when I try this laptop, it just keeps doing this!

Well, for one thing, you aren’t using systemd-boot if you are sitting at a grub rescue prompt.

Can you boot off the ISO and share the output of sudo efibootmgr -v and sudo parted -l and

Using efibootmgr, set 0001 as the first thing in your boot order.

Alternatively, go into your BIOS and select “Linux Boot Manager” as the default.

Either way, the result should be the same.

How would I do this the terminal (efibootmgr) way? I prefer doing things via the terminal now, thanks to this distro.

sudo efibootmgr --bootorder 0001,0002,0000

Weird, it didn’t work. My UEFI firmware settings doesn’t show Linux Boot Manager either. I am feeling hopeless at this point. I remember having a similar problem to this one when I used Solus. I am so confused.

You appear to have stopped replying. I’ll give it a bit more time before I just reinstall the system.

Sorry, I am doing other things in addition to spending time on the forum.

There is no reason to reinstall unless it is totally clean system to being with.

We just need to repair the bootloader.

I would try booting off the ISO and using arch-chroot to get back into your system. Let us know if you need instructions for that.

Then try running bootctl status and see what the output it.

1 Like

You gotta give folks time lol

We’re all here to help but can’t be around 24/7/365 and most of folks around here aren’t paid for any of this. XP we’re just a bunch of nerds.

1 Like

Yeah, but I had gotten used to the 2 minute reply times. Guess I got spoiled.

Well now you have gotten the attention of two moderators…

We do this for free on our own time. Do you see the conundrum that is created by “getting spoiled” on reliance of other people’s good intentions?


Yeah, I have no idea how to arch-chroot, as this is my first time. Any instructions on how to chroot?

Yeah, I guess I should be more patient. I just get into a panic when my main device runs into a problem.

  • Boot off the ISO
  • sudo mount /dev/nvme0n1p2 /mnt -o subvol=@
  • sudo arch-chroot /mnt

This should give you a # prompt. From inside the chroot:

mount /dev/nvme0n1p1 /efi
bootctl status

Paste the output of that here in the forum instead of using pastebin

Firmware: UEFI 2.70 (American Megatrends 5.17)
Secure Boot: disabled
Setup Mode: user
TPM2 Support: yes
Boot into FW: supported

Current Boot Loader:
Product: systemd-boot 249.3-1-arch
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Boot loader sets ESP information
WARNING: The boot loader reports a different ESP UUID than detected!
ESP: /dev/disk/by-partuuid/31323032-3830-4632-b232-303331313431

Random Seed:
Passed to OS: no
System Token: set
Exists: yes

Available Boot Loaders on ESP:
ESP: /efi (/dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101)
File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 249.4-1-arch)
File: └─/EFI/BOOT/bootx64.efi (systemd-boot 249.4-1-arch)

Boot Loaders Listed in EFI Variables:
Title: EndeavourOS
ID: 0x0000
Status: active, boot-order
Partition: /dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101
File: └─/EFI/EndeavourOS/grubx64.efi

    Title: Linux Boot Manager
       ID: 0x0001
   Status: active, boot-order
Partition: /dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101
     File: └─/EFI/systemd/systemd-bootx64.efi

Boot Loader Entries:
$BOOT: /efi (/dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101)

Default Boot Loader Entry:
title: EndeavourOS (5.14.5-arch1-1)
id: 85a1bc4e11ee4141a99892145aa64a1c-5.14.5-arch1-1.conf
source: /efi/loader/entries/85a1bc4e11ee4141a99892145aa64a1c-5.14.5-arch1-1.conf
version: 5.14.5-arch1-1
machine-id: 85a1bc4e11ee4141a99892145aa64a1c
linux: /85a1bc4e11ee4141a99892145aa64a1c/5.14.5-arch1-1/linux
initrd: /85a1bc4e11ee4141a99892145aa64a1c/5.14.5-arch1-1/intel-ucode.img
options: root=UUID=05d0b3ad-6cb8-4897-96cf-5138d83a87c3 rw rootflags=subvol=@ quiet resume=UUID=3d878d1e-73ca-4e63-8c16-d187f291cb5d loglevel=3 nowatchdog

Can you share lsblk -o name,fstype,size,uuid

loop0 squashfs 1.7G
sda iso9660 28.6G 2021-08-26-23-11-41-00
├─sda1 iso9660 1.8G 2021-08-26-23-11-41-00
├─sda2 vfat 98M 18C2-A58E
└─sda3 300K
nvme0n1 476.9G
├─nvme0n1p1 vfat 512M 6D6D-4959
├─nvme0n1p2 btrfs 459.4G 05d0b3ad-6cb8-4897-96cf-5138d83a87c3
└─nvme0n1p3 swap 17G 3d878d1e-73ca-4e63-8c16-d187f291cb5d

How about ls -l /dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101

No idea, but this is what it says:

lrwxrwxrwx 1 root root 15 Sep 18 19:15 /dev/disk/by-partuuid/5556cfb4-b620-6a48-84af-d99551c45101 → …/…/nvme0n1p1