crc fix and/or data recovery of digitus external hdd enclosure

kiwionline

Reputable
Aug 16, 2014
1
0
4,510
My old laptop (windows 7) had the motherboard die but the data was recoverable so had it put in a digitus hdd enclosure. Managed to copy some files across to my new laptop (windows 8) and after these were finished but before everything from the drive had been copied, I shut down the laptop. On start up this morning when trying to access the drive received a crc error. I was unable to directly run a fix so have been attempting the cmnd prompt route as suggested by http://www.wikihow.com/Fix-a-Cyclic-Redundancy-Check-Error. However, while the read-only options are working perfectly fine, the fix and repair options (currently running with /c and /i) keep causing an error in stage 1 after file verification is complete, large files are processed, and bad files are processed (specifically 6e74667363688b2e 2d0). Does anyone have a solution on how I might go about fixing this? Or explaining to me what this error mean?
And before anyone asks the enclosure is working for the other drive in it so I believe the external drive itself is probably not the problem.
Or if that is not possible how I might go about attempting to recovery the data off this drive? Have already tried Recuva and Roadkil (neither recognised the drive to be able to recover from). Preferable for free - or at least free check of whether or not it is possible. And before anyone asks, no the majority of the drive is not backed up anywhere - the hard copy backup I had was accidently destroyed by a friend shortly after the old laptop died and is not recoverable, and I had not yet backed everything to cloud.
EaseUS seems to be working to a point but sorting the needed from the crap so as to minimise costs it difficult due to layout, so again any other programs would be helpful.
I had been trying chkdsk x: /f /r to start with and that was crashing even earlier in the process than with /c and/or /i, and by that I mean that it didn't even finish processing the bad files or sometimes even the large files. However, thanks anyway for your suggestion.