Hitachi HDT721010SLA360 "4th Slave Hard Disc Error"

[Jenners]

Hi,

I have a problem with my HDT721010SLA360. First it was just dead, so it does not spin any more at all. Then I ordered a new PCB from HDDzone.com. I sent them a picture of my old PCB to ensure compatibility. Then I went to a professional firm which is specializing in repairs at microchip level and they swapped my old NVRAM chip to the new PCB.

Back at home my HDD is now spinning again nice and smooth without ominous noises but when I try to boot I get the error message: "4th slave hard disc error, press F1 to resume".
It needs 10-20 seconds until this message is shown. When I press F1 and go into the BIOS the HDD is recognized but has a size of 0MB. When I boot then from my main HDD Windows can't find it, neither in the explorer nor in the system management.

Will a BIOS reset of my mainboard help? Or a firmware update of the HDD?

Thanks in advance

[pcimage]

Could be that the ROM of the new PCB is incompatible with your NVRAM, or it has some sort of firmware issue, or the preamp is bad.

Any which way, it's not a DIY job any more. It's gone beyond that

[fzabkar]

@Jenners, does your PCB have a single chip at U5, or does it have both U5 and U7?

Do you still have your old PCB? If so, could we see a detailed photo of the component side? It might help to take a few measurements to determine how the PCB failed and whether the preamp is likely to have survived.

[Jenners]

@Jenners, does your PCB have a single chip at U5, or does it have both U5 and U7?

Do you still have your old PCB? If so, could we see a detailed photo of the component side? It might help to take a few measurements to determine how the PCB failed and whether the preamp is likely to have survived.

Yes there was only one chip at U5. I attached a photo of my old PCB, where the chip is off at the moment.
Assuming that the NVRAM chip is bad can I somehow rewrite the information on the chip?

Attachments

[fzabkar]

Can you measure these voltages?

TVS_regs.jpg (150.07 KiB) Viewed 10349 times

[Jenners]

Can you measure these voltages?

I added the measured voltages in black. At the Vcore I marked two points with red, where I couldn't measure any voltage, but I'm not sure if I should or if the other spots are sufficient.

Attachments

TVS_regsmeasure.jpg (89.59 KiB) Viewed 10281 times

[fzabkar]

Your multimeter is reading 11% too high. If its battery is OK, then it's time to get a new meter. Otherwise the voltages are OK.

Most preamp damage appears to be the result of an overvoltage on the +5V supply. Your PCB shows no evidence of overvoltage, so the preamp is likely to be OK.

Your "ROM" is embedded within the LSI MCU. If it's a case of incompatible ROM code, then it would be just a matter of finding a compatible PCB. That's still potentially a DIY proposition. That said, I would have thought that hddzone.com would have been able to determine whether their PCB was compatible.

[pcimage]

@Jenners, does your PCB have a single chip at U5, or does it have both U5 and U7?

Do you still have your old PCB? If so, could we see a detailed photo of the component side? It might help to take a few measurements to determine how the PCB failed and whether the preamp is likely to have survived.

Yes there was only one chip at U5. I attached a photo of my old PCB, where the chip is off at the moment.
Assuming that the NVRAM chip is bad can I somehow rewrite the information on the chip?

Do the first two lines of the white sticker match on your original/new PCB's?

[Jenners]

Do the first two lines of the white sticker match on your original/new PCB's?

Yes the first two lines do, but not the last two.

[Jenners]

Is there anything else that has to match? Like the number on the biggest chip? But I thought hddzone.com should manage it when I sent them a photo of my PCB.

[drHDD]

I believe you have problem with system modules. You need something like PC3000 to check it.

[pcimage]

I believe you have problem with system modules. You need something like PC3000 to check it.

Agree, either that or a masked "ROM" / NVRAM mismatch. Either way, you'll need proper tools to diagnose it properly.

End of the road for DIY I'm afraid

[drHDD]

Agree, either that or a masked "ROM" / NVRAM mismatch.

Drive will not spin up in this case.

[pcimage]

Agree, either that or a masked "ROM" / NVRAM mismatch.

Drive will not spin up in this case.

Yes, you're right. I missed that part in the OP.