SSHD ST500LM000

[recovery]

Hello,

I have a SSHD drive, it stays in BUSY, motor is not spinning. I tried to swap the PCB with a donor, the PCB seems the cause of the problem. The terminal output seems to be very clear. I didn't encountered these hard drives until now, so I search information about the data recovery of these hard drives with PC3000. Do you have an idea of how to solve this problem?

Patient:
ST500LM000
1EJ162-038
FW: DEM9

Donor:
ST500LM000
1EJ162-071
LVD3

Terminal on patient drive:

ERROR: Flash Led 9C17 - RestoreALFTablesToDRAM Failed - could not reconstruct Anchor List

Clump Parametrics:
Clump = 0008
DataType = 003A
ModeFlag = 03
EraseCount = 3BABBBAB
EraseFailCount = 02
ProgramFailCount = 05
WeakReadCount = 0A
UncorrectableECCError = 05

---SOC PSM Command History---
Cmd#/PsmCmd Clump Offset Length LbaMid LbaLow LbaBits39To32 Options Status DestClump DestOffset
000A 0008 001E 0002 0000 001E 0000 C200 0024 C207 BD7F

0D0A 0008 0000 0020 0000 0000 0000 C200 0024 C207 BD7F

0C00 0007 1FE0 0001 0000 0000 0000 C000 0001 C207 BD7F

0B00 0007 1FC0 0001 0000 0000 0000 C000 0001 C207 BD7F

0A00 0007 1FA0 0001 0000 0000 0000 C000 0001 C207 BD7F

Flash Statistics:
BridgePSMDriverID = 0x0009
FlashID 98D7 8493 72D7
Flash Manufacturer: Toshiba19nm
Flash Capacity = 00008 GB MLC
Combo Mode

NumberOfClumps = 0x0400
LBAsPerCluster = 0x0020
LBAsPerClumpMLC = 0x4000
LBAsPerClumpSLC = 0x2000
ClustersPerClumpMLC = 0x0200
ClustersPerClumpSLC = 0x0100
DefragClumpThresholdInSectors = 0x2000
UserSLCMaxSizeInClumps = 0x0180
NumberOfPotentiallyWrittenClusters = 0x0002
DefectListRevisionKey 0x0002
SLC Clumps 0x01A7

ALFRecorder:
ReadAnchorEntry

[Amarbir[CDR-Labs]]

Hi ,
Have You Ruled Out a PCB Issue ?

[dataq]

Hi Recovery

We have two of these particular drives with no spin for some months now. Both have ruled out usual PCB type fault. It appears that it is a breakdown in communication between the Nand on the PCB and the drive. Ace have had a remote look at them and have not yet come up with a solution.

I hope this help.

Regards John

[huangmiaofang]

1: reading the original disk ROM
2: Read spare ROM
3: Load Spare disk ROM
4: Replace CAP RAP SAP
5: Load LOD, this process fails, wait one minute, do not de-energized.
6: re-power, again loaded LOD.
7: Start copying data

[dataq]

Hi

Thanks for the info.

Regards John

[Nick_TS]

Source of the post 1: reading the original disk ROM
2: Read spare ROM
3: Load Spare disk ROM
4: Replace CAP RAP SAP
5: Load LOD, this process fails, wait one minute, do not de-energized.
6: re-power, again loaded LOD.
7: Start copying data

Thank you for this procedure.

Source of the post Thanks for the info.

Regards John

Could you share with us your results?

[recovery]

I tried this procedure, I was unable to initialize the drive after step 6.

[DataMedics]

Source of the post 2: Read spare ROM
3: Load Spare disk ROM

I assume by "spare ROM" and "spare disk ROM" you're referring to the ROM of the donor PCB?

[huangmiaofang]

We need spare parts PCB, because within this drive SSD FLASH ROM contains firmware information section

[avalanche]

Any progression with this one? I've just received in a SSHD with a matching fault and about to examine it this afternoon. Have Ace provided any support?

Regards,
J

[IMP]

Its not working on ST1000LM014 as the disk is SA Locked

[avalanche]

Source of the post Its not working on ST1000LM014 as the disk is SA Locked

The ST1000LM014 donor HDD I have in is a Kahuna_5400. There appears to be full terminal and SA access on this series.

Although the donor has a good match on the model, PCB, PN and first three characters of the serial, the FW does not match. The donor PCB was incompatible to initialise the patient HDD. Trying to find a full match is proving challenging.

[IMP]

The ST1000LM014 donor HDD I have in is a Kahuna_5400. There appears to be full terminal and SA access on this series.

It does give terminal access
But does not give full SA access
Please let me know ones you solve this case

[avalanche]

Currently as things stand:

Patient:
W77....
ST1000LM014
1EJ164-040
DEMD
100731589 REV A

Donor 1:
W77....
ST1000LM014
1EJ164-040
SM28
100731589 REV A


Donor 2:
W76...
ST500LM000
1EJ162-040
DEMD
100731589 REV A

On donor 1 and 2 I have full terminal and SA access. I am able to make a full backup of the service area, and edit SMP if required.

Donor 1 PCB was used with patient ROM. The HDD would then enter BSY and does not spin up.

Donor 2 PCB was used with patient ROM. The HDD spins up and gives a terminal output I would normally associated with failed heads in a standard HDD. The HDD spins down and enters RDY. It is not possible to get terminal access by any method including trying to short the SATA read channel:

Boot 0x40M
Spin Up
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
ResponseFrame 0980 0046 00B6 3C00 0008 0000 0000 0000 0A9D 0000 0000 0000 0000 0000 0000 0000 C107 321A B7B7 31F7 C695 90A0 78AE AA1B 996F FC1E 1C85 3ABC 7205 A4B2 3BBE 7883 FFFF
FAIL Servo Op=0100 Resp=0003
0100 0000 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
ResponseFrame 08C0 0047 00B6 3BC0 0008 0000 0000 0000 0AAB 0000 0000 0000 0000 0000 0000 0000 C107 321A B7B7 31F7 C695 90A0 78AE AA1B 996F FC1E 1C85 3ABC 7205 A4B2 3BBE 7883 0014

However, I am not sure if this is due to failed heads or because it is necessary to make further alternations to the ROM to make it compatible such as the head adaptives etc. I have been asking Ace TS for confirmation on this, but I have not had a response yet.

I shall attempt the process suggested by huangmiaofang and post.

Best regards,
J

[avalanche]

It has been possible to get access to LBA values on the patient HDD. The disk is imaging. Once I have inspected the results later today I shall provide a full write up to method of recovery.