On Mon, 10 Jun 2013 11:05:04 +0200
Daniel Bauer
I'm on a OS 12.3 with the latest updates applied. Since an "update .accident" (see description below between asterisk lines) there seems to be kind of a problem with mounting the encrypted disks at boot, the disk that contains the encrypted LVM with /, /home and swap.
Here is what is going on: Your LVM is being decrypted and opened in the "initrd". Opening assigns a virtual device, probably "/dev/mapper/cr_something". You can use "ls /dev/mapper" to see what that actually is. What has happened, is that the virtual device name being used in the "initrd" is different from that given in "/etc/crypttab". Because of this, "systemd" does not recognize that the crypto device has already been setup. How did this happen? When you did those "repairs", you manually setup the crypto for the device, using "cryptsetup". And you used a shorter name, perhaps "cr_lvm" or "cr_sda2" because it is easier to type. That shorter name got into the "initrd" that you built. Simple fix: work out what virtual device name is being used, and change "/etc/crypttab" to use that name. Change only the virtual name (currently "cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part2). Do not change the device name (the part that begins "/dev") on that line. Reboot to check that it is fixed. Harder fix: Redo your earlier "repairs", but use the full device name from "/etc/crypttab" in your "cryptsetup" command. This is hard to do, because you cannot access "crypttab" until you have done the cryptosetup. The simple fix is good enough. There's no need to do it the hard way. The virtual device name has no intrinsic meaning, so anything works. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org