I am in the process of salvaging data from a 1 TB failing drive (asked about it in Procedure to replace a hard disk?). I have done
ddrescue from a system rescue USB with a resulting error size of 557568 B in 191 errors, probably all in
/home (I assume what it calls "errors" are not bad sectors, but consecutive sequences of them).
Now, the several guides I've seen around suggest doing
e2fsck on the new disk, and I expected this to somehow find that some files have been assigned "blank sectors/blocks", to the effect of at least knowing which files could not be saved whole. But no errors were found at all (I ran it without
-y to make sure I didn't miss anything). Now I am running it again with
-c, but at 95% no errors were found so far; I guess I have a new drive with some normal-looking files with zeroed or random pieces inside, undetectable until on day I open them with the corresponding software, or Linux Mint needs them.
Can I do anything with the old/new drives in order to obtain a list of possibly corrupted files? I don't know how many they could be, since that 191 could go across files, but at least the total size is not big; I am mostly concerned about a big bunch old family photos and videos (1+ MB each), the rest is probably irrelevant or was backed up recently.
Update: the new pass of e2fsck did give something new of which I understand nothing:
Block bitmap differences: +231216947 +(231216964--231216965) +231216970 +231217707 +231217852 +(231217870--231217871) +231218486 Fix<y>? yes Free blocks count wrong for group #7056 (497, counted=488). Fix<y>? yes Free blocks count wrong (44259598, counted=44259589). Fix<y>? yes