Hello everybody,
I've got a failed Seagate
ST2000DL003-9VT166 drive with a firmware version
CC32. It is not shown on an SATA controller. The failure was most likely caused by a bad powersupply (cable or ATX). Prior failure the drive often beeped (same sound when normal poweroff occured - probably head parking) and one time it failed completely.
Right after failure I've got this log (with no terminal access):
Code:
Rst 0x40M
MC Internal LPC Process
(P) SATA Reset
User Data Base 00991590
MCMainPOR: Start:
Check MCMT Version: Current
MCMainPOR: Non-Init Case
MC Seg Disc and Cache Nodes: 4011A624 40118734
Seg Write Preamble VBM start: 000010A7 end: 000010CE
Footer - start: 000010D0 end: 000010F7
Seg Read Preamble VBM - start: 000010F9 end: 00001120
Footer - start: 00001122 end: 00001149
Reconstruction: MCMT Reconstruction Start
Max number of MC segments 22E0
Nonvolatile MCMT sequence number 003A2776
[RSRS] 0995
[SW] 17B3
[SW] 17B8
[SW] 17B9
[SW] 17D4
[SW] 17D5
[SW] 1802
[SW] 1838
[SW] 186B
[SW] 1899
[RSRS] 099E
[SW] 18CC
[SW] 18F9
[SW] 191C
[SW] 1951
[SW] 197E
[SW] 1985
[SW] 198E
[SW] 1999
[SW] 19A6
[RSRS] 09A7
ProcessRWError -Read- at LBA 00054759 Sense Code=40000087
InitiateMarkPendingReallocateRequest for disc_lba: 00054759!
Reconstruction: EXCEPTION: Seg Read Fail: Status = 0000
Continuing after error
ReadFooters (Forward): Segment 09A7 StartLBA 002A3AA0 Starting Footer LBA 002A3CA8
SeqNum 003A2789 TotalUserBlocks 01D8
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Footer Status = 0001
Reconstruction: EXCEPTION: Segment Overall Sequence Number Mismatch, No Valid Footer 003A2789 003A2780
Reconstruction: ProcessIncompletelyWrittenSegment
Adds LBA/Len
2681A686/0008 2681A836/0008 2681AA46/0008 2681AB06/0008 2681ACC6/0008 2681ADF6/0008 2681AF6E/0008 2681B1A6/0008 2681B206/0008 2681B356/0008 2681B4AE/0008 2681B5BE/0008 2681BA5E/0008 2681BF0E/0008 2681C026/0008 2681C12E/0008 2681C426/0008 2681C51E/0008 2681C87E/0008 2681C936/0008 2681CB66/0008 2681CF36/0008 2681D1A6/0008 2681D28E/0008 2681D326/0008 2681D336/0008 2681D43E/0008 26A354F6/0008 26A35546/0008 26A355B6/0008 26A366BE/0008 26A36FDE/0008 26A374AE/0008 26A37736/0008 26A378DE/0008 26A379CE/0008 26A37ABE/0008 26A37CD6/0008 26A3818E/0008 26A3864E/0008 26A38776/0008 26A38896/0008 26A38EA6/0008 26A393CE/0008 26A3945E/0008 26AE180E/0008 26AE1B5E/0008 26AE1C06/0008 26AE1FCE/0008 26AE2036/0008 26AE25EE/0008 26AE29FE/0008 26AE33F6/0008 26AE35C6/0008 26AE381E/0008 26AE382E/0008 26AE41B6/0008 26AE452E/0008 26AE469E/0008
Add Count 0000003B
Rems LBA/Len
2681ACC6/0008 2681B206/0008 2681B5BE/0008 2681BA5E/0008 2681C87E/0008 2681C936/0008 2681D326/0008 26A355B6/0008 26A36FDE/0008 26A378DE/0008 26A3864E/0008 26A38776/0008 26AE1C06/0008 26AE2036/0008 26AE381E/0008 26AE469E/0008
Remove 0000 LBA 2681ACC6 End 2681ACCE
Add 0000 LBA 2681A686 End 2681A68E
Add 0001 LBA 2681A836 End 2681A83E
Add 0002 LBA 2681AA46 End 2681AA4E
Add 0003 LBA 2681AB06 End 2681AB0E
Add 0004 LBA 2681ACC6 End 2681ACCE
Reconstruction: ProcInCmptSeg: OverlapDetected: With previous Add/Rem
Remove 0001 LBA 2681B206 End 2681B20E
Add 0000 LBA 2681A686 End 2681A68E
Add 0001 LBA 2681A836 End 2681A83E
... repeats many times ...
Add 003A LBA 26AE469E End 26AE46A6
Reconstruction: ProcInCmptSeg: OverlapDetected: With previous Add/Rem
Reconstruction: Last Chance
Rst 0x40M
MC Internal LPC Process
LED:000000BD FAddr:00007E05
Some time later I was able to execute the pin shorting method and after few tries (too soon, too late, brief flash of "
F3 T>" prompt and drive hang) I've got a terminal access. From this point I have a nearly complete log of the executed actions (I will not post it here as it is redundant and around 20 MB, but I can send it, if required).
Code:
Rst 0x40M
MC Internal LPC Process
(P) SATA Reset
(P) SATA Reset
SIM Error 3005 LBA 0000000000064407 FD FC37D093
RW Error 00000080
User Data Base 00991590
No HOST FIS-ReadyStatusFlags 0002A1A5
I have tried to disable the automatic repair functions by "
/TFxx,yy,22" commands. But drive is stil unable to enable the SATA. I've tried to enable some of the debugging flags (and combinations) from "
/TF" flag list, but without success.
I was able to download ("
/Trxx,yy") probably all available system files (about 100 MB of data). BTW many of them is not listed by the "
/Ty" command. Trying to download some of them shows:
Code:
DiagError 00000024
which is I suppose "not found". But some of them hangs (?) the drive and power must be cycled. BTW One of the system files seems to contain some interesting factory logs from drive manufacturer (I think it is "
/Tr318,3"). SIM file reports size of 32 MB, but the drive will hang after about 17 MB (I don't known if this is problem coresponding with the drive failure or just some buffer overflow - but another file has over 30 MB (filled with 0xff) and gets downloaded fine).
My assumption is, that drive finds some SIM file error and refuses to continue in the boot sequence and that it is possible this error was created by shorting the read channel. The matching file from:
Code:
SIM Error 3005 LBA 0000000000064407 FD FC37D093
is (fileID=0xea, volume=3):
Code:
File Vol FD Location Size Cylinder Hd Sector
---- --- -------- ------------ -------- -------- -- ------
00ea 003 fc37d093 000000064407 00000009 00029539 01 000248
but "
/Trea,3" command returns "
DiagError 00000024" file not found error.
I have not used any of the "
/Ti" or "
/Tm" commands. But after dumping most possible SIM files I have run "
/1N1 - initialize SMART", which hangs the drive after:
Code:
Initial value of SectorAltRlistEvents is 00
Initial value of WedgeAltRlistEvents is 00
...and "
/CU3 - modify media cache", which seems to run OK, but without any other effect. By using commands "
/ARxxx" and "
/2Bxxxx,yyyy" I was able to inspect media cache area (just some random sectors). After "
/CU3" it seems to get cleared.
When I use the "User Data Base" value from drive boot (divided by
. I'm actually able to see original MBR of drive (= userspace LBA 0). Problem is that dumping byte by byte from terminal "
/ARxxx" and "
/2Byyy,yyy" with UART speed about 500 kbps would take like half a year, so my question is:
- It is possible (and how) to instruct the drive to ignore some of the errors and initialize the SATA port?
- Is my assumption, that data are mostly OK, valid?
- Does somebody have existing 0xea SIM file?
P.S. The drive has a single "
/TV40 - Nonresident GList" entry, 0x2990 "
/TV10 - P list" entries, 22 "
/TV80 - Resident Glist" entries and over 0x2900 "
/TV100 - Primary DST List" entries (all logged from console list and SIM files dump).
Thanks for any help.