Known passphrase not accepted in LUKS1 harddisk

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Possible disk error occurred causing clicking noises to occur in external 
Seagate 1TB hard disk, doesn't allow me to properly mount the drive.
2. Ran the command "fsck.ext4 -cDfty -C 0 /dev/sdb1"
3. Clicking noise disappears, however, passphrase which worked previously no 
longer woks now.

What is the expected output? What do you see instead?
I expected to mount my hard disk. Instead, I see this error message while 
trying to unlock the device using the disk utility:
Error unlocking /dev/sdb1: Command-line `cryptsetup luksOpen "/dev/sdb1" 
"luks-b21a89de-2e9e-4b19-b143-4218d5c32ee8" ' exited with non-zero exit status 
2: No key available with this passphrase.
 (udisks-error-quark, 0)

What version of the product are you using? On what operating system?
Running cryptsetup 2.1.4-1-2ubuntu4 on 64-bit Ubuntu 12.04.2.

Please provide any additional information below.
Some essential data is backed-up in the drive.

Original issue reported on code.google.com by Rewarp on 12 Mar 2013 at 2:45

[GoogleCodeExporter]

Refer to the 'Backup and Data Recovery' section of the FAQ.

http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions#6._Backup_and_
Data_Recovery

Before doing anything further, make a complete copy of as much of the disk as 
can still be read.

But if you can't recover the encryption key from somewhere somehow, you're 
probably out of luck, I'm afraid.

Original comment by agk...@gmail.com on 12 Mar 2013 at 3:12

[GoogleCodeExporter]

Places you might find the key:  Backups as described in the FAQ;  Disk contents 
that went astray if there's been corruption or sector remapping;  The output of 
'dmsetup table --showkeys' run while the device was active;  Any swapfile or 
suspend-to-disk memory area that hasn't yet been wiped.

(I'm closing this because it's not a software issue.  Please use the dm-crypt 
mailing list if you want to follow-up.)

Original comment by agk...@gmail.com on 12 Mar 2013 at 3:19

• Changed state: Invalid
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

(By the way, did you really manage to run the fsck against the encrypted device 
sdb1 with force and yes options?)

Original comment by agk...@gmail.com on 12 Mar 2013 at 3:30

[GoogleCodeExporter]

Thanks for the resources. I will take it to the mailing list should I have 
further questions. I did manage to run the fsck command. The disk was not 
properly mounted due to some defect, but the passphrase was accepted to run 
fsck.

Original comment by Rewarp on 12 Mar 2013 at 4:01