Arch Linux

eluffie

Member

Registered: 2021-11-01

Posts: 7

[Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

Hey guys,

I cannot boot LVM on LUKS with dracut unified image. No kernel parameters are passed using the EFI entry.
I am never asked for the password to unlock the LUKS partition. The full error message is:

dracut-initqueue[440]: Failed to start systemd-cryptsetup@luks\x2d6a962e7d\x2d.... : Unit systemd-cryptsetup@luks-[same uuid].service not found
Timed out waiting for device /dev/gpt-auto-root

dracut.conf:

omit_dracutmodules+=" brltty "
use_fstab=yes
hostonly="yes"
hostonly_cmdline="yes"
install_items+=" /etc/keymap_terminal "
show_modules=yes
uefi=yes
early_microcode=yes
add_drivers+=" lz4 fat vfat "


CMDLINE=(
	rd.luks=no
	root=/dev/mapper/MyVolGroup-root
	luks.name=6a962e7d-664d-4005-bf8a-e96271843b9b=cryptlvm
	rd.luks.allow-discards=luks-6a962e7d-664d-4005-bf8a-e96271843b9b
	rd.lvm.lv=MyVolGroup/root
	rd.lvm.lv=MyVolGroup/swap
	rd.luks.crypttab=no

	debug
	rootflags=rw,relatime
	rootfstype=ext4
	nosplash
	rd.shell
	rd.debug
	sysrq_always_enabled
)
kernel_cmdline="${CMDLINE[*]}"
unset CMDLINE

rdsosreport.txt

https://pastebin.com/DF4Y6dXX

lsinitrd:

https://pastebin.com/zUsSrxWQ

uuids:

0b627a48-a4b4-49a1-a94e-9de8ca73a8c5 -> ../../dm-2
2021-10-01-17-00-36-00 -> ../../sdc1
6a962e7d-664d-4005-bf8a-e96271843b9b -> ../../sdb2
88FD-8226 -> ../../sdb1
8c725152-214a-49e2-897b-e84691537fef -> ../../dm-1
EEA4-A93D -> ../../sdc2
fde509e0-c751-4396-afe8-0c4dd4330f64 -> ../../sda2

Any idea what I'm missing?

Last edited by eluffie (2021-11-10 21:23:50)

dreamycrane

Member

Registered: 2019-03-18

Posts: 25

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

The luks systemd generator I think reads the
/etc/crypttab
file.
Make sure it is correct
in the form

decrypted-volume-name <UUID-of-luks-partition>

plz post the output of

grep -i grub_cmd /etc/default/grub

eluffie

Member

Registered: 2021-11-01

Posts: 7

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

Hi, thanks for your reply.

At some point I deleted

/etc/crypttab

and subsequently set

rd.luks.crypttab=no

.
Shouldn't it still work using

rd.luks.name

or

rd.luks.uuid

.
I will add my root partition to crypttab and test on the weekend!

I am not using GRUB, just EFI which directly loads the unified image generated by dracut. I don't even have GRUB installed anymore.
Is

/etc/default/grub

still somehow considered by something?

Also, what volume name do I have to match in the crypttab entry?

eluffie

Member

Registered: 2021-11-01

Posts: 7

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

Sooo, I think what you were looking for in

/etc/default/grub

is in the CMDLINE variable in my dracut.conf in the first post.

And the /etc/crypttab explicitly states that the root volume is not supposed to be in there, so I think thats not the problem.

Does anybody have an idea on how to debug this or even how to temporarily make the system boot using the emergency shell?

eluffie

Member

Registered: 2021-11-01

Posts: 7

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

After extracting the initrd, I noticed that the 3 files in /etc/cmdline.d  do not match (at least not exactly) the lines I put in kernel_cmdline in dracut.conf. Why is that?

Also /proc/cmdline in the emergency shell contains a " Ln" at the end, where does that come from?

Khere

Member

From: Italy

Registered: 2020-03-04

Posts: 170

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

That can might be helpful https://bbs.archlinux.org/viewtopic.php?id=256471

---

Fan of Giorgio Moroder & Mohammad Ammax enemy

eluffie

Member

Registered: 2021-11-01

Posts: 7

Re: [Solved]dracut-initqueue: Failed to start systemd-cryptsetup not found

Ok, turns out the UEFI implementation of my shit noname motherboard was busted.

Using systemd-boot with the exact same unified image works, man I should've tried that earlier