PC-3000 Forum

Dears Engineers,


This HDD Western Digital, model WD1600AAJS-75M0A0 not recognizes, the engine initiates the rotation normally.

It would like to know if this problem can be on to the one electronic defect or assemble heads?

In sees picture the PC3000UDMA.


Regards,

Alexandre

Hy alexander , after the hdd startup could u heard the complete "recalibration process" ? , did u check SA structure?

Regards

Are you sure that is original PCB on the drive?

Hi, Alexandre Silveira Any news about this disk ?

What is the full code off the disk?

ZeBong wrote:Hi, Alexandre Silveira Any news about this disk ?

What is the full code off the disk?

----------------------------------------
The model WD1600AAJS-75M0A0, thanks!

Alberto wrote:Hy alexander , after the hdd startup could u heard the complete "recalibration process" ? , did u check SA structure?

Regards

--------------------------------------------
Not complete recalibration process and not check SA Structure.

Thanks!

Its strange why on a WD 160GB show only on head enable ?, and why doesnt get info from the ROM to show u Model, etc , looks like this is not the patient PCB , if u dont heard the full recalibration process, and if u get ABRT answer to read sector command , what did u get on PSV Mode?

Regards

agrree with beto... seem like it is not its Native PCB....

Cannot find what family belongs this drive to. This is unsuported model.

However you can try to do SA Structure test with selecting different families in Wd-marvell utility startup dialog.

Some family may match your drive if the utility will sucessfully read the modules.

Roustam wrote:Cannot find what family belongs this drive to. This is unsuported model.

When do you think it will be supported?

I have similar problem on WD ZEUS drive. No ID, SA is completely accessible and no errors, PCB is original, but I recieve same error as displayed in picture above:

Zone Allocation Table......HDD RAM Reading error - Device Error Detected: 'VSCE PERM OVL NOT LOADED'

I have made backups of all SA, ROM and ROM modules and SA Tracks, and can find no apparent fault. I think the fault may be with the ROM or one of the ROM modules. I have tried copying appropriate modules to donor for HotSwap but donor develops same problem.

I had several of these cases too; no solution. However, in once case it was due to an error in Rom module 47.

Dobre

I could find no solution, so I tried some things, and when I wrote mod 47 from a donor and write all SA modules then donor ROM from donor, then disk gives ID of donor and no errors. Data cannot be accessed as adaptive information has been changed. I wrote all original modules and rom modules back to patient, and problem is still there. I also believe it is because of problem in ROM module 47.