[opensuse-factory] cryptsetup in rescue as well as in dracut do not work
Hi, during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that cryptsetup open --type luks /dev/sda2 myroot ask the passphrase and then hanges around for ever. After switching back to the oS 13.2 ISO image I was able to use the same command followed by vgscan and vgchange -a y. After downloading http://download.opensuse.org/update/13.2/x86_64/dracut-037-17.6.1_17.12.1.x8... and forced installation of the old dracut the system is up and running again. In other words: both dracut of Factory as well as rescue mode of Factory are not able to handle encrypted root devices from a former 13.2. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On Friday 2015-07-03 16:44, Dr. Werner Fink wrote:
during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that
cryptsetup open --type luks /dev/sda2 myroot
ask the passphrase and then hanges around for ever. After switching back to the oS 13.2 ISO image I was able to use the same command followed by vgscan and vgchange -a y.
Are you combining dmcrypt with LVM? Because a TW VM of mine with encrypted root (but no LVM) still boots after the gcc5 update. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Jul 03, 2015 at 04:55:21PM +0200, Jan Engelhardt wrote:
On Friday 2015-07-03 16:44, Dr. Werner Fink wrote:
during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that
cryptsetup open --type luks /dev/sda2 myroot
ask the passphrase and then hanges around for ever. After switching back to the oS 13.2 ISO image I was able to use the same command followed by vgscan and vgchange -a y.
Are you combining dmcrypt with LVM?
Because a TW VM of mine with encrypted root (but no LVM) still boots after the gcc5 update.
Hmmm ... indeed this encrypted root image done by YasT2 is to be by a device mapper type as the vgscan and vgchange -a y gives the root device /dev/mapper/system-root as link to ../dm-1 and also the swap is such a link /dev/mapper/system-swap -> ../dm-2 . There is also /dev/system/swap and /dev/system/root which are used in the /etc/fstab Is this really a gcc5 triggered problem? I'm in doubt for that. Werner -- "Having a smoking section in a restaurant is like having a peeing section in a swimming pool." -- Edward Burr
On Fri, Jul 3, 2015 at 5:44 PM, Dr. Werner Fink
Hi,
during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that
cryptsetup open --type luks /dev/sda2 myroot
ask the passphrase and then hanges around for ever.
I vaguely remember having the same problem and I recall that the solution was something related to udev ... I had to manually notify it that the scanning phase was stopped, if my memory serves me well. Sorry for not being very precise, but not documented == forgotten :-( HTH, Robert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday, July 03, 2015 04:44:23 PM Dr. Werner Fink wrote:
during debugging I had done an update of dracut which had lead to a broken initrd which does not ask for passphrase anymore. After trying the rescue mode of the latest Factory ISO image I've seen that
cryptsetup open --type luks /dev/sda2 myroot
ask the passphrase and then hanges around for ever. After switching back to the oS 13.2 ISO image I was able to use the same command followed by vgscan and vgchange -a y. After downloading
I am using an encrypted LVM, and everything is still working fine after the gcc5 update. To manually open, I have been using: cryptsetup luksOpen /dev/sdb3 cr_lvm vgchange -a y and these are still working. That particular encrypted LVM was setup with 13.2, though not via the installer. I probably used "cryptsetup" directly to encrypt the partition, and then Yast partitioner to setup the LVM in the encrypted space. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Dr. Werner Fink -
Jan Engelhardt -
Neil Rickert -
Robert Munteanu