ST2000LM007-1R8174 FAILED to spare00000101!

[DRNZ]

Model : ST2000LM007-1R8174
Serial : WDZ7QS9Q
Firmware : SBK2
Capacity : 2 TB (3 907 029 168)


Hi there,

I need a bit of help identifying the problem with this hard drive. Terminal output repeats FAILED to spare00000101! but if I'm quick enough I can get to a F3 T> prompt

Boot 0x80M
Rst 0x80MSrv DETCR init 0x0000
(P) SATA Reset

RAW OFF
PASS
(DOS Table) Worst Count: 00000000 At SU: FFFFFFFF NT: 00000000 OT: 00000000
(POR) Recover Secondary MCMT Opened Recovered
Starting LBA of RW Request=0000BEFE66 Length=00000660
ProcessRWError -Read- at LBA 0000BEFE8F Sense Code=43110081
ProcessRecoveryComp-2
ERC TO exceeded, orig value in us:FFFFFFFF
MS Read Fails: 05F7F330,00003300
(MC POR Duration): 00000002BE
Intel 6G->3G
Send Status: COMRESET seen
CSpd= 3Gbps
DSC
Starting LBA of RW Request=0000BE96CE Length=00000E58
ProcessRWError -Read- at LBA 0000BE98C3 Sense Code=43160080Out:
FAILED to spare00000101!

Starting LBA of RW Request=0000BE96CE Length=00000E58
ProcessRWError -Read- at LBA 0000BE98C4 Sense Code=43160080Out:
FAILED to spare00000101!

Starting LBA of RW Request=0000BE96CE Length=00000E58
ProcessRWError -Read- at LBA 0000BE98CC Sense Code=43160080Out:
FAILED to spare00000101!

Starting LBA of RW Request=0000BE96CE Length=00000E58
ProcessRWError -Read- at LBA 0000BE98F2 Sense Code=43110081
Common path start quit now ProcessRC: 00000000,00000000ReadContinuous: 00BE98F2,000002A4

[DRNZ]

I figured that the terminal was locked so unlocked via ROM mod. I can now access SMP-Flags in SysFile93 but cannot write chances back to HDD.

I read that is possible to edit SMP-Flags in RAM, is that correct?

[DRNZ]

This is what I get in logs when trying to write back SysFile93

SMP Dbl: 0x3C001000 - 0x0001FFFF (0x0000000F)
Wr SysF 3:93:0 (0/2000) err = 0x00000005

[DRNZ]

I managed to edit the SMP-flags in RAM then in SysFile93 using ATA indirect access. I can now see a file structure in data extractor. Time to start imaging.

[DRNZ]

Cloned from head 0,1,2 successfully. Head 3 is very slow at reading. Does this indicate weak heads?

[Filipp_TS]

If behavior is the same at any areas over Head3 then this Head is weak.
If some areas are reading well, but other are slowly then might be issues related to the surface condition over this particular Head3.