Closed GoogleCodeExporter closed 9 years ago
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
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
(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
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
Original issue reported on code.google.com by
Rewarp
on 12 Mar 2013 at 2:45