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
  • 1
    Did you try to unlock manually also? Is there the same error message? Also you could have a look at the output of cryptsetup luksDump before and after conversion... Commented Nov 5, 2024 at 21:53
  • @U.Windl this is pretty manual already (the password is not human readable so i can't really type it), but yes, I tried to copy and paste the password into the prompt in the terminal. Notably cryptsetup was using /dev/tty to directly print to the terminal and capture I/O so I couldn't see what I was pasting. That might have had an effect but I think it did the same thing for both formats. I luksDumped it both ways and there weren't any complaints about errors. The format and structure was obviously different but that was about it. Commented Nov 5, 2024 at 21:58
  • You could also add a second key slot for the time of transition. Using the second slot you could re-create the first slot in LUKS2 and the see whether it works then. If so you could remove the additional slot again. Commented Nov 5, 2024 at 22:04
  • @U.Windl Luks 2 adds a "Digest" and has different fields for the keyslot. The fields that exist in both ( Salt, iterations, AF stripes) are the same. Fields that went from global to per-slot ( Ciper/Mode, hash, KDF) seem to be the same. Ther'es a new area offset that worries me a little because 32768 is either a default or a misplaced error flag. I'll look at adding a separate key. If it works it's still a problem, but a workaround is available at least. Commented Nov 5, 2024 at 22:12
  • 1
    Assuming you used a different passphrase for the second slot, I conclude that your original setup has some kind of problem. Also I think using non-printable-ASCII characters in passphrases (as you seem to have) is a bad idea. Commented Nov 5, 2024 at 22:51