Genes Lists via arch-general
2017-07-15 15:07:48 UTC
failing to ask for password for luks encrypted /home partition and boot
Fully updated from testing repos - when I reboot now, systemd no longer
asks for password to unlock luks partition. There is no hesitation at all and no password prompt at all. The boot runs through and gives an error that crypt set up failed.
Root is not encrypted just /home. I'm then prompted to press Ctl D or
give root password and drop to single user mode - doing that then I can
cryptsetup open /dev/sdxx home
which prompts for password and succeeds
After I do above, then the error goes away evidenced by:
systemctl status firstname.lastname@example.org
shows all is normal - exiting from single user 'repair' mode - then
boot continues and completes normally. And /home gets mounted via
/dev/mapper as normal
The issue is with latest systemd that I no longer get prompted for a
password for the luks encrypted partition.
systemd password agents:
running systemd-ask-password by hand does indeed ask for password
in the console.
/run/systemd/ask-password is empty directory.
the journal contains this:
systemd-cryptsetup: Failed to query password: Timer expired
systemd: Failed to start Cryptography Setup for home.
(Its possible that the bug is in systemd-cryptsetup in latest release?)
# pacman -Q linux systemd
I googled but was no able to find any relevant bugs - checked systemd
github issues but found nothing similar.