[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-ddrescue] fill-mode vs luks encryption
From: |
Atom Smasher |
Subject: |
Re: [Bug-ddrescue] fill-mode vs luks encryption |
Date: |
Sat, 7 Jun 2014 11:13:46 +1200 (NZST) |
On Fri, 6 Jun 2014, Scott Dwyer wrote:
I am assuming that you are used to using the find/grep method. Check out
this link for more ideas that may work in your case, assuming the file
system is mountable:
http://tim.purewhite.id.au/2011/04/disk-recovery-which-files-are-damaged/
=============
no, apparently this file-system needs to be fsck'd before it can be
mounted.
The one that is likely to work the best in your case would be the one
using MD5 checksums. The idea is to make a list of all the files MD5
checksums, then use the fill mode to change the bad sectors, then make
another list of the checksums and compare the lists. Because the disk is
encrypted you won't be able to find a specific pattern like you say, but
this method looks for differences in the files themselves which won't
care what the pattern is.
============
that should work!
i can make a copy of the recovered image, and use fill-mode on one of the
copies. then fsck them both, mount them both (as read-only loop devices)
and just "diff -r" the two mounted file systems.
if i didn't have the drive space to create two images at the same time, i
could do similar with find/sha1sum, then fill-mode, then "sha1sum -c".
thanks!
--
...atom
________________________
http://atom.smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"The universe is not hostile, nor yet is it friendly.
It is simply indifferent."
-- John Hughes Holmes