Timeline for LUKS: Wrong Password or Corrupt Headers?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 1, 2021 at 17:04 | history | protected | dr_ | ||
| Dec 1, 2021 at 16:58 | comment | added | dr_ | I've had the same issue with a Linux VM (VMware) hosted on a Windows 10 machine which uses a SSD. I know the password is correct because I wrote it down, and the keymap didn't matter because the password only contained numbers. I suspected corruption problems after ruling out all other possibilities. | |
| Oct 8, 2019 at 9:55 | history | edited | outtaluk | CC BY-SA 4.0 | hexdumps |
| Oct 8, 2019 at 9:51 | comment | added | outtaluk | I followed your advice from another question about using hexdump. You can see the hexdumps here if anybody's interested: mega.nz/#!QZxRDCzA!254HtfzHibAkJXcO6BcEZuoRpjLvQBXV7WjKYMgvbfs | |
| Oct 7, 2019 at 23:42 | comment | added | frostschutz | hexdump -C? it's impossible to validate a LUKS header, you can only check for obvious corruption (obvious nonrandom data where random data should be in the key material or the like) | |
| Oct 7, 2019 at 20:37 | history | edited | outtaluk | CC BY-SA 4.0 | New Info |
| Oct 7, 2019 at 14:56 | answer | added | Emmanuel Rosa | timeline score: 1 | |
| Oct 7, 2019 at 14:07 | comment | added | outtaluk | I've posted the commands. The full output is here: pastebin.com/cVYsvGnM | |
| Oct 7, 2019 at 14:01 | history | edited | outtaluk | CC BY-SA 4.0 | More Commands |
| Oct 7, 2019 at 13:34 | comment | added | Lambert | Can you check the output of cryptsetup -v isLuks /dev/sdb1 and/or cryptsetup luksDump /dev/sdb1 | |
| Oct 7, 2019 at 13:25 | history | edited | outtaluk | CC BY-SA 4.0 | added 42 characters in body |
| Oct 7, 2019 at 13:18 | comment | added | outtaluk | Keyboard works ok. I tried using 3 methods to unlock the partitions; the terminal cryptsetup command, the file manager, and the boot login screen. | |
| Oct 7, 2019 at 13:13 | history | edited | outtaluk | CC BY-SA 4.0 | Added commands |
| Oct 7, 2019 at 12:37 | comment | added | Lambert | Perhaps a failing key on the keyboard? Does the password looks correct when you just type it on a shell prompt? Can you update the question with command output of your manual take on unlocking the encrypted partitions? | |
| Oct 7, 2019 at 12:02 | history | migrated | from serverfault.com (revisions) | ||
| Oct 7, 2019 at 8:48 | history | asked | outtaluk | CC BY-SA 4.0 |