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