[solved] systemd-boot and GRUB stopped showing ARCH boot entry

nur_lisa · 2024-01-22 14:33:04

**Update**:
The problem was that the linux imgs were not on my EPS/boot partition anymore for some reason (if you have any clue why that could happen, let me know). Mounting both root and EPS partition, chrooting into Root, then running 'sudo pacman -S linux' fixed the issue.

Hey guys,

I desperately need your help - not even the local hackerspace group was able to help me with this problem and I need my laptop for work tomorrow.

My old laptop broke and I got a new one (went from Thinkpad E15 with AMD processor to Thinkpad T495 with AMD processor). I transferred the SSD with my Windows/Arch Linux dual boot from my old laptop to my new one.

Windows was booting fine, but Linux was not shown as an option in GRUB anymore.

I thought okay, maybe something in my GRUB broke, it has happened in the past also, might be time to switch to systemd-boot anyways.

So I set up an Arch ISO stick, mounted my Arch Linux partition and chrooted into it (that all worked fine btw), uninstalled GRUB and set up Systemd-Boot.

I mostly followed this guide, with some small modifications because my partitition is encrypted (usingLUKS):
https://bbs.archlinux.org/viewtopic.php?id=223909

My config file looks like this:
> title Arch Linux

> linux /vmlinuz-linux

> initrd /initramfs-linux.img

> options cryptdevice=UUID={UUID}:cryptlvm root=/dev/volume/root quiet rw

(of course with the proper UUID, which I copied directly into the file. I also tried PARTUIID={PARTUIID}, which didnt change anything)

For some reason that also doesnt work. I can use systemd-boot to start Windows, but Arch is not shown as an option anymore.
I switched back to GRUB, but same problem.

I really desperately need this laptop for my master thesis tomorrow, because I have a big deadline coming up. So I thought maybe you guys could pinpoint me towards the likely cause of error.

So far I thought of the following:

* The arch install does not work out of the box for a new laptop because of **driver/kernel issues** or something. Because it is broken, systemd-boot does not show it as an option. **Fix**: chroot into it and **install the missing drivers**(?) Is that possible? I thought in case of a broken install it would still be shown as an option and just fail during the boot process
* I missed something about how to set up **systemd-boot with LUKS**. Maybe my config file is wrong?
* I have the **wrong UUID**. Because of the encryption setup, theres two arch partitions, one very small one that i guess is responsible for decrypting process, and one big one with the data that i chroot into. I used the UUID of the second one, is that correct?
* I **physically damaged my SSD** somehow and that fucked up my install? is that even possible?
* Something is **wrong in my BIOS**, seeing as everything worked fine on the old laptop?

Should I just say fuck it, chroot into my partition, copy and backup all the data and then re-install everything? Or is there a solution I am missing?

Last edited by nur_lisa (2024-01-23 13:39:17)

V1del · 2024-01-22 15:33:26

systemd-boot with luks is not a thing if your kernels are not on the ESP, is/was the ESP mounted to /boot and does the ESP contain vmlinuz-linux and initramfs-linux.img? Chances are your initramfs needs to be explicitly updated and or you want to boot the fallback initramfs, but none of this has anything to do with systemd-boot or GRUB showing you the option. they might not show you the option if the underlying files do not exist.

Generally speaking there's a lot of assumptions and very little hard data here. Boot a live disk, mount all your partitions like you think they are logically correct, chroot in and post

efibootmgr -uv
lsblk -f
ls -l /boot
cat /boot/grub/grub.cfg

https://wiki.archlinux.org/title/List_o … n_services

nur_lisa · 2024-01-22 17:42:10

Hey, thank you so much for the reply! I really appreciate it <3

Heres the outputs

