http://bugzilla.opensuse.org/show_bug.cgi?id=904987 --- Comment #1 from Federico Vecchiarelli --- Created attachment 613254 --> http://bugzilla.opensuse.org/attachment.cgi?id=613254&action=edit Screenshot - List of disks by-uuid In this screenshot you can see dracut looking for the root volume, however, because it has not unlocked the encrypted luks (on the screenshot shown as 3c8dd99d-28c7-4258-a19f-c75e0a067076), the boot process can't continue. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@suse.com Assignee|trenn@suse.com |juwolf@suse.com --- Comment #2 from Thomas Renninger --- There was a similar report already? As the 13.2 medium is out already I guess all that can be done is writing an article on the opensuse wiki page... Federico: Would you mind doing so, please. Please take care to have key words like 13.1 to 13.2 update/upgrade crypt/whatever included, so that others can find it quickly. Then just paste in your workaround as described in this bug. A reference to this bug may also be nice if we still find some more that can be done. This would help others with a similar setup a lot. Afaik Julian tried an update and it worked, but the setup may have been slightly different? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Vojtech Zeisek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Vojtech.Zeisek@opensuse.org --- Comment #4 from Vojtech Zeisek --- I didn't experience that problem I have in laptop mSATA with boot and encrypted LVM containing root and swap, and large HDD contains encrypted home. root and home use ext4. So that in 13.1 I was asked for two passwords during the boot. I on-line upgraded to 13.2 and there was no problem in the boot. The only think is I'm asked only for one password during the boot. I have no idea how his is possible. But it works. All partitions are correctly mounted. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 --- Comment #6 from Vojtech Zeisek --- Yes, I do $ cat /etc/crypttab cr_home /dev/disk/by-id/ata-ST1000LM014-1EJ164_W3802Q1Y-part1 none none cr_ata-KINGSTON_SMS200S360G_50026B72420708CE-part3 /dev/disk/by-id/ata-KINGSTON_SMS200S360G_50026B72420708CE-part3 none none $ cat /etc/fstab UUID=63dab9f4-dbe1-44be-a93d-b7a6e141b44d / ext4 noatime,defaults,noacl,user_xattr 1 1 /dev/mapper/cr_home /home ext4 acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,nofail 0 2 /dev/disk/by-id/ata-KINGSTON_SMS200S360G_50026B72420708CE-part2 /boot ext4 acl,user_xattr 1 2 UUID=cb0a2ff8-b112-4eb4-af0b-549c8ca05697 swap swap defaults 0 0 /dev/disk/by-id/ata-KINGSTON_SMS200S360G_50026B72420708CE-part1 /boot/efi vfat umask=0002,utf8=true 0 0 I haven't touched those files. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 --- Comment #8 from Vojtech Zeisek --- I didn't create cryptab. I encrypted the system during installation of 13.1, so the installer had to create it, I guess. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c10 --- Comment #10 from Alexander Naumov --- Hey, I can reproduce it with kernel 4.9.0-2.gfd5379c-pae (i686). After entering passphrase system froze for 2 mins. After that we get kernel-message every second: dracut-initqueue[131]: Warning dracut-initqueue timeout - starting timeout stripts After 1 min we get dracut-shell... I can't mount USB stick (for copying /run/initramfs/rdsosreport.txt), kernel doesn't see new devices. Kernel 4.8.13-1-default works well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c11 --- Comment #11 from Alexander Naumov --- Update kernel to 4.10 (from /Kernel:/HEAD/standard) fixes this problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c14 --- Comment #14 from Chris Targett --- Created attachment 712434 --> http://bugzilla.opensuse.org/attachment.cgi?id=712434&action=edit lsinitrd outputs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c16 Joost W changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joostw@gmx.de --- Comment #16 from Joost W --- Hi everybody, sorry, found this only after placing another bug, please have a look here as my issue seems similar: https://bugzilla.opensuse.org/show_bug.cgi?id=1024240 Bye, Joost -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c18 --- Comment #18 from Daniel Molkentin --- Please provide the output of the following: cat /etc/crypttab sudo lsinitrd -f etc/crypttab /usr/lib/systemd/system-generators/systemd-cryptsetup-generator && ls /tmp/*.service -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c20 --- Comment #20 from Joost W --- Created attachment 713413 --> http://bugzilla.opensuse.org/attachment.cgi?id=713413&action=edit Output of systemd-cryptsetup-generator -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c22 --- Comment #22 from Joost W --- Created attachment 713424 --> http://bugzilla.opensuse.org/attachment.cgi?id=713424&action=edit output of ls -l /dev/disk/by-id -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c24 Steffen Golle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stamper@stampernet.de --- Comment #24 from Steffen Golle --- I ran into the same problem. openSUSE Tumbleweed with Kernel 4.9.10 is not starting anymore. At boot, the plymouth splash screen doesn't show the password prompt. The system message from dracut-initqueue is: Failed to connect to the bus. No such file or directory. Can you tell me, how to enter the dracut shell from grub? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c26 --- Comment #26 from Chris Targett --- I have just attempted to install Tumbleweed on a new hardware. - Intel NUC - Corsair Force NVME SSD - OpenSUSE-Tumbleweed-DVD-x86_64-Snapshot20170304-Media.iso (4.10.1-1-default) *all* installs have been booted through UEFI. * First install attempt using the LUKS+LVM option resulted in 3 partitions. efi(vfat), boot(ext4), and system(lvm). On boot no password entry was requested, and was not present on any alternate TTYs. System dropped to a dracut shell. * Second install attempt, the installer initially wanted to install to the USB stick that was installing it. When changing the target disk and selecting the LUKS+LVM option, only two partitions were created. efi(vfat) and system(lvm). On boot Grub requested the LVM password, and the subsequent graphical boot also requested the password. System booted flawlessly. * Third install attempt matched the third. No password prompt on any TTY. In dracut shell: * /etc/crypttab was empty In chrooted mount (from dracut shell): * /etc/crypttab contains `cr_-Force-part3 /dev/disk/by-id/-Force-part3 none none` There is no /dev/disk/by-id matching that name. * `lsinitrd -f etc/crypttab` returns no output. But `lsinitrd | grep crypttab` lists a 0 byte file. * `/usr/lib/systemd/system-generators/systemd-cryptsetup-generator` creates `cryptsetup.target.requires`, `dev-disk-by-id\x2did-\x2dForce\x2dpart3.device.wants`, `dev-mapper-cr_\x2dForce\x2dpart3.device.d`, `dev-mapper-cr_\x2dForce\x2dpart3.device.requires`, `systemd-cryptsetup@cr_\x2dForce\x2dpart3.service`. Running `dracut -f` did not change the size of crypttab in `lsinitrd`. Fixing the crypttab to point to somewhere that does exist, and then running `dracut -f` fixed the size of the crypttab in the initrd. On boot the password was requested, but did not progress past the loading throbber. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Steven Harms changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjharms@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c29 Sebastian Rettenberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian.radish@gmx.de --- Comment #29 from Sebastian Rettenberger --- Is there any update to this issue? I stumbled across when applying updates to Leap 42.2. The default installation works well but after installing all updates, the system does not show the password prompt. The system did not fall into the dracut shell but I can access it with the rescue system from the installation medium. - /etc/crypttab is correct - etc/crypttab in the initrd was empty - Running dracut -f fixed the crypttab in the initrd but still no password prompt after reboot. Is there anything else I need to run on the rescue system? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Dariusz Ostolski changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.opensuse.or | |g/show_bug.cgi?id=1049359 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Dariusz Ostolski changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|http://bugzilla.opensuse.or | |g/show_bug.cgi?id=1049359 | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 http://bugzilla.opensuse.org/show_bug.cgi?id=904987#c32 Chris Scheible changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cgscheible@yahoo.com --- Comment #32 from Chris Scheible --- Hi, I hit the same issue after applying the latest patches to OpenSuse 42.2 two weeks ago on my system (HP Spetre 13 w/ NVME SSD). The system is configured with LUKS encrypted system LVM, only /boot is unencrypted. The encrypted LVM setup was done by the OpenSuse installer when I provisioned the system. The symptom for me was exactly the same as in the other bug reports: no password prompt for unlocking and mounting the rootfs logical volume during boot. The root cause that I found on the system was that the OpenSuse patch update automagically renamed the partitions in /dev/disk/by-id/ . However, the update neither rebuilt the /etc/crypttab with the new partition names nor rebuilt the initrd. To get the system working again, I used the following procedure: * Boot into emergency shell from grub menu (add '1' to end of kernel boot line), the shell with the boot output just errors out after not finding the rootfs and tells me to rebuild the initrd... * Selected emergency shell with ALT+F7 (shouldn't the emergency shell prompt open on the same shell as the boot messages?) * dracut emergency shell /etc/crypttab contained old /dev/disk/by-id/ partition ... * Booted rescue system from USB stick and setup chroot environment. Did the following in the chroot environment: ls -l /dev/disk/by-id/ (find partition with the encrypted physical volume for the system LVM) cryptsetup luksOpen /dev/nvme0n1p9 lvscan cp /etc/crypttab /etc/crypttab.old vi /etc/crypttab (replaced the wrong /dev/disk/by-id/... path with the absolute partition path /dev/nvme0n1p9) mkinitrd (rebuilt initrd, copies the new /etc/crypptab to initrd filesystem) exit chroot reboot ==> system now asks for password to unlock encrypted partition and boots as expected after password entry. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Chris Scheible changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |http://bugzilla.opensuse.or | |g/show_bug.cgi?id=1000454 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.