Hi everyone,

My Seagate SSHD - model Laptop Thin ST500LM000, f/w: DEM7 is death (not spin up).
I made the basic work and checked the simple elements of PCB (transil, resistors 0, cleaned contact strips, even resoldered the motor controller) - unfortunately - the drive still the same "dead".
Anyway - the same PCB somehow works - i can download the BIOS by the terminal in PC3K.
After reprogramming (or resoldered) the BIOS (by PC3K) drive remains a dead (if donor PCB has a different firmware). With the identical donor PCB (the same firmvare version) and reprogramming the BIOS disk spin up but with parameters (sn, etc.) from donor. Like identical after hot swap. Of course, can't read SA and user area......

It seems to me - that because it is hard SSHD - start the drive is very fast (before it gets started motor). To make this possible, some are some startup information must be included in ROM and NAND of the disk.

I my opinion, theoretically are there way to recovery data.

First: repaired PCB.
It may be difficult because the same PCM can be effective. If they are physical or logical errors in NAND this possibility will not be successful. Only, when any others element is damaged (fe. transistor). Further risk when resoldered critical element (bios, NAND, ASIC) to other PCB - these components can be damaged....

Second: Disable feature of SSHD.
Perhaps we can block all that SSHD (any bypass) and switch to work as a normal HDD.
In my opinion this way is the best. Question: If we can disable the NAND - how to do it ?

Third:
Replace critical startup information from own patient NAND of PCB to donor NAND of PCB.
Similar question: If we can - how to do it ?


Can someone please help ?
I thank You in advance for your help.

igen

I would start by measuring the supply voltages:

viewtopic.php?f=1&t=27790

I can help you disable the supply to the NAND, if you wish to try this.

Your photo is too dark to be useful.

_________________
A backup a day keeps DR away.

Hi Fzabkar,

I enclose a brighter picture.
rgds.

Hi!
I have two drives with similar issue. This is a Seagate SSHD LED 9Cxx issue caused the drive cannot erase NAND chip.
I still don't have a solution

Hi Saltwater,

"....Lengyel, magyar – két jó barát, együtt harcol, s issza borát..."

I hope that we can disable NAND....

rgds.

thats what I though, that you're an hungarian (judging by your nick) , although you didn't specify your location

I'm from Poland....

igen, igen

Hold the drive powered, maybe after a while the loader bypass the nand, and a motor will spins up.

Saltwater, You tried this method ? My disk all the time is death.

Yes, after a half an hour it spins up and puts drdy, but when i initialize the disk its goes back bsy. I cant read sys files over terminal at the moment.

Can you post terminal ?

I have identified what I believe to be 4 supply voltages (V1 - V4).

V4 appears to be the +3.3V supply for the NAND IC. Pin #1 is an active high enable. The regulator can be disabled by pulling this pin low. Perhaps a 100 ohm resistor between this pin and ground would be the safest way to disable this supply, or you could remove the chip completely.

_________________
A backup a day keeps DR away.

This happens because the drive is being identified from the donor's SSD.

On these drives ROM and PCB are paired to each other. To perform a proper diagnostics you need to check terminal output with the original PCB/ROM from the moment you power the drive up.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Bingo!

I'm expecting some "clump" errors there

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

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

Hi everybody,

Thank you all for your interest and response. I will try to answer to anyone.

To: Dmitri and Pcimage.

Sorry, but unfortunately i forgot to write earlier about terminal... After power up terminal is not working. Absolutely nothing. Is death. It does not respond to anything.
The only exception is reading BIOS via terminal - read correctly. In addition, after ends to read the BIOS and in such at this mode - that the reaction occurs Ctr-Z:

Bad cmd: 0x1A1A
>
Bad cmd: 0x1A1A
>

But perhaps this is a normal reaction in this mode, i don't know ...

To: Saltwater.

I kept power on over an hour and nothing..... All time disk is death (do not spin up) and only BSY....

To: Fzabkar

As you requested, I measured with a multimeter points that you described.

For comparison, here also the value for the smooth disk. They are very similar.
(white digits - data from a smooth drive, red digits - from the patient)

In accordance with your suggestion, i removed the chip LDO regulator (six pins).
Still nothing (do not spin up, BSY), but ........ the "small" difference ....
I received a message on the terminal - the following content:

ERROR: Flash Led 9C07 - Couldnt ID Flash Device
Bridge PSM Driver ID: FFFF
LbaMidWord: 8D00
LbaHighWord: 0000

Clump Parametrics:
Clump = FFEF
DataType = 00F0
ModeFlag = 00
EraseCount = 00000000
EraseFailCount = 00
ProgramFailCount = 00
WeakReadCount = 00
UncorrectableECCError = 00

---SOC PSM Command History---

Cmd#/PsmCmd Clump Offset Length LbaMid LbaLow LbaBits39To32 Options Status DestClump DestOffset
000E FFEF AF3D 5886 8D00 FFFF 0000 78DB 0080 800A 31CD

Unfortunately, the drive still does not respond to the Ctr-Z .....

rgds. for everyone

Then most likely the issue is in the SSD part of the drive. More specifically - some kind of data loss or corruption, that's the most precise diagnosis possible remotely.

It's necessary to have the drive on hands to tell exactly what happened and to estimate what can be done.
These drives are more complex to handle than the regular ones and traditional approaches are of little use with them.

_________________
• Remote RAID, NAS, SAN, VMware, DVR (CCTV), flash and tape recovery. Data recovery support.

Hi everyone, again

Has anyone any idea ?

I greet all.

No, i dont have any ide, but please PM me if you have a solution.

Oké, magyar

there were some of these i solved and working on one these days too. However, i need the drive to recover it, will not do it remotely.
Basically, i met several causes and issues which required appropriate treatment, the diagnosis is pretty hard, but not impossible.

pepe

_________________
Adatmentés - Data recovery