Maxtor Diamond Max 8 not detected in Bios

[Serville]

Guys, I really need some help. I was helping a friend backing up his data with Ghost when suddenly the system crashed and his Maxtor Diamond Max 8 40GB could not be detected anymore in Bios.
Using Maxtor Powermax, it detects as N40P and Smart Failure. Using MHDD, it said "Firmware Corrupted". Is this really a firmware issue or what ? I heard that a firmware corruption will still be detected in Bios as N40P. This one is not detected at all by Bios, but Maxtor utility and MHDD still detects it. The drive is still spinning normally (no clicking sound, etc)
Fyi, everything went well before the crash without a sympthom of hardware failure or bad sectors.

Now, I have downloaded HDD Repair 2.0, and Maxtor 6E040L0 NAR61EA0.rar from the download section.
It is exactly the same drive 40GB NAR61EAO, so I suppose the file can be used, right ?
Question is I have no clue what to do after running HDD Repair 2.0. No manual either.
Can someone help me with some instructions ?
Data recovery is not important. I just feel bad it happened when I was using it (after 4 years without a problem), so I try to bring it back to life if possible.

[datenrettung]

probably G-List and DMCS corrupted

[BlackST]

If you don't know how N40p work ask someone to do it 1-on-1 . P.s. when these drives fail, likely end of life reached. Value of drive = 5/10$. Use as doorstop, paperweight, brick...

[BlackST]

P.s. If you touch some mods on the drive it will do more damage. Ask a pro near you to put a fresh fw and selfscan it. Likely it will end cut at 30 GB. But 'utilizable'. Maybe not. This will cost few bucks, usually. NO, 'SELFSCAN' in hddrepair doesn't work for your drive.

[HDD Spaz]

If firmware has failed on this it's because of other issues with the drive. Once repaired should not be used again. Repair is only for data recovery. Why waste time and effort on a drive with no data and is worthless?

[BlackST]

I disagree about reliability. Selfscanned drives after fw repair years ago and still working...

[rameez]

I agree with Blackst .

[seeprakash]

Serville,

This seems to be a typical firmware issue with maxtor drives.

Is the data on the drive important ???? ... if yes don't try hd repair 2.0.

Prerequisite for using HD Repair 2.0 is you need good knowledge of HDD firmware.
Do some research and googling :- )

HDDs will have small OS of their own which is called "Firmware".
A HDD works in conjunction with PCB card, Hard disk assembly.

HD repair can only read some of the modules in the firmware zone of the HDD.
It can correct the header's of the modules but if the module it self corrupt it cant repiar it.

First place the HDD in safe mode by putting jumper to the first two pins when placed horizantally near the 40 pin connector [.............][_ : : :] [. . . .]


On the HD Repair screen :

1)Click on execute select the LDR file which you have downloaded.
2)If matched your HDD spins up and you will see a ok in the below logs section
3)Take a backup of the current modules by clicking >>on get map
4)verify the current modules click> check modules
5)Make sure all the modules are ok

If you see any modules as failed try replacing them (right click write).

Cheers,

[BlackST]

@seeprakash... have you heard about adaptive data ? NO.
IF you replace a failing error list you have to scan drive for logical defects again and fix the rest.
IF you touch adaptives the drive won't work anymore after power off/on and you'll have to rebuild the SA again
IF the surface is worn it won't revive the drive.
How do you check good/bad module with that hddrepair 2.0 i.e. there's trash in the middle of a module?
It's definitely not for newbies even with free software found on the net. I think even in Wikipedia you find how to make napalm...
A.Y.O.R.

[seeprakash]

BlackST/All,

I mentioned in my response Prerequisite for using HD Repair 2.0 is "Good Knowledge sorry solid knowledge of HDD firmware". There is a caution also mentioned not to use HD Repair if the Data is critical.

After all if one knows firmware structure properly they should be replacing what is required otherwise they shd send it to we DR Pros.

FYI:I am continuing my research on HD Repair 2.0 ,in the timespan I will post my experiences/lessons learnt using HD Repair as a Doc so that it helps someone who is in need :- )

Cheers,

[BlackST]

FYI:I am continuing my research on HD Repair 2.0 ,in the timespan I will post my experiences/lessons learnt using HD Repair as a Doc so that it helps someone who is in need :- )

Good luck... that program made so many damages, either in expert than newbie hands, so maybe some experiment is worth.

[Serville]

I got wrong. The bios actually detects it as N40P, but the screen was scrolling so fast and I couldn't see it clearly.
I know that my friend could simply buy a new hd, but that is not the point why I'm so persisting on repairing this hd.
My point is, the hd has run for 4 years without a problem, and suddenly when I helped him back up his data, the hd got damaged. So, I just tried to show some responsibilty here to fix it, if I can.
I explained it to my friend, and he has no problem. He has bought WD 160GB drive as replacement.
But still, I feel a little upset. And I still tried to revive the hd, if that is possible.
In the process of fixing it, I realize I might do more damage to it, and I don't care. My friend also doesn't care.
For me, it is just an experiment to satisfy my own curiosity. Nothing more.
If failed and the drive is dead, let it happen .

Seeprakash,
I followed your instruction. I found 3 modules got damaged, but when I choose to write them, the program asked for a BIN file which I don't have (eventhough I have loaded/executed the LDR file previously). What is this BIN file? I thought I only needed the LDR file. Could you explain this , or where I could find them ? Thanks.

I attach the "check structure" screen where shown the 3 damaged modules (1C, 1E & 23).




I

Attachments

[BlackST]

No comment.

[Steve]

No comment.

But that in itself was a comment

[seeprakash]

@BlackST:

I consider & know you are one of the best in this entire hddguru.
Your comments and suggestions are of high quality,I respect your knowledge.

Serville:

Try to get a donor hdd of the same model and firmware as the patient hdd.
Make copies of the modules by right clicking on the modules needed.

I suggest please read some docs realated to hdd firmware or the PC3000 docs specifically the maxtor section before you venture into any adventure :- )

Document each step what you do & the results.

Cheers,

[irecover]

HEY,
if you have problems with your loss data... maybe i can try.. it to recover it.. all those have problem in (bios cannot be detected,0LBA), just send to me the version,the product,firmware, all those details...( mayirecover@yahoo.com ).

[pepe]

aa, yes, to a guy with 2 posts and a yahoo email address

pepe