efibootmgr -uv 
BootCurrent: 001B
Timeout: 0 seconds
BootOrder: 001B,0002,0001,0010,0011,0012,0013,0018,0019,0016,0017,001A,0000,001C,001D
Boot0000  Windows Boot Manager	HD(1,GPT,61693cdc-6eb8-41b4-9f63-343f8ff2bf2c,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)䥗䑎坏S
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 dc 3c 69 61 b8 6e b4 41 9f 63 34 3f 8f f2 bf 2c 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 61 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* GRUB	HD(1,GPT,61693cdc-6eb8-41b4-9f63-343f8ff2bf2c,0x800,0x32000)/File(\EFI\GRUB\grubx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 dc 3c 69 61 b8 6e b4 41 9f 63 34 3f 8f f2 bf 2c 02 02 / 04 04 30 00 5c 00 45 00 46 00 49 00 5c 00 47 00 52 00 55 00 42 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
Boot0002* Linux Boot Manager	HD(1,GPT,61693cdc-6eb8-41b4-9f63-343f8ff2bf2c,0x800,0x32000)/File(\EFI\systemd\systemd-bootx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 dc 3c 69 61 b8 6e b4 41 9f 63 34 3f 8f f2 bf 2c 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
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
      dp: 04 06 14 00 66 8b 1c 72 6c 42 86 4e 8e 99 34 57 c4 6a b0 b9 / 7f ff 04 00
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
      dp: 04 06 14 00 2d 76 6a 12 58 57 ca 4f 85 31 20 1a 7f 57 f8 50 / 7f ff 04 00
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
      dp: 04 06 14 00 a6 d9 d8 a7 b0 6a eb 4a ad 9d 16 3e 59 a7 a3 80 / 7f ff 04 00
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
      dp: 04 06 14 00 5b 61 7e 3f 45 0d 80 4f 88 dc 26 b2 34 95 85 60 / 7f ff 04 00
Boot0014  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
      dp: 04 06 14 00 f4 e6 6e f4 85 47 a3 43 92 3d 7f 78 6c 3c 84 79 / 7f ff 04 00
Boot0015  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
      dp: 04 06 14 00 60 3f 5d 66 3e ad ad 4c 8e 26 db 46 ee e9 f1 b5 / 7f ff 04 00
Boot0016  USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 86 70 12 96 aa 5a 78 48 b6 6c d4 9d d3 ba 6a 55 / 7f ff 04 00
Boot0017  USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 6f f0 15 a2 88 30 b5 43 a8 b8 64 10 09 46 1e 49 / 7f ff 04 00
Boot0018* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 00 1c 19 99 32 d9 4c 4e ae 9a a0 b6 e9 8e b8 a4 00 / 7f ff 04 00
Boot0019* NVMe1	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a401)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 00 1c 19 99 32 d9 4c 4e ae 9a a0 b6 e9 8e b8 a4 01 / 7f ff 04 00
Boot001A  ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 00 / 7f ff 04 00
Boot001B* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 33 e8 21 aa af 33 bc 47 89 bd 41 9f 88 c5 08 03 / 7f ff 04 00
Boot001C  PCI LAN	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot001D  Regulatory Information	FvFile(e4a83242-deee-f12e-15ff-0102036cc3ce)
      dp: 04 06 14 00 42 32 a8 e4 ee de 2e f1 15 ff 01 02 03 6c c3 ce / 7f ff 04 00
Boot001E* Boot Next Boot Option	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,a7ca6d35b2c2684783721826a7404894)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b a7 ca 6d 35 b2 c2 68 47 83 72 18 26 a7 40 48 94 / 7f ff 04 00

lsblk -f
NAME        FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0                                              
sda                                                
├─sda1                                             
└─sda2                                             
nvme0n1                                            
├─nvme0n1p1                           59.6M    39% /boot
├─nvme0n1p2                                        
├─nvme0n1p3                                        
├─nvme0n1p4                                        
└─nvme0n1p5                                        
  └─root                              43.7G    71% /

ls -l /boot
total 3
drwxr-xr-x 9 root root  512 Jan 21 14:19 EFI
drwxr-xr-x 2 root root  512 Oct 25  2021 System Volume Information
drwxr-xr-x 7 root root 1024 Jan 20 15:59 grub
drwxr-xr-x 3 root root  512 Jan 22 08:51 loader

cat /boot/loader/entries/arch.conf
## This is just an example config file.
## Please edit the paths and kernel parameters according to your system.

title   Arch Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options cryptdevice=UUID="a574a7dc-5cd4-451f-86a7-17c5a17dc709":root root=/dev/mapper/root rw

Last edited by nur_lisa (2024-01-22 17:54:34)

Arch Linux

#1 2024-01-22 14:33:04

[solved] systemd-boot and GRUB stopped showing ARCH boot entry

#2 2024-01-22 15:33:26

Re: [solved] systemd-boot and GRUB stopped showing ARCH boot entry

#3 2024-01-22 17:42:10

Re: [solved] systemd-boot and GRUB stopped showing ARCH boot entry

Board footer