Re: [gentoo-user] Kernel upgrade and now LUKS failure.
Am 03.05.2010 18:56, schrieb Jason Dusek: I have an encrypted block device, `/dev/sda2', which is mounted as my root filesystem. I recently installed this system -- I've been away from Gentoo for awhile -- and used gentoo sources 2.6.31-r6. When the kernel upgrade rolled around, to 2.6.32-r7, I installed and rebooted and then my passphrase didn't work anymore. The error message: Command failed: No key available with this passphrase. I see something similar here. Upgraded from tuxonice-sources-2.33-r1 to -r2 on my thinkpad. I use an encrypted /home mounted by pam_mount, it reads the key from a file so there is no keyboard involved. When I login I don't get /home mounted. /var/log/messages says: pam_mount(mount.c): crypt_activate_by_passphrase: Operation not permitted but with both kernels, -r1 and -r2 I now fiddle around with downgrading cryptsetup etc. Any hints welcome, thanks. Stefan
[gentoo-user] Kernel upgrade and now LUKS failure.
I have an encrypted block device, `/dev/sda2', which is mounted as my root filesystem. I recently installed this system -- I've been away from Gentoo for awhile -- and used gentoo sources 2.6.31-r6. When the kernel upgrade rolled around, to 2.6.32-r7, I installed and rebooted and then my passphrase didn't work anymore. The error message: Command failed: No key available with this passphrase. However, rebooting with my old kernel works fine so I'm not sure what the problem is. Could it be a different version of `cryptsetup'? When the device can't be opened on boot, I have the option to drop to a shell. I try to run `cryptsetup' and I get the same error -- so maybe that's my problem? Would different versions of `cryptsetup' be incompatible with devices encrypted by older versions? That seems brittle and dangerous to me. -- Jason Dusek
Re: [gentoo-user] Kernel upgrade and now LUKS failure.
Am 03.05.2010 18:56, schrieb Jason Dusek: I have an encrypted block device, `/dev/sda2', which is mounted as my root filesystem. I recently installed this system -- I've been away from Gentoo for awhile -- and used gentoo sources 2.6.31-r6. When the kernel upgrade rolled around, to 2.6.32-r7, I installed and rebooted and then my passphrase didn't work anymore. The error message: Command failed: No key available with this passphrase. However, rebooting with my old kernel works fine so I'm not sure what the problem is. Could it be a different version of `cryptsetup'? When the device can't be opened on boot, I have the option to drop to a shell. I try to run `cryptsetup' and I get the same error -- so maybe that's my problem? Would different versions of `cryptsetup' be incompatible with devices encrypted by older versions? That seems brittle and dangerous to me. -- Jason Dusek Some rough guesses to get you started: 1. Keyboard layout specific passphrase? Do you use a non-american keyboard layout? Maybe it has not been loaded at the time you enter the passphrase. 2. Check that all necessary components (hash algorithm, block cipher, encryption algorithm) are compiled into the new kernel. Hope this helps, Florian Philipp signature.asc Description: OpenPGP digital signature
