Hdd is dead. No action.. no spin ..no sound.

this is pcb fault. but which part is ?

there is no visible fault.

Test diode

Unfortunately diodes are O.K.

I can only recognise one diode. Which one(s) did you find?

I would also test the regulators. I can see at least 3, possibly 4 or 5.

_________________
A backup a day keeps DR away.

what does it spit out on the serial port?

I bet u have some LED 9Cxx message.

pepe

_________________
Adatmentés - Data recovery

yes, what is the terminal output ?

_________________
RAID/Server Recovery

Sorry. there is only one diode.

i have measured diode 2 monhts before...Which is regulator?

You're right Pepe.

without isolate
ERROR: Flash LED 9C1C - No clumps available - cannot get new active clump

Clump Parametrics:
Clump = 0094
DataType = 0000
ModeFlag = 01
EraseCount = 00000099
EraseFailCount = 00
ProgramFailCount = 00
WeakReadCount = 00
UncorrectableECCError = 00

---SOC PSM Command History---
Cmd#/PsmCmd Clump Offset Length LbaMid LbaLow LbaBits39To3
2 Options Status DestClump DestOffset
000A 0094 0000 0001 0000 000E 0000
8000 0021 4505 0A8B


with isolate

UncorrectableECCError = 00

---SOC PSM Command History---
Cmd#/PsmCmd Clump Offset Length LbaMid LbaLow LbaBits39To3
2 Options Status DestClump DestOffset
000A 0094 0000 0001 0000 000E 0000
8000 0021 5505 0A0A
ERROR: Flash LED 9C1C - No clumps available - cannot get new active clump

Clump Parametrics:
Clump = 0094
DataType = 0000
ModeFlag = 01
EraseCount = 00000099
EraseFailCount = 00
ProgramFailCount = 00
WeakReadCount = 00
UncorrectableECCError = 00

---SOC PSM Command History---
Cmd#/PsmCmd Clump Offset Length LbaMid LbaLow LbaBits39To3
2 Options Status DestClump DestOffset
000A 0094 0000 0001 0000 000E 0000
8000 0021 5505 0A0A

This error is not something you can easily get rid of using a few terminal commands. The code has some flaws.
I can probably help you but i need the drive in my hands.

pepe

_________________
Adatmentés - Data recovery

Just for the reference of others who may be troubleshooting an actual PCB fault, here is my guess as to the voltage test points:

_________________
A backup a day keeps DR away.

ISTM that there is some corruption (?) in the NAND flash area of the PCB. I wonder if there is some terminal command that initialises or clears the NAND cache.

Alternatively, if we were to disable the supply to the SSD section of the PCB, would the drive then continue to function as a normal HDD?

Failing that, would it make sense to transfer the "ROM" to a donor board? ISTM that the drive would then inherit the donor's cached data, but perhaps we could rewrite the cache with the patient's own data by repeatedly reading 4GB or 8GB from the end of the user area. Presumably this won't flush the donor's cached PCB data to the patient's platters.

_________________
A backup a day keeps DR away.

since the fw hangs due to sompe programming flaw there is no terminal command you could get it alive with.

pepe

_________________
Adatmentés - Data recovery

So, get a donor PCB, initialise its SSD cache via terminal (?) or some other way, then transfer the patient's "ROM".

_________________
A backup a day keeps DR away.

good idea, but won't work.

_________________
Adatmentés - Data recovery

Same issue


I have a donor PCB. Removed Rom chip . And soldered to patient rom to donor PCB. But somehow drive serial seeing donors serial. I have readed ROM over donor. Serial look normal (patients serial)
Cannot access to drive
Is it possible to assist me to repair bad PCB or adjust donor PCB .

I have another 1 TB donor PCB. Tried this also. Patient drive made a weird noises.
and a 3th donor PCB in my hand. this drive working.
Patient____ST500LM00 1EJ162-070 FW:LVD1 date:14074 WU PCB:100705349 REV D 13 AUG 2013
3th donor: ST500LM00 1EJ162-070 FW:LVD1 date:14061 WU PCB:100705349 REV D 03 AUG 2013

I would measure voltages according to pictures that above

_________________
A Recovery Service In Turkey . Veri Kurtarma Türkiye https://www.digitalverikurtarma.com
Donor Drives hdddonormarket.com

drive inits from nand by default. That's why you read donor serial even after rom swap.

pepe

_________________
Adatmentés - Data recovery

I have tried with 3th donor that a working drive.


And writed patient Rom.
same . patients SN. and drive cannot initialize
transfered ROM chip phisically
Same.

Could it be head isue?
No unusual sound .
logs attached
Donor >>model:ST500LM000-1EJ162 firmware version:LVD1 serial number:W370LF84
Patient model:ST500LM000-1EJ162 firmware version:LVD1 serial number:W370LJ7J

_________________
A Recovery Service In Turkey . Veri Kurtarma Türkiye https://www.digitalverikurtarma.com
Donor Drives hdddonormarket.com

oops.
Donor drive working with patient ROM now. Full access

_________________
A Recovery Service In Turkey . Veri Kurtarma Türkiye https://www.digitalverikurtarma.com
Donor Drives hdddonormarket.com

Does that mean that all the donor's adaptives (CAP, RAP, SAP) are backed up in NAND? Does it also mean that a bad ROM can simply be substituted by any donor ROM?

Now that the donor drive is working with the patient's ROM, is there any way to force the adaptives in the donor's NAND to be refreshed from the patient's ROM? If you use PC3K/MRT to rewrite the ROM adaptives, will the drive's firmware transparently update the NAND as well?

_________________
A backup a day keeps DR away.

Tried same version 3 another different Rom.
All of them working. Accessing to drive and data. lol.
Strange discovery.
But I cannot accessed customers data yet.



I am using MRT. ROM remainig same after try modify adaptives. can anyone make it manually for me .

_________________
A Recovery Service In Turkey . Veri Kurtarma Türkiye https://www.digitalverikurtarma.com
Donor Drives hdddonormarket.com

What if you initialise the donor's NAND after the patient's ROM is installed? Will the NAND be reinitialised with the patient's adaptives? Hopefully you won't have two dead drives.

_________________
A backup a day keeps DR away.