Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Another Maxtor n40p problem

September 16th, 2010, 8:14

Hello dear sirs and madams,

First of all I would like to thank you for helping me with my problem. The information on this forum was pretty useful in salvaging data from my Maxtor.

I have this maxtor 6e40l0**** nar61590 etc... it showed n40p in the BIOS

I successfully loaded a clone LDR, after that it showed a lot of checksum errors in a lot of modules. The only broken (read error) module was G-List, so I replaced that one with a clone.
After these actions I could successfully create an image from the broken hard disk. Yeaaah, all my data salvaged.... but windows will still not recognize the 2 NTFS partitions on the disk.

I did everything I thought was possible; Recalculate checksum, Logical scanning, Translator recalculation etc...

My question, is it possible to restore those partitions ? If you would like more information I am happy to provide. I'll see if I can post the 'check modules' output here

Kind regards

Re: Another Maxtor n40p problem

September 16th, 2010, 8:31

If you can image the drive without bad sectors, then the problem is not with modules checksum or translator, but rather with the logical structure of the disk.

I bet you had some bad sectors when imaging; these drives are all failing now, with a tremendous number of bad sectors.
If for example the boot sector is bad, windows wont recognize it.
Better to use sw to scan the image and recover your data like that.

Dont use this drive any longer, its going to fail rather sooner than later.

Dobre

Re: Another Maxtor n40p problem

September 16th, 2010, 8:55

Strangely enough, the number of bad sectors in the image is rather 'normal'. The image I created is very healthy, 90% data recovered (as far as I know). The only thing is, I need some exchange data, i think only recoverable by booting into the OS on the broken disk. (perhaps the image will help me with that)

But you might have a point that the logical structure might be broken. I will look into that, shouldn't be hard to repair...
Post a reply