Failing to restore systemd-boot loader after motherboard change

Utini · 2025-01-31 16:44:55

Hi everyone,

I am running arch with windows 10 in dual boot.
My Archlinux is encrypted with luks/lvm.
Both OS are installed on the same nvme:

/dev/nvme0n1p1 = windows efi 100mb
/dev/nvme0n1p2 = windows 
/dev/nvme0n1p3 = windows
/dev/nvme0n1p4 = windows repair
/dev/nvme0n1p5 = linux extended boot partition
/dev/nvme0n1p6 = encrypted container

Basically I did the following to try and restore it:

Boot arch from USB
cryptsetup luksOpen /dev/nvme0n1p6 lvm
mount /dev/mapper/mycontainer /mnt
mount /dev/nvme0n1p1 /mnt/efi
mount /dev/nvme0n1p5 /mnt/boot
arch-chroot
bootctl --esp-path=/efi --boot-path=/boot install
exit
umount -R /mnt 
reboot

I can still only see the windows boot manager in BIOS. Any ideas?

I will follow up in sec with more outputs.

Scimmia · 2025-01-31 16:50:40

Is the entry there in `efibootmgr -u` after the bootctl install?

Utini · 2025-01-31 17:03:15

Scimmia wrote:

Is the entry there in `efibootmgr -u` after the bootctl install?

I will re-check in my next post. Let me first post some of the other outputs here:

[root@archiso /]# ls -al /boot
total 349392
drwxr-xr-x 4 root root   4096 Jan  1  1970 .
drwxr-xr-x 18 root root   4096 Nov 29 13:19 ..
drwxr-xr-x 3 root root   4096 Mar 17 2023 EFI
-rwxr-xr-x 1 root root 153600 Jan 10 10:26 amd-ucode.img
-rwxr-xr-x 1 root root 139044711 Jan 20 07:27 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root 86912693 Jan 20 07:27 initramfs-linux-lts-fallback.img
-rwxr-xr-x 1 root root 49145587 Jan 20 07:27 initramfs-linux-lts.img
-rwxr-xr-x 1 root root 55595311 Jan 20 07:27 initramfs-linux.img
drwxr-xr-x 3 root root   4096 Mar 20 2023 loader
-rwxr-xr-x 1 root root 13074944 Jan 20 07:26 vmlinuz-linux

[root@archiso /]# ls -al /boot/loader
total 16
drwxr-xr-x 3 root root 4096 Mar 20 2023 .
drwxr-xr-x 4 root root 4096 Jan  1  1970 ..
drwxr-xr-x 2 root root 4096 Jul 14 2023 entries
-rw-r--r-- 1 root root    6 Mar 17 2023 entries.srel

[root@archiso /]# ls -al /boot/loader/entries
total 28
drwxr-xr-x 2 root root 4096 Jul 14 2023 .
drwxr-xr-x 3 root root 4096 Mar 20 2023 ..
-rwxr-xr-x 1 root root  492 Jul 14 2023 arch-fallback.conf
-rwxr-xr-x 1 root root  332 Mar 20 2023 arch-hardened.conf
-rwxr-xr-x 1 root root  504 Jul 14 2023 arch-lts-fallback.conf
-rwxr-xr-x 1 root root  518 Jul 14 2023 arch-lts.conf
-rwxr-xr-x 1 root root  601 Sep  4 07:18 arch.conf

[root@archiso /]# ls -al /boot/EFI
total 12
drwxr-xr-x 3 root root 4096 Mar 17 2023 .
drwxr-xr-x 4 root root 4096 Jan  1  1970 ..
drwxr-xr-x 2 root root 4096 Mar 17 2023 Linux

[root@archiso /]# ls -al /boot/EFI/Linux
total 8
drwxr-xr-x 2 root root 4096 Mar 17 2023 .
drwxr-xr-x 3 root root 4096 Mar 17 2023 ..

