FS#66290 - [dracut] 050-1 systemd module has hard depends on systemd-ask-password-plymouth.service
Attached to Project:
Arch Linux
Opened by jason ryan (jasonwryan) - Saturday, 18 April 2020, 06:05 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 15:57 GMT
Opened by jason ryan (jasonwryan) - Saturday, 18 April 2020, 06:05 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 04 May 2021, 15:57 GMT
|
Details
Description: Generating an img with dracut 050-1 throws an
error for a missing systemd module:
dracut: *** Including module: systemd *** Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist. Which is to be expected if you haven't installed, or have any desire to use, plymouth. Steps to reproduce: update to dracut 050-1 and generate an image,*without having plymouth installed*. The generated image does work, but throws additional errors on boot (possibly unrelated). |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Tuesday, 04 May 2021, 15:57 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 051
Tuesday, 04 May 2021, 15:57 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 051
What are the errors you are getting during boot?
Shiv dracut-initqueue[401]: Failed to start systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service
This is before the dracut prompt to unlock the luks container, which I can successfully decrypt.
systemctl status systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service
Unit systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service could not be found.
How are you setting up the encryption (rd.luks.id/rd.luks.name kernel command line option, contents of /etc/crypttab)? What is the output of "lsblk -f" (to match the UUID of the failing systemd unit to a partition)?
I applied your patch and I still get the spurious error message(s). The luks volume is the correct one. For some reason it fails the first time:
loader entry:
options rd.luks.uuid=19c6bbf3-c981-4276-82b3-bddfcfc7a8f2 root=UUID=1d2dfd7d-accb-47f4-aa42-c85bfcff8e2f rd.lvm.vg=vgroup init=/usr/lib/systemd/systemd quiet loglevel=3 rw
lsblk:
─luks-19c6bbf3-c981-4276-82b3-bddfcfc7a8f2 254:0 0 117.2G 0 crypt
/usr/bin/dracut -H -f --no-hostonly-cmdline --kver 5.6.5-1-JWR /boot/initfamfs-dracut.img
Rebooting shows the same error, without backslashes (ie., exactly as if using the default dracut-lib.sh).
I downgraded to 049, and no errors are thrown when generating the intird.
Should I just open a bug upstream for the plymouth issue?
Thanks for the help!
Opening an upstream issue for the "systemd-ask-password-plymouth.service does not exist" warning sounds like a good idea, it looks like it has been introduced by https://github.com/dracutdevs/dracut/commit/70b19acf941c0bf41b2c69c761124425910c0653 and should be easily fixed by checking for the existence of systemd-ask-password-plymouth.service before running systemctl add-wants in modules.d/00systemd/module-setup.sh (though this only comes from briefly looking over the relevant changes, I haven't actually verified that conjecture yet).
I have opened an issue upstream: https://github.com/dracutdevs/dracut/issues/795
And I'll begin the bisection to track down the other issue.