Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 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? Commented Oct 7, 2019 at 12:37
  • Keyboard works ok. I tried using 3 methods to unlock the partitions; the terminal cryptsetup command, the file manager, and the boot login screen. Commented Oct 7, 2019 at 13:18
  • Can you check the output of cryptsetup -v isLuks /dev/sdb1 and/or cryptsetup luksDump /dev/sdb1 Commented Oct 7, 2019 at 13:34
  • I've posted the commands. The full output is here: pastebin.com/cVYsvGnM Commented Oct 7, 2019 at 14:07
  • 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) Commented Oct 7, 2019 at 23:42