PC-3000 Forum

Hi,
I've this HDD:
Model : WDC WD10EAVS-00D7B1
Serial : WD-WCAU4C556973
Firmware : 01.01A01
Capacity : 1 Tb (1 953 525 168)

ROM Modules:
ROM version............................. : 05.CVE
ROM F/W version......................... : 000500CV
Overlay F/W version..................... : 05.CVE
Servo F/W version....................... : 04.3G

After an heads swap i managed to get access to the disk. I can read the HDD ID correctly and in the utility I see the heads map as follows: 2, 3, 4, 5, 6, 7.
Donor had the same head map so I think it's correct.

I created a task but every sector I try to read gives instantly an error reading and the sector turns black.
In the Data Extractor the heads map builded is: 0, 1, 2, 3, 4, 5.
I don't know why this happens.
How can I get the drive to correctly read the sectors?

2, 3, 4, 5, 6, 7 is the physical map, 0, 1, 2, 3, 4, 5 is the logical one. Totally normal to see that.

I'd start by opening up the modules table and run a test of all modules. It's likely that some necessary module is damaged. Hopefully, it can be repaired by composite read & replace or if it's level B just replaced by a donor.

I would like to add that the donor can be not fully compatible, and it can be necessary to change the head map in RAM: http://blog.acelab.eu.com/ram-head- ... -case.html
Also, since the original heads were bad, the drive can have the Slow Responding issue, solve it as well: http://blog.acelab.eu.com/pc-3000-h ... oblem.html

Just noticed your post. It may be too late to help but in the future try to modify RAM headmap to just head 0 or 1. Often a bad or weak head can interrupt the proper loading of translator, hence the inability to read any sector. After initialization, modify RAM headmap again to include all heads and see what happens. I've had several cases like this so I know it's an issue.

I encountered the exact same issue.. the fix was very simple, just had to clean the connection on PCB > to the heads (the part that connects the heads to the PCB), it was VERY dirty.. after cleaning it the drive started reading logically without an issue. Hope it helps!

murphman, we've all been thinking that contact clearing was done already