2. would indicate a corrupt header, but 1. is really strange. Unless Kubuntu has done something they really should not do, namely adding their own passphrase checksum, I have no idea how that behavior could happen. Unless there is some large ssd-sector caused corruption, the LUKS header should not get corrupted by powering things down. It never gets written in normal operation and there is a safety-distance to the data area. Regards, Arno On Wed, Apr 24, 2019 at 12:42:08 CEST, Greg Laun wrote: > I have a LUKS-encrypted hard drive partition that is showing the > following behavior on Kubuntu 19.04: > 1. If I enter the correct passphrase, Kubuntu drops into emergency > mode. If I enter the incorrect passphrase, Kubuntu asks for the > passphrase again. > 2. If I run cryptsetup luksOpen <target device> myName with the correct > passphrase, it tells me "No key available with this passphrase." > Does anybody know what would account for this behavior? How is > Kubuntu's UI layer able to take a different code path based on the > correct passphrase if dm-crypt no longer recognizes the passphrase? > Is it possible there are arguments to luksOpen that I can pass to have > the passphrase recognized again? > The passphrase worked 4 days ago. The machine was powered down > accidentally by an unruly toddler, but I'm not sure if that's enough to > corrupt the LUKS header. > Thanks for any help/info! > Greg > _______________________________________________ > dm-crypt mailing list > dm-crypt@xxxxxxxx > https://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@xxxxxxxxxxx GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. -- Plato If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
