Re: Is my LUKS header corrupted?
Arno Wagner <[email protected]>
| Newsgroups | gmane.linux.kernel.device-mapper.dm-crypt |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Apr 24, 2019 at 14:14:43 CEST, Michael Kjörling wrote: > On 24 Apr 2019 14:08 +0200, from [email protected] (Arno Wagner): > > 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. > > 1. would seems to me to *possibly* indicate a corrupted file system. > Running a *read-only* fsck from within that emergency mode shell may > be advised, just to see if there's significant metadata damage within > the container. Also check how the file system is mounted when the > system drops into emergency mode; read-only or read/write. Makes sense to me. 2. may be due to keymap or locale problems, especially when the test was done in that emergency shell. In that case, the LUKS header may well be fine and the filesystem within the LUKS container may be damaged instead. And that can happen on a hard power-off. Arno > > -- > Michael Kjörling • https://michael.kjorling.se • [email protected] > “The most dangerous thought that you can have as a creative person > is to think you know what you’re doing.” (Bret Victor) > _______________________________________________ > dm-crypt mailing list > [email protected] > https://www.saout.de/mailman/listinfo/dm-crypt -- Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: [email protected] 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 [email protected] https://www.saout.de/mailman/listinfo/dm-crypt