WD5000KS

[EC68]

my disk is

WD 5000KS
WD CAVIAR SE 16
MDL:WD5000KS-00MNB0
DATE 17 SEP 2006
DCM:HCACAJAH

PCB
2061-701383-E00 AG XS 3H18 3MNX 5 0001100 7101

donors

WD 5000KS
WD CAVIAR SE 16
MDL:WD5000KS-00MNB0
DATE 08 SEP 2006
DCM:HCACAJAH

PCB
2061-701383-E00 AG XS 3H18 205U 6 0006080 7086

when i was copying data from one disk to wd5000ks system froze..i did a reset and from then my disk appears to controller screen(jmicron)but windows cant boot with that disk connected...when i disconect the disk its ok
i managed to find a similar disk to swap pcb but it doesnt work,it doesnt even show at controlers screen(with its own pcb at least i can see the disk as a name on jmicron screen)
i was hopping that if i had a donor that similar i was going to work just fine
any ideas?

[jono-ats]

These look really close. I don't remember if these have embedded ROMs or not. If there is a separate ROM, I would try to swap it. Failing that, I'd do a hotswap.

Jon

[EC68]

is it possible to be the heads that have the problem?because pcb's so intetical should do the work(they have the same DCM so no changing rom needed),
is that right?

[jono-ats]

is it possible to be the heads that have the problem?because pcb's so intetical should do the work(they have the same DCM so no changing rom needed),
is that right?

The heads probably are bad. We've seen others in this series with bad heads and mechanicals.

But before I condemn them, I do everything else I can to be more certain. For example, I am working on a WD2500 and recovering data from 5 of the 6 heads. It is a clicker. I gained access to the LBA doing a hotswap. The donor drive isn't anywhere close to the subject drive (different part number) but they are of the same family (Hawk). Apparently, they are close enough to use. So I would think yours would be as close as practical and they should work, all things being equal.

Nonetheless, if there is a different head map (located in ROM) then clicking can occur, and that's why I would eliminate the ROM as a possible culprit.

Jon