How to identify corrupt files after cloning a failing drive?

GinaW7

Prominent
Apr 9, 2017
4
0
510
Hi everyone,

The 500 GB hard drive on my laptop was going bad, it had about 120 bad sectors, so I set out to clone it to a new one.

I created an image of it with ddrescue, then restored the image to a larger 1 TB drive.

Out of the 500 GB drive, 600 KB could not be retrieved by ddrescue.

After restoring the image, I booted on the Windows Seven Repair Disk and ran a "CHKDSK E: /B" on the Windows partition. I didn't notice it saying anything special.

Then I opened a Windows 7 session and ran "sfc /VERIFYONLY", which said it "did not find any integrity violations". From that, can I conclude that all system files are okay? Does SFC check everything?

Then I ran a CHKDSK /B on the data partition, that talked about recovering 12 orphaned files in a folder that had created instability prior to cloning. I then tried to duplicate and open those files, which seemed to work.

What about the rest? How do I go about checking whether all my program and data files are devoid of corruption? Would simply trying to copy them do the trick, would it tell me it can't read them of something? Or is there another method? I have a ddrescue mapfile, but the methods I saw based on that seemed quite complicated... So that will be a last resort! ;o

Thank you for your help! :)
 
I'd recommend recovering the data you need and reinstalling windows and programs. If anything was unrecoverable it's hard to say what could happen. freezing, hangs, corrupt files, shutdowns, etc.

Implement a backup if you don't have one and are worried about data loss. a mirrored(raid1) drive can help keep you going in addition to that.
 

GinaW7

Prominent
Apr 9, 2017
4
0
510
Thanks, failboat, but as I said in my first message, I have done the cloning operation already. For now, the system seems stable, so I'm gonna stick with this solution until proven otherwise.

I'd quite like to know how I can pinpoint the files that were corrupted, though. I'm sure a solution must exist...