[root@archiso /]# ls -al /efi
total 6
drwxr-xr-x 5 root root 1024 Jan  1  1970 .
drwxr-xr-x 18 root root 4096 Nov 29 13:19 ..
drwxr-xr-x 5 root root 1024 Mar 17 2023 EFI
drwxr-xr-x 2 root root 1024 Mar 18 2023 System Volume Information
drwxr-xr-x 4 root root 1024 Jan 31 18:31 loader

[root@archiso /]# ls -al /efi/EFI
total 5
drwxr-xr-x 5 root root 1024 Mar 17 2023 .
drwxr-xr-x 5 root root 1024 Jan  1  1970 ..
drwxr-xr-x 2 root root 1024 Jan 31 18:31 Boot
drwxr-xr-x 4 root root 1024 Mar 18 2023 Microsoft
drwxr-xr-x 2 root root 1024 Jan 31 18:31 systemd

[root@archiso /]# ls -al /efi/EFI/systemd
total 124
drwxr-xr-x 2 root root 1024 Jan 31 18:31 .
drwxr-xr-x 5 root root 1024 Mar 17 2023 ..
-rwxr-xr-x 1 root root 124416 Jan 13 10:12 systemd-bootx64.efi

[root@archiso /]# ls -al /efi/EFI/Boot
total 124
drwxr-xr-x 2 root root 1024 Jan 31 18:31 .
drwxr-xr-x 5 root root 1024 Mar 17 2023 ..
-rwxr-xr-x 1 root root 124416 Jan 13 10:12 bootx64.efi

[root@archiso /]# ls -al /efi/loader
total 6
drwxr-xr-x 4 root root 1024 Jan 31 18:31 .
drwxr-xr-x 5 root root 1024 Jan  1  1970 ..
drwxr-xr-x 2 root root 1024 Jan 31 18:31 entries
drwxr-xr-x 2 root root 1024 Jan 31 17:29 keys
-rwxr-xr-x 1 root root   45 Mar 23 2023 loader.conf
-rwxr-xr-x 1 root root   32 Jan 31 18:31 random-seed

[root@archiso /]# ls -al /efi/loader/entries
total 6
drwxr-xr-x 2 root root 1024 Jan 31 18:31 .
drwxr-xr-x 4 root root 1024 Jan 31 18:31 ..
-rwxr-xr-x 1 root root  492 Jan 31 18:31 arch-fallback.conf
-rwxr-xr-x 1 root root  332 Jan 31 18:31 arch-hardened.conf
-rwxr-xr-x 1 root root  504 Jan 31 18:31 arch-lts-fallback.conf
-rwxr-xr-x 1 root root  518 Jan 31 18:31 arch-lts.conf
-rwxr-xr-x 1 root root  601 Jan 31 18:31 arch.conf

[root@archiso /]# bootctl --esp-path=/efi --boot-path=/boot install
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".
! Mount point '/efi' which backs the random seed file is world accessible, which is a security hole!
! Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole!
Random seed file /efi/loader/random-seed successfully refreshed. (32 bytes)
[root@archiso /]#

[root@archiso /]# bootctl status

System:
  Not booted with EFI.

Available Boot Loaders on ESP:
  » ESP: /efi
    File: /EFI/systemd/systemd-bootx64.efi (systemd-boot 257.2-2-arch)
          /EFI/BOOT/bootx64.efi (systemd-boot 257.2-2-arch)

Boot Loader Entries:
  $BOOT: /boot
  token: arch

Default Boot Loader Entry:
  type: Boot Loader Specification Type #1 (.conf)
  title: Arch Linux (arch.conf)
  id: arch.conf
  source: /efi/loader/entries/arch.conf (on the EFI System Partition)
  linux: /efi/vmlinuz-linux (No such file or directory)
  initrd: /efi/amd-ucode.img (No such file or directory)
          /efi/initramfs-linux.img (No such file or directory)
  options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock

