Hi All,

I have the above drive that has suffered a PCB malfunction. During this malfunction the Marvel chip was badly damaged. I have another PCB that appears to be the closest match and when fitted it makes all the right sounds (no knocking), but the drive stays busy. I know it's a NVRAM / ROM issue and the original has been damaged by the malfunction. My questions are a) can you re generate the ROM (like WD) from modules on the drive and b) how would you access these if the drive is busy.

And I suppose c) Is there another workaround? This drive is one half of a NAS RAID arrray, and I would really like to get this sorted...

In Terminal mode with the donor PCB I get this...
--------------------------------------------------------------------

SPW 1.5G LinkOk! SpnOk
spd: 0000 0000 0000
ADC: FFFF
DAC: 9C8E
H: +00000
SK C: 000163DB
ENG>SRV>
SvoTbl Loaded
BD

FdtTbl Loaded

*** Break at 0x37A0 [from Trap]
37A0: 0080
DBG>DBG>

----------------------------------------------------------------------

Any input would be greatly appreciated...

Regards,

Steve...

_________________
East Anglian Data Recovery Services
http://www.eadr.co.uk

"If it's your only copy - then it's not a backup!"

If you trade a REALLY WORKING solution for dealing with Barracuda unable to load OVL 1A problem without using PC3K or SD , I'll help you.

NOTE : FOR DATA RECOVERY !! (if I would have simply re-used the drive , I can put a fresh FW on it in SECONDS)

Connect LED to the PCB or monitor the computer HDD LED for blinking. Tell us the error code. For example 3 long and 11 short blinks mean 3B.

There is NO LED error until the drive stays busy this way otherwise terminal log would have been different !

Agree. LED blinking comes with "LED XX" message in terminal.

Then put jumper for POIS and use VTOOL or WCUBE to figure out what is going wrong.