Hello,

I have an old HDD as above which has died. No smoke or fireworks, it just stopped responding completely. The PCB shows no signs of damage but I found a donor drive and swapped the board over. The old drive now spins up with no nasty noises but is not recognised. I'm not sure if there's a ROM chip on this model or not.

Any advice would be much appreciated.

Mike.

No ideas? I'm wondering whether to spend any more time on this or give up entirely.

The FW code is stamped with white lettering on the bottom of the HDU chassis. These must match. Your donor PCB is probably incompatible.

_________________
http://www.datasaversllc.com

maybe post some pics of both boards. also there might be a simple fix to the dead one. Some troubleshooting could be done if you post a picture of the dead one, though of course this is no garauntee.

Thanks very much for the replies.

The FW code is the same on both drives (AASY 1310).

I would lean towards fixing the dead PCB too but cannot see any burning so don't know where to start. Pictures of the bad board attached.

Any input much appreciated.

Can you measure the following voltages?

_________________
A backup a day keeps DR away.

It's a dual MOSFET.

FDS6961A, Fairchild, Dual N-Channel Logic Level PowerTrench MOSFET, 3.5A, 30V, Rdson = 0.090 ohm:
http://www.fairchildsemi.com/ds/FD/FDS6961A.pdf

RDS035L03, dual N-channel MOSFET, 30V, 3.5A, Rohm:
http://www.khwy.net/images/product/jing ... 035l03.pdf
http://www.ec66.com/market/sheet/RDS035L03.pdf

PCB Reference Photos • Quantum Fireball Plus AS 20GB hires PCB photos:
http://malthus.zapto.org/viewtopic.php? ... 3369#p3369

_________________
A backup a day keeps DR away.

first time I have seen those chips referred to as "Cute" Spildit.

Defect list/translator is probably toast

_________________
All went well until I plugged the drive in.

Unlikely as It's original Pcb won't spinn the drive at all...Probably Pcb fault

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Many thanks for all the input. I can confirm that it is a mosfet and not a ROM chip although the lettering is a little faint. I'll check those voltages later and get back to you.

Thanks again.

Happy to take a look at no charge, as long as you pay for shipping.

If it does turn out to be PCB (I have a lot of these!) it will be a reasonable price, and I should be able to confirm if it's a Fw issue.

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

The mask ROM version of the Quantum/NEC uPD760009GJ microcontroller appears to be "101". I don't know how important it is, but does it match the version on the replacement PCB?

_________________
A backup a day keeps DR away.

1310 was the more "rare" version.


Defect list/translator was typical fault on Galaxy drives. As PCB suddenly died it's first port of call(if head/s not damaged)

_________________
All went well until I plugged the drive in.

pcimage - Thanks for the kind offer. I may well take you up on it.

fzabcar - The mask ROM version on the microcontroller is 101 on both PCBs.
Voltages are marked in red for dead PCB and blue for the donor.

Why not have some more fun and check out the UART

_________________
All went well until I plugged the drive in.

The Vcore supply is down from 2.6V to 1.5V and the Vio is down from 3.3V to 1.1V.

(I incorrectly assumed that the transistors were NPN rather than PNP, so I got the order of the inputs and outputs wrong, but the numbers are OK.)

The preamp supply (-5V) is OK.

I'll have to find my own PCB and make further measurements of my own.

I'm not sure about the ROM code. Other Quantum/NEC micros (eg uPD787012JG) have 3 ROM code digits in the same place, but I can't find a datasheet for the uPD760009GJ.

There is an error LED on the PCB, but I'm assuming yours don't flash, otherwise we would have heard from you.

FWIW, here are excerpts from a HDD IC database that shows various Quantum MCUs (including ROM code?) and motor controller ICs.

http://translate.google.com/translate?s ... edit-text=

Quantum AS Quantum D760009GJ 101 L6279 V2.4
(Quantum) LB Quantum D760006GJ 102 TDA5247
LD Quantum D760009GJ 103 L6279 V2.4
LE Quantum D760009BGJ 104 AN8411SH
LM Quantum D760006GJ 104 L6264

_________________
A backup a day keeps DR away.

What kind of errors would signal the LED?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

FWIW, here are 3 threads where end users talk about these LEDs in relation to various problems with various Quantum models:

http://webcache.googleusercontent.com/s ... 40765.html
http://webcache.googleusercontent.com/s ... p?t=313886
http://webcache.googleusercontent.com/s ... om/?p=4208

_________________
A backup a day keeps DR away.

ISTM that the MCU may be faulty. It is the only IC that uses both the Vcore and Vio supplies (apart from the motor controller which controls them).

The Vio circuit looks very similar to the application circuit in the datasheet for Panasonic's AN8428GAK motor controller combo IC which was used in other Quantum models.

The AE part is similar to the 2SB1073 PNP transistor in the application circuit, while the X17 part appears to be similar in function and pinout to the XN4502 dual NPN transistor.

My next step would be to measure the voltage across the pair of 0.68 ohm current limit resistors. It might be easier to measure the voltage between the tab of AE and the 3.3V test point. If this voltage is around 0.7V, then this would imply that the Vio supply is being overloaded by something on the Vio rail.


2SB1424, Rohm, marking AE, PNP transistor, -20V, -3A, low VCE(sat):
http://www1.futureelectronics.com/doc/R ... 4T100R.pdf

XN4502, Panasonic, dual NPN transistor, 50V, 500mA:
http://datasheet.eeworld.com.cn/pdf/PAN ... XN4502.pdf

_________________
A backup a day keeps DR away.