Bugzilla – Bug 1051741
No LUKS password prompt after update to udev/systemd 234
Last modified: 2017-08-04 06:04:20 UTC
Created attachment 734814 [details] Log of the zypper dup Hi all! I have a TW installation with a separate XFS /home partition, encrypted with LUKS. Since the recent update to systemd 234-2.1, the usual password dialogue is no longer shown during boot. Instead (if I switch to the cli with ESC), I get a screen with alternating error messages that I fail to interpret (see the attached images, sorry, this is not a VM, so only pictures …). After wrangling around with snapper a bit, I am very sure this is due to the update from udev and systemd version 233-2.2 to 234-2.1. I attached the log of zypper dup, which contains a lot of dracut and udev messages, where I don't see the reason for the computer's behaviour.
Created attachment 734815 [details] The updates I installed
Created attachment 734816 [details] The boot screen Unfortunately, only a picture … this is how the boot screen looks. Usually, I expect an "enter your 'home' password here" prompt.
Created attachment 734817 [details] Message 1/2 Error message reads A start job is running for dev-mapper-cr_home.device
Created attachment 734818 [details] Message 2/2 The second message reads A start job is running for dev-disk-by\WHATEVER-THAT-IS.device P.S.: Is there any chance to upload multiple attachments at once? I feel quite wrong right now :-/
The same happened to me and it seems that is https://bugzilla.opensuse.org/show_bug.cgi?id=1048679 (on 42.2). The comment #2 in duplicate https://bugzilla.opensuse.org/show_bug.cgi?id=1050299 explains what to do to fix it. I started TW (could not enter /home password), logged in as root. ls /dev/disk/by-id/nvme-* The edited /etc/crypttab to have the matching ...part1 entry. After reboot, I could enter the /home password as usual.
@Michael Born: Thanks for the information. I wonder why I got the "old" format anyway? Wouldn't it be good to alter the installer to use the "new" format? My install is just a couple of weeks old … *** This bug has been marked as a duplicate of bug 1048679 ***