A few months ago I set full disk encryption during installation of Ubuntu 17.10. Now, I've decided to upgrade. The upgrade ran to the end without any problems. However, after reboot I am not able to log into my encrypted disk.

Where can be the problem? I am 100% sure I press the "right keys" on the keyboard, but technically I don't know what I am writing because of "*" characters and maybe after upgrade my keyboard layout changed. I use some characters which might be somewhere else on the keyboard. What language is default after upgrade?

By the way, I've already tried Caps-lock, but still no luck.

Help will be really appreciated. I am not a fan of installing my system and all backups over and over again.

  • have you tried to mount the drive from a USB Key? You can do it via GUI in the Drives application. – luisgonzalez May 2 at 23:20
  • Thank you for reply. After few wrong attempts I got to initramfs - so in a command line. Cool. I've tested my charset (its ok), I've checked there is some key set via $ cryptsetup luksDump. So I tried to add new passphrase to my encrypted partition: $ cryptsetup luksAddKey /dev/sdb1 . But I am still getting error about wrong password. Its crazy, I know for 100% that this password was working before upgrade. – M_Ryan May 2 at 23:49
  • So... To be absolutely sure its not a typo, I've booted live CD and I've spend some time trying different passwords with: $ echo -n "blahblah" | cryptsetup luksAddKey /dev/sdaX I know I AM writing right password, I've even tested same keyboard keys using UK and US layout + in combination with caps-lock. Just to be sure. Still "No key available with this passphrase". cryptsetup luksDump /dev/sdaX shows key slot 0 as enabled. Well, so it looks like "something happened" during Ubuntu 17.10 to 18.04 upgrade and my luks partition is locked-out. Anything like that ever happened to you? – M_Ryan May 3 at 1:06
  • I upgraded from 16.04 to 18.04 and I'm having a different issue than yours. In my case it was a LUKS partition that shows another type of error. – luisgonzalez May 3 at 3:30
  • If there is no more keys than the partition is lost, isn't it? – Christopher Perrin May 3 at 16:22

Got the same issue when I have upgraded my ubuntu from 17.10 to 18.04. After lot of testing I found a solution for my problem. I just changed the keyboard layout in US and typed my password in my nativ layout (azerty). So it seems that the cryptsetup prompt is now in my nativ layout and not in US anymore. And my password was never stored in azerty layout as I thought.

Hope my solution will help you, and excuse me for my poor English.

  • This was the solution for me. Password entered at cryptsetup (17.04) was actually in the U.S. keyboard layout, after upgrading it changes to native language; thus you now have different keys to press - e.g., if you pressed " you actually entered @ when typing the password, if you pressed £ you actually entered #. Map the symbols from the native layout to the corresponding U.S. symbols. – Vix May 17 at 11:26
  • Same here. My passphrase, which I entered during installation and always thought was in sv_SE layout seems like it always was in en_US. Hence the characters that's on different keys between en_US and sv_SE needed to be typed where they would be for sv_SE. – mgor May 20 at 14:36

protected by Community May 4 at 13:09

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.