Comment 10 for bug 1047384

Revision history for this message
James Bennet (6-launchpad) wrote :

By the way, this can be triaged by doing the following on the next boot (if you could get access, but it was just not the key you expected i.e. in my case)

cryptsetup -y luksAddKey /dev/sda[x]
sudo cryptsetup luksRemoveKey /dev/sda[x] 0

Check with:

sudo cryptsetup luksDump /dev/sda5