Only one more Seagate thread ST2000DM001

[Gortosch]

Hello I'am the new guy,

I have read through all the threads about the Baracuda ST2000DM001. But unfortunately I could not find a similar case. I'm well versed in IT and electronics, but I don't know much about hard disk technology.

The hard disk is either not recognized at all or not recognized correctly. I think it could be this S.M.A.R.T. overflow error. As I said I read a lot but nothing fits right.

The Data of the hard drive:

Code:

Model: ST2000DM001
PN: 1CH164-572
FW: CC44
Date:13214
Site: WU

Board: 100687658 REV C

When I connect the terminal interface, I get the following output:

Code:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

I push strg+z... 5 minutes later:

Code:

ASCII Diag mode

F3 T>

When I connect the terminal with isolated head connector to the pcb (I have read this in a series of "how i fix my seagate" tutorials):

Code:

Boot 0x40M
Spin Up
FAIL  Servo Op=0100 Resp=0003
0100 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 0000 0000 0000
ResponseFrame 1EC0 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 2AC5 5E86 9EBE 68C6 69C9 29EF 96BC 3D1D F1E0 17A7 0000 007F 000A 0000 FFF7 0004 0010
FAIL  Servo Op=0100 Resp=0003
0100 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 0000 0000 0000
ResponseFrame 2680 0000 0000 7FC0 0008 0000 0000 0000 FBE7 0000 0000 0000 0000 0000 0000 0000 2AC5 5E86 9EBE 68C6 69C9 29EF 96BC 3D1D F1E0 17A7 0000 007F 000A 0000 FFF7 0004 0000

Nothing happens after that.

Does anyone have any ideas? The data on the disk is semi-important. But it would not matter if they are gone. I'd rather learn something new.

I also have the EEPROM if anyone needs it for analysis.


Grüße
Sven

[northwind]

Hi Sven

It all looks normal.
Terminal output on startup is fine and the behavior with isolated heads is normal.

Can you describe exactly how the drive behaves on power on?
And what do you mean when you say the drive is not recognised correctly?

[Gortosch]

Hello Northwind,

thank you very much for your answer.

The 5 minutes are normal? Oh, I wouldn't have thought so.

The problem with the hard drive is that it is mostly not detected in windows. If this hard disk does happen to be detected, after several minutes, the disk is not properly responsive. (offline or no Partition or ...)


Grüße
Sven

[Lardman]

The long delay to be ready isn't normal but the lack of error message about it and the servo error without the hsa are. What does the smart say about the drive?

If you can bring it online long enough to clone with hddsuperclone you can go that way but you're reducing your chances of a successful recovery by a DR pro if you were considering it.

[Gortosch]

Hello Lardman,

i have read the S.M.A.R.T. values:

Code:

Boot 0x40M
Spin Up
Trans.

Spin Up
SpinOK
(P) SATA Reset

ASCII Diag mode

F3 T>/1

F3 1>N5
Att
Num  Flgs normlzd worst raw
1   000F   51     51   00000004BEED3C
3   0003   5F     5F   00000000000000
4   0032   5F     5F   00000000001512
5   0033   52     52   00000000005A60
7   000F   37     37   00001700649D53
9   0032   4C     4C   00000000005403
A   0013   64     64   00000000000000
C   0032   64     64   0000000000006E
B7   0032   64     64   00000000000000
B8   0032   51     51   00000000000013
BB   0032    1      1   00000000000C71
BC   0032   63     63   00000B000E0016
BD   003A   64     64   00000000000000
BE   0022   51     27   00056413130013
BF   0032   64     64   00000000000000
C0   0032   64     64   0000000000006C
C1   0032   1C     1C   00000000023849
C2   0022   13     3D   00001100000013
C5   0012    1      1   0000000000FB58
C6   0010    1      1   0000000000FB58
C7   003E   C8     C8   00000000000000
F0   0000   64     FD   252A2000000C2E
F1   0000   64     FD   0000006A622C98
F2   0000   64     FD   0000007AD6B3E7
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000
0   0000    0      0   00000000000000

F3 1>

Is there a list of how to interpret the values?

DR Pro is a no-go. I'm just kidding. I want to learn something.
The data on the hard drive is semi-important. When they're gone, they're gone. It doesn't matter.


Grüße
Sven

[Lardman]

Is there a list of how to interpret the values?

It easier just to grab in in crystaldisk or similar, it will do that for you.

You may find this recent post useful.
https://groups.google.com/g/datarecoverycertification/c/VCtmpmXRoLM , cloning is still recommended.

[Gortosch]

Hi Lardman,

It easier just to grab in in crystaldisk or similar, it will do that for you.

Thank you very much.
But how can I import the values into CrystalDiskInfo?

Thank you for the link I will read through the same. But the thread looks exactly like my problem.


Grüße
Sven

[maximus]

For the SMART attributes you can search online. Here is a basic understanding of the attributes: https://en.wikipedia.org/wiki/S.M.A.R.T.

Usually the most important ones are 5 (Reallocated Sectors Count) and C5 (Current Pending Sector Count). In your case:

Reallocated Sectors Count = 0x5A60 = 23,136
Current Pending Sector Count = 0xFB58 = 64,344

This certainly indicates the drive is failing, and given the nature of these drives probably has media damage that is only going to get worse.

[grevan]

You may find this recent post useful.
https://groups.google.com/g/datarecoverycertification/c/VCtmpmXRoLM , cloning is still recommended.

[/quote]
Does anybody know who moderates this Group? I requested to join a week ago but no answer. Thanks.

[LarrySabo]

Scott Moulton. Did you provide the description of your interest, as requested here: https://groups.google.com/g/datarecover ... tion/about

[grevan]

Hi Larry, yes, I wrote some lines.
Thanks