Recover files from corrupt file system?

[Curt]

What freeware do people recommend for recovering files from a corrupt XP
NTFS filesystem? I've tried PCInspector FileRecovery - which I've used
successfully in the past - but it hangs when it goes to scan that drive
and generates the following error:
"NT_read error
error no.121"

If I click Ignore I get:
"Access violation in module FileRecovery.exe.."

Then the program just hangs (stops responding).

I've also tried "Recover My Files" but it didn't find anything.

I ran a disk check with Western Digital's tools and it came up clean.

Thanks!

 

[socrtwo]

Try my listings:

http://www.s2services.com/simpleundeletefreeware.htm
http://www.s2services.com/fullfeaturedundeletefreeware.htm

 

[Curt]

Try my listings:

http://www.s2services.com/simpleundeletefreeware.htm
http://www.s2services.com/fullfeaturedundeletefreeware.htm

Thanks! I'll try them and report back.

 

[Curt]

Thanks! I'll try them and report back.

No luck with any of these. :-(

 

[Anonymous]

Curt submitted this idea :

What freeware do people recommend for recovering files from a corrupt XP NTFS
filesystem?

I've heard that Unstoppable Copier from
http://www.roadkil.net/unstopcp.html
has successfully completed the mission that you're describing.

 

[socrtwo]

Cool, sorry, I didn't pick that one up. I agree, it sounds like the
media is physically damaged. Unstoppable copier and CopyItAnyway
(http://www.digitalsystem.co.yu/download.html) are worth trying.
There's also a third one that I ran across of but never noted anywhere
for memory sake. So suggestions from others...?

 

[B. R. 'BeAr' Ederson]

What freeware do people recommend for recovering files from a corrupt XP
NTFS filesystem? I've tried PCInspector FileRecovery - which I've used
successfully in the past - but it hangs when it goes to scan that drive
and generates the following error:
"NT_read error
error no.121"

That's an error message built internally by the PCInspector FileRecovery
recovery program from Windows system errors, after a ReadFile Kernel32
system function call returns an error. The above mentioned error seems to
indicate a timeout while trying to access a certain file. There are several
reasons possible.

I'd suggest to boot a live Linux with NTFS drivers and try to recover
the file(s) from that system. This way file locking, driver problems,...
will not block your attempts. If the file(s) can not be read from Linux,
then either your file system is screwed or you disk is physically
damaged. (Although your test tools didn't report any problems.)

Other possible causes seem increasingly unlikely to me. But it wouldn't
hurt to remove all other drives (HD/DVD/...) and maybe even the more
resource eating cards (like TV cards and such) to exclude resource
conflicts.

Maybe you even change the HD cable to exclude transmission problems.
(The hardware test tools may only check the readability of data *inside*
the drive cache without actually copying them into the memory. - To gain
some execution speedup.)

BeAr

 

[James]

Curt leapt out of the bath and screamed "EUREKA!" before typing in
alt.comp.freeware:

No luck with any of these. :-(

You could try http://www.knoppix.org/ as a suggestion.

HTH