Remote help - two modules bad - WD1600AAJS

[ddd123]

Hello

We look for remote help
we have SD tools,

in SA are bad RBBlist

Please contact me via PM, who can help us remotely
The drive cannot read

[visz]

maybe jared can help you on this

[data-medics]

Try disabling head 0 in RAM, soft reset the drive, then re-enable head 0 and see if you get sector access.

[data-medics]

Hold on, I'm researching that specific model now.

[pcimage]

I think these only have one head.

[Dmitri]

We look for remote help
we have SD tools,

in SA are bad RBBlist

Please contact me via PM, who can help us remotely

According to what I see on the picture, I believe I'd be able to help, but using PC-3000, not SD.

If I recall correctly, module 6F is unimportant, but module 32 is a part of the microprogram.

I have no idea what SD is capable of, but can you do the following:

It would be good to check each head in the user zone. If one head is dead, then drive won't start reading on its own.
Can you build a head map in the user zone and check reading for each head individually in the user zone?


I also do not recall exactly right away and can't check atm, but mod 32 can be the RELO-list. If it's unreadable, then translator will not work.
If this assumption is correct, then you can take mod 32 from a drive of the same model (check that its size is the same), write it to both copies, clear it and then attempt to start reading.

Remember that each attempt to write into SA is dangerous. But considering the tool limitations, I do not see another way for now.
So before doing anything, backup everything you can from the SA!

Everything above also presumes that you know your tool well, have an experience with similar operations and understand what you're doing (especially considering that I'm suggesting blindly, without any experience with SD).

[ddd123]

drive has only one head

we have also #32 module from donor

[pcimage]

Mod 32 is the Relo list.

As Dmitri suggested, write it from donor then clear it. Then check it.

If the writes don't stick then you either have writing issues with the head (unlikely) or bads in the SA (more likely).

That being the case, you'll either have to modify the SA dir to relocate the module to a clean area, or smart hot swap.

Again, I'm looking at the procedure from the point of view of a pc3k user.