Dracut cryptsetup error on boot but system still works

[strm]

Hi folks!

My system is booting up and running fine. However, when dracut stops at boot to wait for the luks passphrase for the root fs, it always prints out a warning like this:

dracut-initqueue: Failed to start systemd-cryptsetup@rootfs\x20rootfs.service: Unit ystemd-cryptsetup@rootfs\x20rootfs.service not found

I tried with kernel cmd line rootdelay=20 to no avail.

[ChaoticCookie]

Have you checked out https://wiki.gentoo.org/wiki/Rootfs_encryption#Systemd

Can you paste the contents of your grub cmdline?

Code: Select all

cat /proc/cmdline

[strm]

Thx for the hint. I have checked out and read the article. systemd is compiled with USE flag cryptsetup and dracut with dracut-cpio.

The cmdline is

Code: Select all

initrd=\EFI\.. quiet splash amdgpu.dpm=1 amdgpu.dcdebugmask=0x12 amdgpu.lockup_timeout=100000 rootdelay=90 root=UUID=.. rd.luks.key=..=/swap.key:UUID=.. rd.luks.name=..=rootfs rd.luks.name=..=swapfs rd.luks.options=..=keyfile-timeout=90s resume=/dev/mapper/swapfs systemd.machine_id=..

[ChaoticCookie]

Sounds like you maybe hitting a bug with rd.luks.key. From

Code: Select all

man 7 dracut.cmdline

crypto LUKS - key on removable device support
NB: If systemd is included in the dracut initrd, dracut’s built in removable device keying support won’t work. systemd will prompt for a password from the console even if you’ve supplied rd.luks.key. You may be able
to use standard systemd fstab(5) syntax to get the same effect. If you do need rd.luks.key to work, you will have to exclude the "systemd" dracut module and any modules that depend on it. See dracut.conf(5) and
https://bugzilla.redhat.com/show_bug.cgi?id=905683 for more information.

[/quote]

Can you try it without a keyfile and entering a password manually?

[zen_desu]

it only prints a warning but boots fine?

[strm]

Sry for the late reply.

Yes. It shows the warning but boots fine. I disabled keyfile and use password instead. Same result.