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
January 10th, 2007, 12:41
Hello,
I have a Maxtor Diamondmax Plus 8 drive which I'd like to recover data from. I've ran MHDD against the drive and the ID command reports it as a MAXTOR 6E040L0 with NAR61590 firmware. From other posts I'm guessing this could indicate that the firmware maybe OK
I've done nothing else which the drive at the moment, should I run a MHDD scan against the drive or is this destructive?
The drive is recognised under linux but immediately I try and access the drive it fails with read errors.
Thanks for any help,
Muppet.
January 11th, 2007, 15:54
MHDD scan should not write data,unless you ask it to.
What does Maxtor diags say about the drive?
Can you image the drive,with say ddrescue under Linux?
January 12th, 2007, 10:23
pcimage wrote:MHDD scan should not write data,unless you ask it to.
What does Maxtor diags say about the drive?
Can you image the drive,with say ddrescue under Linux?
Thanks for the reply.
If I run Maxtor diag 4.23, the basic quick test passes on all points and after running the SMART test states that an advanced test is required. Running an advanced test results in the message saying the drive is failing and needs to be replaced. The diagnostic code returned is "ca62d770".
Under linux, I've tried various block offsets in dd, which the read always failing.
Under an MHDD scan, I get AMNF and UNC errors. These errors are not consistant and I get different results if I re-run the scan.
Thanks,
Muppet.
January 13th, 2007, 19:32
Just wanted to say that thanks to the resources on this forum (and elsewhere) I managed to piece together enough information to recover the drive and retrieve the data.
For anyone struggling, all I can say is that all the information is out there if you take the time to look for it.
Muppet.
January 14th, 2007, 4:56
Check the SMART value and tell .
January 19th, 2007, 15:27
Don`t scan in MHDD more time,because scan by MHDD,some bad sector maybe remap in Glist,sometimes maybe make Glist danger,so the driver will identify N40P in bios,and you can`t access it by normal way.
One of ways to get date is connect to PC3000 and recover data by PC3000-DE program.
January 21st, 2007, 5:35
If it is identified by this name N40P then it is a firmware problem u will need pc3000 for repair .
Powered by phpBB © phpBB Group.