Very slow WD20EZRX

[pclab]

Hi

I have a very, very slow HDD.
It's a Diablo3S - WD20EZRX-00D8PB0

It takes along time to get ready and ID. I could already make a full backup of the resources with much dificulty.
After I issue a command to read something (defect lists, etc) it goes BSY but eventually it reads.
I have tried the slow fix repair, change PCB and write ROM, rebuild ROM, etc.
I have compared module 47 with a rebuild one and it show me changes.
I apply module 47 and it doesn't ID.
Compared ROM with ROM rebuild, it show changes on comparison, but if I write it, no ID again....
Any ideas how to deal with this? Heads?? ROM??

Thanks

[Tomset]

Solve the problem "SlowResponding" -
clean relo-list and block error handling.

[pclab]

Hi Tomset

I have run the slowfix option but it didn't solved...

[waqas_ali766]

Hello,
You are not able to solve this problem by only one click slow fix button.
Because all company have only clear relo list and only 1 byte changed in 02 module in one button back ground.

Try to short the tv9 and tv 10 points, then power on the hdd it click two or three times. then shows you ready status.
Then enter the utility and initilize the 01 module, then it will gives you access to firmware, then open 02 module and change all byte with 00 after the last xxxxxxxxxxxxxxxxxxxx . then write it in the hdd,

Some time it not write because you not upload the 11 overlay module.
try to initialize the 11 module then upload it in ram , then write 02

after that it not show you busy.

In second case if the head is weak.
Try to change region to boot hdd from copy 1 if head 0 damaged .

Regards
Waqas Ali

[Tomset]

pclab,
Record check, before you do run the slowfix?

[pclab]

Hi Tomset

I have tried the slowfix on UDMA and on DFL-WD too. Didn't solved...

I'll try Waqas sugestion .

Thanks

[waqas_ali766]

Hello,
If you want to regenerate the ROM in Latest hard disk then Try to read regions of copy 0 and 1, then split modules from regions,

Then try to regenerate ROM from Modules which are obtained from regions. then Write ROM to PCB and then Write all modules of ROM (generated module) into the PCB.

Some time in latest hard disk, hard disk not show detection because the head map 0A module in Rom was empty. and when you check ROM it show no head is unable. due to this empty head map hard disk not show id , but gives you access to firmware , some time yes or some time no.


Regards
Waqas Ali

[data-medics]

This might be a dumb question, but after you built the ROM from SA did you write the ROM modules to it? If not it might explain why it doesn't get ready after.

[pclab]

Hi

I got the drive back to work already.
Tried to short PCB has Waqas said, etc, etc and still nothing.
As a few guys said that it should be the Slow fix repair I tried 3 or 4 times to do the slow fix repair and it finnaly got back working....
The strange was the number of times I needed to do it....
HDD imaged with a few bad sectors.
But case closed.
Hope it can help more guys.

Thank You

[waqas_ali766]

Hello
Its good to hear. that data is recovered.


Regards
Waqas Ali

[labtech]

Hi

I got the drive back to work already.
Tried to short PCB has Waqas said, etc, etc and still nothing.
As a few guys said that it should be the Slow fix repair I tried 3 or 4 times to do the slow fix repair and it finnaly got back working....
The strange was the number of times I needed to do it....
HDD imaged with a few bad sectors.
But case closed.
Hope it can help more guys.

Thank You

There is a high chance that the area occupying the relo-block module is very degraded, therefore not allowing the "write" aka the module modifications to complete. Hence, issue was persistent. Perhaps mapping the relo-block mod to another healthier area will make the drive more stable.

[pclab]

The drive is still under warranty.
The client will send it to WD.
We got the most important: Data. ehehhe

[lcoughey]

I've encountered a few cases where we had to run the slow responding fix a few times before it stuck. All is well that ends well.