http://bugzilla.opensuse.org/show_bug.cgi?id=1165702 Bug ID: 1165702 Summary: Yast installer stores device id in crypttab vs fstab uuid breaking encryption as id's are different in live system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SLED 15 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: tneo@gmx.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- The Yast installation process reports the following devices: SDA == SSD, root SDB == SSD, home SDC == HDD, windows SDD == HDD, data SDE == HDD, data SDD is a hardware raid configuration. Both the SDB and SDD drives are encrypted and use XFS as filesystem. Upon installing openSUSE Leap or Tumbleweed, both partitions are recognized by Yast. Upon entering the passphrase Yast can successfully mount both drives. Once installation is complete booting fails as the boot process can't decrypt one drive. It reports that LUKS is not able to decrypt drive SDD1. And after a minute and a half wait the boot drops to the emergency prompt. At this point I'm not able to access the GUI. I checked my /etc/fstab configuration vs the /dev/disk/by-uuid directory and the encrypted UUID's are correct. The decryption process fails for cr-auto-1. As it turns out in /etc/crypttab there are 2 entries: cr-auto-1 /dev/sdd1 cr-auto-2 /dev/sdb1 Based upon the configuration of YAST2 installation these device ID's are correct. But when I run fdisk -l it turns out that my encrypted partition is not on SDD1, but on SDC1: SDA == SSD, root SDB == SSD, home SDC == HDD, data SDD == HDD, windows SDE == HDD, data Thus between the installation process and the live run system my device ID's changed for 2 drives while the configuration has not changed. I was able to fix this by changing the values in the crypttab, but it is not desired to have to edit this file manually. Also I think that in the crypttab file the UUID should be used to prevent this issue from happening. -- You are receiving this mail because: You are on the CC list for the bug.