Galaxy2D displayng corrupt ID and SN and datas

[positivebit]

Got this ST3500830ACE,
can ID and read sectors (only in pio mode)
but cloning drive also in raw recovery i have all data as "garbage".

Looks like a general corruption, of SA and DA,
anyone faced this?

Attachments

[drc]

Check pins / cable

[positivebit]

Tryed to clean contacts, tryed 2 pc3000 machine, same results.

Guessing:

- rom corrupted
- pcb faulty
- SA corrupted
- heads dirty

[unknown]

Most likely PCB.

Good luck

[Nick_CT]

Anything in terminal output?

[positivebit]

Terminal output is perfect.
Tmrw will diagnose pcb..

[pcimage]

I would bet its a bad PCB too.

Or at least a dodgy SATA connection.

[drc]

This is IDE, right? So, problem with one of the pins or solder joint to PCB... either way replacing PCB is easier if you have one on hand

[northwind]

I had the same problem. It took me 2 hours to realize this was a connections/connector issue. I saw light when I connected another drive and saw that hieroglyphic on drive's ID. It turned out to be my IDE -> Sata converter.

[positivebit]

Data recovered,happy customer,
ROM corrupted or PCB faulty was the issue.

[mr_spokk]

Data recovered,happy customer,
ROM corrupted or PCB faulty was the issue.

Must been Pcb, as this model needs the ROM to be transferred as well.

[fzabkar]

AISI, it was obviously an issue with the IDE interface.

The first clue is the fact that every second character in the model number is corrupt. The IDE bus is 16 bits wide, and each character is stored in 8 bits ...

Other clues include the number of logical sectors, ie ...

32831 = 0x803F

This number should be 0x003F, so clearly there is a single stuck bit.

You could then refer to the IDE pinout to identify the failing bit:
http://pinouts.ru/HD/IdeInternal_pinout.shtml

ISTM that DD15 (pin#18) would have been faulty. I would have checked the soldering, plus the associated resistor.