[Solved] dracut 050-1 throws random error about plymouth

jasonwryan · 2020-04-18 00:53:13

Regenerating dracut after a custom kernel build for 5.6.5 throws this weird error:

 Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist.

Which makes total sense because I don't have plymouth installed. Why is dracut looking for a non-existent, and completely unneccessary, systemd service?

#edit: seems it is pulled by the sytemd module, which seems completely asinine:

dracut: *** Including module: systemd ***                                                                                                                      
Failed to add dependency on unit, unit systemd-ask-password-plymouth.service does not exist.

--

The generated initrd does work, but throws an additional error on boot about systemd-cryptsetup@.service failing (which is weird, as the correct luks volume is unlocked).

From the same boot:

┌─[Shiv ~]
└─╼ systemctl --failed                                                                                                                                        
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

Apr 18 12:03:29 Shiv systemd[1]: Starting Cryptography Setup for luks-19c6bbf3-c981-4276-82b3-bddfcfc7a8f2...
Apr 18 12:03:29 Shiv systemd[1]: Started Dispatch Password Requests to Console.
>>>> Apr 18 12:03:29 Shiv dracut-initqueue[401]: Failed to start systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service: Unit systemd-crypt> <<<<
Apr 18 12:03:44 Shiv kernel: random: crng init done
Apr 18 12:03:46 Shiv systemd-cryptsetup[396]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/19c6bbf3-c981-4276-82b3-bddfcfc>
Apr 18 12:03:46 Shiv systemd[1]: Finished Cryptography Setup for luks-19c6bbf3-c981-4276-82b3-bddfcfc7a8f2.
Apr 18 12:03:46 Shiv systemd[1]: Reached target Local Encrypted Volumes.
Apr 18 12:03:46 Shiv systemd[1]: Reached target System Initialization.
Apr 18 12:03:46 Shiv systemd[1]: Reached target Basic System.

┌─[Shiv ~]
└─╼ systemctl status systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service                                                           
Unit systemd-cryptsetup@luksx2d19c6bbf3x2dc981x2d4276x2d82b3x2dbddfcfc7a8f2.service could not be found.

Last edited by jasonwryan (2020-12-21 22:05:47)

jasonwryan · 2020-04-18 06:05:25

https://bugs.archlinux.org/task/66290

CarbonChauvinist · 2020-12-21 16:01:19

Thanks for this upstream report jasonwryan; looks like this fix got into the 51-1 release and we no longer get those nag messages now upon initrd rebuild.

Last edited by CarbonChauvinist (2020-12-21 23:13:26)

jasonwryan · 2020-12-21 22:05:28

I did have to suppress the annoying error about squashfs failing, but the other fixes are very welcome.

Arch Linux

#1 2020-04-18 00:53:13

[Solved] dracut 050-1 throws random error about plymouth

#2 2020-04-18 06:05:25

Re: [Solved] dracut 050-1 throws random error about plymouth

#3 2020-12-21 16:01:19

Re: [Solved] dracut 050-1 throws random error about plymouth

#4 2020-12-21 22:05:28

Re: [Solved] dracut 050-1 throws random error about plymouth

Board footer