WD3200BPVT-22JJ5T0 ( Jamaica 4KV )

[unknown]

Hello gurus,

I have a problem with this series ( Jamaica 4KV ) hdds.
The drive spin up and calibrate and detected normally, but after few seconds the motor become very slow ( not spin down ) and the drive become un detectable.

There's a corruption in ( G-list and RBBlist ) modules, is this the only problem or there's anther problem elsewhere

thanks in advance

[deftrue]

I don't see why such corruption would affect spin velocity. Is the spindle controller hot? Have you checked coils base impedance?

[unknown]

I don't see why such corruption would affect spin velocity. Is the spindle controller hot? Have you checked coils base impedance?

No. I replaced the entire PCB from donor drive. I believe it's a common error of this family ( Jamaica 4KV ) because I have seen such a problem in several drives family.

[waqas_ali766]

these drives are called intelligent drives. when no work is going on the hdd. it reduce its motor and park heads to parking area.
if glist is damaged then u can't access data.

[unknown]

these drives are called intelligent drives. when no work is going on the hdd. it reduce its motor and park heads to parking area.

It's not even detectable not in stand by mode.

[fzabkar]

WD has a WDIDLE3 utility to disable the idle3 timer. There is also an open source Linux version, idle3ctl.

If you can't get either to run on your patient drive, then perhaps you could experiment with a working drive. I believe that the timer value is written to MOD 02. You could confirm this for yourself by running WDIDLE3 and then comparing your resource dumps before and after. You would then modify the appropriate MOD on your patient, recompute its checksum, and write it back.

[unknown]

What tools are you using ?
Maybe you should start by clearing the g-list and fixing the RBBlist ?
Check if all modules read ok and checksum is ok.

SD doctor.
I already fixed modules and write it back and the drive worked and the data on the drive has been recovered.
Thank you sir.

WD has a WDIDLE3 utility to disable the idle3 timer. There is also an open source Linux version, idle3ctl.

If you can't get either to run on your patient drive, then perhaps you could experiment with a working drive. I believe that the timer value is written to MOD 02. You could confirm this for yourself by running WDIDLE3 and then comparing your resource dumps before and after. You would then modify the appropriate MOD on your patient, recompute its checksum, and write it back.

Thank you very much for your feedback sir.