Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

cc250080 · 2022-02-08 16:16:47

Dear all,

I had followed the installation wiki to the letter as far as I am aware, and I had read the documentation about systemd boot, sd-encrypt Hook and its kernel parameters, nevertheless after many trial and error I am still stuck at boot.

/etc/mkinitcpio.conf

HOOKS=(systemd keyboard sd-vconsole block sd-encrypt autodetect base udev modconf filesystems fsck)

And then I rebuild initramfs"

# mkinitcpio -P

/boot/loader/entries/arch.conf

title Arch
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options rd.luks.name=49a5c51a-6ced-48eb-a0ca-b7435aa390d5=root root=/dev/mapper/root rw

The output of blkid -s UUID

nvme0n1p6: UUID="49a5c51a-6ced-48eb-a0ca-b7435aa390d5"

And after any change to the loader config I did :

#bootctl install
#bootctl update

Nevertheless and after many tries and changes, I am getting the follow error during boot:

:: running hook [udev]
:: Triggering uevents...
Waiting for 10 seconds for device /dev/mapper/root ...
ERROR: device '/dev/mapper/root' not found. Skipping fsck.

And then it drops me into an emergency shell where I can just confirm the UUID is correct.

I am kind of desperate at this point, any ideas what might be wrong with my setup?

Thank you very much.

Last edited by cc250080 (2022-02-09 11:55:03)

cmm11 · 2022-02-08 23:35:13

Not sure if this will fix your issues (also maybe just typos in your post)
1. You have "filesystem" in your hooks line when it should be "filesystems"
2. /boot/loaders/entries/arch.conf should be /boot/loader/ (not loaders)
3. In your rd.luks.name you have :root when any examples i've seen has been = not :
Example - https://wiki.archlinux.org/title/dm-cry … .luks.name

Last edited by cmm11 (2022-02-08 23:40:49)

cc250080 · 2022-02-09 12:01:13

Dear cmm11, thanks for taking the time to answer and come with help.

I had checked such typos, since the system is not booting I was unable to upload or copy paste real files. The only discordance I really had was the ":" versus "=" in the arch.conf file inside loader. Actually I have seen in the documentation being used both with : and = and I tried both.

Right now I have checked and corrected (switched to = ) my files but I still have the same behaviour. I find it perplexing that the system looks for /dev/mapper/root before asking me for the passphrase to decrypt the source partition, but I am still seriously lost. I had also updated the first post to reflect the actual state of the config files.

Thank you very much for your suggestions, I need to keep looking =/

kermit63 · 2022-02-10 00:59:43

Where is /boot located? If it's inside your encrypted oot partition then it would account for the error you are seeing.

cc250080 · 2022-02-10 08:04:39

/boot is a different partition, in this case /dev/nvme0n1p2, the Efi partition that is also shared with windows 11.

Raynman · 2022-02-10 09:44:58

cc250080 wrote:

I had followed the installation wiki to the letter as far as I am aware

Where did you get those HOOKS? It doesn't match examples or advice from https://wiki.archlinux.org/title/dm-cry … n#Examples and https://wiki.archlinux.org/title/Mkinit … mmon_hooks

You have systemd, but the udev hook (which seems to cause the failure) is also included and (probably less important) the order is nonstandard.

Arch Linux

#1 2022-02-08 16:16:47

Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

#2 2022-02-08 23:35:13

Re: Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

#3 2022-02-09 12:01:13

Re: Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

#4 2022-02-10 00:59:43

Re: Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

#5 2022-02-10 08:04:39

Re: Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

#6 2022-02-10 09:44:58

Re: Problems with Systemd boot and sd-encrypt at boot "/dev/mapper/root nf

Board footer