www.deadharddrive.com

[TouchClarity]

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...

[sunnydreamspace]

hi,
i can handle it. it's firmware don't matching due to stay busy states. it different with WD. please feel free to contact me by email or MSN. thanks.
_________________
provide Hard drive PCB,entire drive/ Data Recovery service.... big HDD resource. talk to me immediately! sunnydreamspace@hotmail.com
skype: sunnydreamspace