Any ideas why a disc would scan perfectly (all <50Ms) in a certain area, eg LBA 450M to 500M, yet not be imaginable, forward or reverse, in:
MTools Pro
Atola
RStudio

??

Thanks

What happens when you try to image in that region?

It could be because of MHHD (If you are using it) uses the "Verify" command to scan, while actual software perfrom "Reading" of the surface, and there are many cases, where a drive can respond good in verifying but actually has dirty surface (in reading, ofcourse).

Use HDDSCAN/HDAT2/Victoria to perform the "Read" command onto the surface (Which MHDD obviously doesn't support) to get the exact idea about the disk. (Or if you already using any of them, simply change the scanning method from "Verify" to "Read").

_________________
I just hate spammers...It was a Spammer, who ruined my life!

If i try to image the region, forwards or backwards, retries or no retries (up to 32 for example) I just get errores. Not a single block is read, not even random ones.

Victoria 3.3.3 would not recognize the drive (it is SATA connected via BIOS through a SI3112 Host card, MHDD did fine) nor would HDAT2.

I am beginning to suspect the SATA host. But MT Pro and MHDD both pick it up fine...

Well, can MHDD do an ATOF of anything in that region?

Victoria ( RUS ) will detect SATA drives

Wich kind of Sector Error did u got UNC, IDNF, AMNF,ABRT

Regards

Does it click when reaching the "critical" LBA ?

Give HDDSCAN a try. It does work with SATAs. Also, you must be using victoria for DOS. Use Victoria for windows -it supports SATA. Just run a read test and you will get the actual picture.
If nothing you can do from the above, Go for Cgallery's advice. the ATOF command in MHDD actually reads the surface (not just verify) and should help you.

_________________
I just hate spammers...It was a Spammer, who ruined my life!