ST1000LM014 SSHD PCB Replacement Issues

[DataMedics]

So I've done several Seagate SSHD PCB replacements already and I know about how to clear the NAND to get it working after transferring the ROM. However, I've got a case here that I can't seem to find a drive that's a close enough match for the code in the NAND to work with my patient ROM code. I've tried three same model/part number/FW drives but all were manufactured 4+ months after this drive and I can't find one with a closer date.

I was told on the last post of this thread about a Ace possibly having a custom ROM that can allow for wiping the NAND: https://forum.hddguru.com/viewtopic.php ... 47#p265047

Any chance I could get my hands on that custom ROM? (I know my support is currently expired, but I'm only asking for a copy of the custom ROM code)

[goooz]

hello

I had some cases like this. Please check PreAmp-ID !!
Some drives looks like all the same but they have different heads and the Kahuna solution/Donor PCB will not work.
This info is stored in NAND too.

Hope it helps


By the way:
I am searching for LVD5 PCB (ST1000LM014)

[DataMedics]

Even if I leave the donor PCB on the donor drive it won't attempt to spin up with the patient ROM code. So I just need to find a closer one unless someone has another solution here. Issue seems to be the firmware in the NAND won't play nice with the ROM code.

[AJ2008]

Some ROM will use CFW overlays, some will use DFW. You will need to use donor that uses corresponding type.

It may be possible to import RAP CAP SAP IAP from patient ROM into donor ROM using CFW overlays then use Kahuna patch to flush NAND.

[digitalsupport]

Any terminal output, Flash Led or ALFTable errors ?
Have you tried to make a hybrid rom as AJ2008 suggested ?

[DataMedics]

Source of the post Some ROM will use CFW overlays, some will use DFW. You will need to use donor that uses corresponding type.

It may be possible to import RAP CAP SAP IAP from patient ROM into donor ROM using CFW overlays then use Kahuna patch to flush NAND.

This was, somewhat helpful. After importing adaptives from patient ROM into donor ROM I'm able to get the drive to spin up and ID (with the Donor ID naturally) and I can even get into terminal. However, when I try to clear the NAND in terminal I get servo errors and then the drive reports:

Code: Select all

F3 O>I

 RECOV Servo Op=0055 Resp=0005
 RECOV Servo Op=0155 Resp=0005
 RECOV Servo Op=0055 Resp=0005
 RECOV Servo Op=0155 Resp=0005
 RECOV Servo Op=0055 Resp=0005
 RECOV Servo Op=0155 Resp=0005
Failed to load overlay 00000004
LED:000000BD FAddr:00004264
Rst 0x40M
Boot 0x40M
 Spin Up
 Trans.

Disc FW failed to load



(On subsequent power up)

Code: Select all

Failed to load overlay 00000001
LED:000000BD FAddr:00004264
Rst 0x40M
Boot 0x40M
 Spin Up
 Trans.

Disc FW failed to load


What's really odd is I can only get into terminal once, then on subsequent power-ups it instantly goes to the "Disk FW failed to load" error. I can only get back into terminal by writing the hybrid ROM code to the PCB again.

[DataMedics]

Source of the post Any terminal output, Flash Led or ALFTable errors ?

The terminal error with the donor ROM is always the same:

Code: Select all

Boot 0x40M
LED:000000EE FAddr:002579E4
LED:000000EE FAddr:002579E4


[DataMedics]

This is the terminal message with the original PCB still in place:

Code: Select all

Boot 0x40M
 Trans.

 ERROR: Flash Led 9C2A - ALF-SetupForComboMode Failed - Invalid Mode
   Clump:  FE55
   Combo Mode Bit:  0002

Clump Parametrics:
                    Clump = 012F
                 DataType = 001A
                 ModeFlag = 01
               EraseCount = 00007643
           EraseFailCount = 00
         ProgramFailCount = 00
            WeakReadCount = 00
    UncorrectableECCError = 00

---SOC PSM Command History---
 Cmd#/PsmCmd    Clump     Offset     Length     LbaMid     LbaLow   LbaBits39To32 Options   Status    DestClump  DestOffset
     0000       012F       18C8       0000       8000       2F62       0000       C000       0080       C207       AA14 

     0800       012F       18C0       0008       8000       2F5A       0000       C000       0080       C207       AA14 

     0701       0122       16E0       0020       0000       0000       0000       C000       0080       C207       AA14 

     0600       0007       1520       0001       0000       0000       0000       C000       0080       C207       AA14 

     0501       0007       1520       0001       0000       0000       0000       C000       0080       C207       AA14 

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

 ActiveClumpInfo
   Active Journal             Clump 0122   Offset 1700
   Active Anchor              Clump 0007   Offset 1520
   DType 0000   Read Cache          Clump 0326   Offset 0000
   DType 0001   Read Boot           Clump 0253   Offset 0000
   DType 0008   Dirty Write Cache   Clump 0173   Offset 0000
   DType 0009   Dirty Boot          Clump 010D   Offset 0000
   DType 0011   Clean Write Cache   Clump 0136   Offset 0000
   DType 0012   Clean Boot          Clump 00C3   Offset 0000
   DType 001A   SIM                 Clump 009B   Offset 0000
   DType 001B   DRIVEFW             Clump 0101   Offset 0000

--- ALF RFS Recorder ---

--- Recorder prints backwards: newest to oldest ---
 IARCount    Status       Clump      ClumpSentinel      FunctionOrigin
 ALFRecorder:
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   GetNewActiveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   GetNewActiveClump
   TableAdjustForMoveClump
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   ReconstructNodesInActiveClump
   GetNewActiveClump
   MakeAnErasedClumpAvailable
   EraseCondemnedClump
   TableAdjustForMoveClump
   TableAdjustForMoveClump
   TableAdjustForMoveClumpToCondemn
   EraseTableSystemClump
   EraseTableSystemClump
   EraseTableSystemClump
   WriteALFTables
   SaveNewAnchorToFlash
   AdvanceActiveAnchorPointer
   AdvanceActiveAnchorPointer
   WriteAnchorEntry
   AdvanceActiveAnchorPointer
   WriteAnchorEntry
   WriteJournalLog
   AdvanceActiveJournalPointer
   IssueALFRequest
   ReadDataFromFlash
   IssueALFRequest
   ReadDataFromFlash
   Request spin / disc table recovery


Maybe I'm totally looking in the wrong place and the PCB is fine. I'm not really sure. This SSHD architecture still baffles me at times. It's not doing any clicking or making any sounds that'd indicate head failure, it's just refusing to spin up at all with the original PCB/ROM so my suspicion immediately goes to the PCB.

[rickchbz]

hello everyone

i have the same case

at first it was status busy and after a while changed to ready, but after i follow the topic atached here by kahuna 5400 utility, i wrote the rom and it's worsed, and now it's don't spins up anymore

i have a donor drive, i replaced the heads, my pacient heads were good because my donor runs with them normaly, but now i can't returns to initial mode because this model have a nand chip, and i don't know if i must replace pcb , it won't help without the original NAND , i think so

how do i make to returns to the first state ?

i wrote the original ROM after and it also didn't work, i think that i had a unique chance , and i wasted it

[rickchbz]

after i replaced the PCB , quick data analise on pc3000, NTFS, it's worked normaly, i restore client data without none problem with nand, the nand doesn't scare me anymore


SOLVED