Spildit wrote:
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.
fzabkar wrote:
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.
