WD10EAVS-32D7B1 (Kermit) help

O

Othersteve

New member
Hey guys,

All right, total newbie here to firmware work, but I've got the first one I'm experimenting with that I think I need help with.

This drive spins up, "clicks" three times, spins down. Cannot do RAM headmap, load LDR from similar drive, or anything of the sort. I have a near match (WD10EAVS-00D7B1) from a few months prior but I cannot even get the patient drive to accept LDR in RAM.

I'm using MRT, but have been able to find information suggesting that PC-3000 had a way to edit SA regions that can supposedly prevent the drive from spinning down. I figure MRT is likely also capable of this but I'm not sure where to head next. Any suggestions?

Thanks so much! This stuff is hard! ;-)
 
pclab

pclab

Moderator
Most probably, if it clicks and spins down it mus be head problems.
Have you checked inside?
 
O

Othersteve

New member
No, I haven't, and in fact that's typically where I think I'm going to draw the line on recoveries (anything requiring disassembly). It's okay, all of the firmware stuff is all practice at the moment anyway :)

Thanks, I do very much appreciate the reply!
 
pclab

pclab

Moderator
If this is a pratice drive (and not a client drive), you can open it and be sure how it is inside, since it's already dead!
 
O

Othersteve

New member
Yeah I'll probably give that a shot... thanks for the advice on it pclab!

I'm practicing on all abandoned drives from years past... figure I'll give it a solid few months before I try anything at all significant on client stuff. :)
 
O

Othersteve

New member
So get this --

I have another one of these now in hand, similar symptoms. Slightly different model: WD10EAVS-32D7B1.

This one I'm able to provoke to ID however, by disabling H3 in ROM (heads map normally is 2,3,4,5,6,7 - so it's revised to 2,4,5,6,7 and IDs).

However, I can only read LBAs at the very start of the drive. I've even tried heads mapping and then disabling everything related to physical H3, without luck thus far. Any trick to getting later LBAs to read?

Thanks for the help guys! :)
 
O

Othersteve

New member
Just an update, it looks like module 36 on this drive is throwing errors. I tried offsetting it after reading, then writing it back to a new address, and it now shows: Read "OK", The head "Err", Check "Err"

I'm totally out of my depth here :LOL:
 
O

Othersteve

New member
Sorry -- can't edit so I have to reply again :p

So I fixed 36... I think. Read Composite, Read Copy 1, compared to a like drive and copied over header data. Computed checksum, verified, wrote back to drive. Now it shows OK across the board.

However drive still only allows very early LBA access... and nothing beyond that point.
 
You must log in or register to reply here.
Top