WD5000AAKX-00ERMA0 slow - any MRT solution?

[ABBdata]

This hard drive is very slow.
I replaced the heads and it didn't help.
The patient's heads work on the donor.
MRT head tests show that the patient's heads are good (read and write) on the donor.
On the patient, with both the new heads and the original heads, only reading from head zero is possible.
Any solution?

Mr. William received no support.

Attachments

imagem.png (38.39 KiB) Viewed 396 times

[michael chiklis]

Top surface has some damages, maybe also heads parking ramp is damaged.
Check is there are visible scratches with green light.

Other possibility is that donor heads might have pretty different MRjogs compared to patient heads.
Analyze patient and donor mod 47 for MRjogs comparing.

[michael chiklis]

https://www.hddoracle.com/viewtopic.php ... ilit=MOD47

https://www.youtube.com/watch?v=bN8uwV7udtI

[fzabkar]

Could the patient PCB have a "head mimic" fault??

[michael chiklis]

Could the patient PCB have a "head mimic" fault??

I hadn't thought of that, but I think this could also be a possibility.
In that case, it would be enough to replace the PCB with the donor one and transfer the ROM.

[ABBdata]

My sincere thanks for your comments.
There really is a difference using another PCB, but even so, there isn't much progress.
Sometimes I can recognize it normally.
Sometimes I can read the modules.
I'm researching this module 47.
Based on your response about media damage, would the damage be present throughout the media?
It's hard to believe that this would be surface damage.
data is readed, but very slowly

[michael chiklis]

I think it could be MicroJogs not well matching on head 1.
Donor heads must have most close MRjogs to patient heads. If value is quite different you might see slow reading or reading with some errors, but if value is too different then it will be quite impossible to clone.

I sent you a PM with some usefull infos

[ABBdata]

MJogs patient
Head 0 = 0x0CC1
Head 1 = 0x0D58

Mjogs donor
Head 0 = 0x0C8A
Head 1 = 0x0CF5

it's not far

[ABBdata]

Strange
Original heads work fine on the donor drive.
1º head swap
Donor 1 = heading with patient heads.
Patient = clicking
2º head swap
Donor 2 = heading with patient heads.
Patient = slow, same as the originals.
I switched the donor 1 heads back to the patient drive and it continues to read the entire hard drive perfectly.
3º head swap
I switched the donor 1, heads back to the patient drive and it was clicking
Donor continues to read.

I copied the donor's adaptives to the patient.
Any more attempts?

[michael chiklis]

Go to edit ID in wd utility and tick those 2 options called "TLER" or similar.

Acelab explain this:
https://blog.acelab.eu.com/western-digi ... overy.html

Disable also SMART refresh, on bottom of TLER options.

[fzabkar]

I don't understand why microjogs should have any effect during reading. They are essential for writing because they determine the position of the write element with respect to the centre of the track.

[michael chiklis]

In acelab's opinion, Microjog values ​​that differ too much between patient and donor can cause reading difficulties.
https://blog.acelab.eu.com/pc-3000-for- ... rives.html

The acceptable difference of the values should be less than 100. If the difference of the values is more than 300
then serious problems with data reading will appear. In such case you should look for another heads stack donor.

[fzabkar]

I have read the blog, but I still don't understand why microjogs should matter during reading, as long as SA writing is switched off. Why should the drive care where the write element is located, or even if it exists at all, if it is reading a sector rather than writing it?