PC-3000 Forum

Hello everyone. Just working on my third drive with PC-3000. It is a ST3000DM001.

I have this drive that powers on and appears to Autodetect. Status registers stay BSY for around 10 seconds and then in ready state. If I leave it there around 20 seconds or so and then try to Run the utility, the drive status register stays BSY indefinitely and I get the following:

HDD ID has not been read ERROR: HDD Redyness timeout (10000). Run Utility?
It is like the drive drops off and can no longer be detected.

So I have disconnected from PC-3000 and I thought I would do a resistance test on the motor pads on the drive itslelf. With the PCB in place, I get almost 0 ohms across all pads. However if I remove the PCB, the resistance is what it is expected to be. Approx 3.2 ohms. When I test the pads on teh PCB, I definitely get 0 ohms. So i put it down to the PCB being the problem which is shorting.

Would you as a next step go and source a PCB donor?

I just want to get anyone's feedback to make sure I am on the right track as I am new to this.

Thanks.

for Seagate, you should check terminal output. also, at DSC DRD status you should check if the motor stops - Seagate drives will generally report a ready state from ROM only where heads cannot read overlays from SA - if motor has stopped probably heads are at fault.

Terminal log will help. Most likely PCB is not the issue here.

I dont understand what you mean by 'drive drops off' - unless this relates to spindle motor stopping?

Thank you for responding. When drive is in ready state, the motor is still spinning. I can tell it is for sure.
I probably should not have stated 0 ohms. It has some resistance there. But it is 0.4 ohms. It should be 2-4 ohms.
Other things I noticed. When I remove the PCB, the resistance is normal.
If PCB is on hard drive, then I get this very low resistance. But if I leave the drive unplugged for say an hour or so, the resistance returns to normal up until I plug the drive into power. So something on the PCB is causing the low resistance and takes some time to dissipate.
I am jumping on a support session tomorrow with someone from Acelab and hopefully they shed some light on this issue.
I'll report back.
Thanks.

Im sure they will give great advice to you

Thank you guys. I just thought to provide an update. Tech support did help me out. Pardon my terminology, as it turned out, I had issues with the drive in the G-List which filled up and caused the drive not to become ready. Tech support did their magic stuff and got it going. I tried following along as best I could and did learn a bit. Looked complicated but the tech guy made it look easy. Once the drive ID'd, the rest was easy.

Drive had a total of 6 heads. Head 1 was pretty bad. Customer did not want to pay for a head replacement so gave him the options and risks. I did a map scan of user profile only and made a data copy. Currently just saving the data off to another drive. Looks like I probably saved 80-90% of data.

Off on a training course in Prague in October so hope to get good at this stuff.

Appreciate your time to respond.