WARNING: default boot entry is broken.
[root@archiso /]#

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux (arch.conf) (default) (not reported/new)
id: arch.conf
source: /efi/loader/entries/arch.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux (arch.conf) (not reported/new)
id: arch.conf
source: /boot/loader/entries/arch.conf (on the Extended Boot Loader Partition)
linux: /boot/vmlinuz-linux
initrd: /boot/amd-ucode.img
        /boot/initramfs-linux.img
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux LTS (arch-lts.conf) (not reported/new)
id: arch-lts.conf
source: /efi/loader/entries/arch-lts.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux-lts (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-lts.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux LTS (arch-lts.conf) (not reported/new)
id: arch-lts.conf
source: /boot/loader/entries/arch-lts.conf (on the Extended Boot Loader Partition)
linux: /boot/vmlinuz-linux-lts
initrd: /boot/amd-ucode.img
        /boot/initramfs-linux-lts.img
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux LTS Fallback (arch-lts-fallback.conf) (not reported/new)
id: arch-lts-fallback.conf
source: /efi/loader/entries/arch-lts-fallback.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux-lts (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-lts-fallback.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine lsm=landlock
type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux LTS (arch-lts.conf) (not reported/new)
id: arch-lts.conf
source: /efi/loader/entries/arch-lts.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux-lts (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-lts.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux LTS Fallback (arch-lts-fallback.conf) (not reported/new)
id: arch-lts-fallback.conf
source: /efi/loader/entries/arch-lts-fallback.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux-lts (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-lts-fallback.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux Hardened (arch-hardened.conf) (not reported/new)
id: arch-hardened.conf
source: /efi/loader/entries/arch-hardened.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux-hardened (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-hardened.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine

type: Boot Loader Specification Type #1 (.conf)
title: Arch Linux Fallback (arch-fallback.conf) (not reported/new)
id: arch-fallback.conf
source: /efi/loader/entries/arch-fallback.conf (on the EFI System Partition)
linux: /efi/vmlinuz-linux (No such file or directory)
initrd: /efi/amd-ucode.img (No such file or directory)
        /efi/initramfs-linux-fallback.img (No such file or directory)
options: cryptdevice=UUID=f9132979-a484-4710-95ab-a64bbccf8257:lv; allow-discards root=/dev/MyVolumeGroup/mine

Utini · 2025-01-31 17:14:37

Scimmia wrote:

Is the entry there in `efibootmgr -u` after the bootctl install?

Didn't even have efibootmgr installed until now :S
It doesn't seem to be in the list:

[root@archiso /]# efibootmgr -u
BootCurrent: 001E
Timeout: 0 seconds
BootOrder: 001C,0010,0011,0012,0013,0014,001B,001D,001E,001F,0020,0021,0022
Boot0000* Windows Boot Manager	HD(1,GPT,0515b7c3-4740-4666-b054-42e9efe1772,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi) ▒▒▒▒S
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Diagnostic Splash Screen	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Lenovo Diagnostics	FvFile(4376ab9a-6ab0-4aeb-a9d9-163e59a7a380)
Boot0013  ThinkShield secure wipe	FvFile(3593a045-bd52-43d0-80be-cbf5ece2477)
Boot0014  ThinkShield Passwordless Power-On	Usb(0x0,0x2e2e953bba)-/app
Boot001B  Startup Interrupt Menu	FvFile(da465b87-a2bf-4c12-b78a-0316172a8026)
Boot001D  Rescue and Recovery	FvFile(66545f30-a3de-4cad-8e26-d4bcee9f1b5)
Boot001E  USB CD	VenMsg(bc7838d2-0f82-4460-8316-c06bee79425b,b6721926a5a78b8d6c8494d13ba6a55)
Boot001F  USB FDD	VenMsg(bc7838d2-0f82-4460-8316-c06bee79425b,6ff015a2830b0543a80b8610099461e49)
Boot0020  Other HDD	VenMsg(bc7838d2-0f82-4460-8316-c06bee79425b,93c491a4ceae9aa0b6e9be8ba400)
Boot0021  PXE BOOT	VenMsg(bc7838d2-0f82-4460-8316-c06bee79425b,ca80c2349e7ae947ebf43003a5caae

Scimmia · 2025-01-31 17:16:32

I know grub and refind require it to add entries, not sure about systemd-boot. If you do the bootctl install again now with it installed, does it add the entry?

Utini · 2025-01-31 17:19:20

Scimmia wrote:

I know grub and refind require it to add entries, not sure about systemd-boot. If you do the bootctl install again now with it installed, does it add the entry?

Already tried and didn't work

Head_on_a_Stick · 2025-01-31 17:26:31

Which filesystem are you using the the /boot/ partition? If it's non-FAT have you added the EFI filesystem drivers to /efi/EFI/systemd/drivers/?

For /boot/loader/entries/arch{,-lts}.conf, the path for the kernel & initramfs images should be relative to the XBOOTLDR partition. Remove the leading /boot from their paths and see if that works.

zakazak · 2025-01-31 17:39:40

Head_on_a_Stick wrote:

Which filesystem are you using the the /boot/ partition? If it's non-FAT have you added the EFI filesystem drivers to /efi/EFI/systemd/drivers/?
For /boot/loader/entries/arch{,-lts}.conf, the path for the kernel & initramfs images should be relative to the XBOOTLDR partition. Remove the leading /boot from their paths and see if that works.

/efi and /boot are both fat32.

ChatGPT fixed my issue by suggestion the following:

efibootmgr --create --disk /dev/nvme0n1 --part 1 --label "Systemd-boot" --loader /EFI/systemd/systemd-bootx64.efi

I would still like to understand what is happening.
Basically I now manually added the entry for the systemd bootloader manually.
But why didn't it work previously with the bootctl install command?

Head_on_a_Stick · 2025-01-31 17:44:07

That command sometimes fails to create an entry, I can't find any links atm but I've seen it before here.

Apologies for not noticing the missing boot entry, that was obvious from your posted output.

V1del · 2025-01-31 17:47:15

System:
  Not booted with EFI.

did you reboot and pick a different entry between the bootctl commands and the efibootmgr commands? Since the Arch USB is bootable for both, most mainboards will present you entries for an UEFI (mostly denoted with a [UEFI] prefix or so) or a BIOS boot, and if you picked the wrong one initially and the right one the second time around, this might explain the relevant difference

Utini · 2025-01-31 18:29:24

V1del wrote:

System:
  Not booted with EFI.
did you reboot and pick a different entry between the bootctl commands and the efibootmgr commands? Since the Arch USB is bootable for both, most mainboards will present you entries for an UEFI (mostly denoted with a [UEFI] prefix or so) or a BIOS boot, and if you picked the wrong one initially and the right one the second time around, this might explain the relevant difference

Mhh I rebooted like 20 times and re-tried everything above several times so everything is possible.
How ever, I always rebooted in the same manner:
- Reboot
- Press Enter during BIOS boot up
- Press F12 to boot the boot selector utiliy
- Select USB Stick to boot

Arch Linux

#1 2025-01-31 16:44:55

Failing to restore systemd-boot loader after motherboard change

#2 2025-01-31 16:50:40

Re: Failing to restore systemd-boot loader after motherboard change

#3 2025-01-31 17:03:15

Re: Failing to restore systemd-boot loader after motherboard change

#4 2025-01-31 17:14:37

Re: Failing to restore systemd-boot loader after motherboard change

#5 2025-01-31 17:16:32

Re: Failing to restore systemd-boot loader after motherboard change

#6 2025-01-31 17:19:20

Re: Failing to restore systemd-boot loader after motherboard change

#7 2025-01-31 17:26:31

Re: Failing to restore systemd-boot loader after motherboard change

#8 2025-01-31 17:39:40

Re: Failing to restore systemd-boot loader after motherboard change

#9 2025-01-31 17:44:07

Re: Failing to restore systemd-boot loader after motherboard change

#10 2025-01-31 17:47:15

Re: Failing to restore systemd-boot loader after motherboard change

#11 2025-01-31 18:29:24

Re: Failing to restore systemd-boot loader after motherboard change

Board footer