ST1000LM014 1TB SSHD - only drivers detected in Windows

[byandrej]

Hi,
I have broken disk which spins normaly and is shown in BIOS but if I:
-connected on motherboard SATA and then try to boot using live linux or other OS->infinity boot (see attached pic)
-connected using external USB connector->Disk drivers recoginzed but not shown in Disk manager or cmd diskpart

If I connect it on serial port I get following results:

Rst 0x40M
Servo Processor Is Reset.
(P) SATA Reset

Request spin / disc table recovery
ASCII Diag m
TCC:0018
ode

F3 T>
RECOV Servo Op=0900 Resp=0005

F3 T>/7
F3 7>X

Head 00 Resistance 01D4
Head 01 Resistance 01BC
Head 02 Resistance 0194
Head 03 Resistance 01A8

....(some hex code)....
DriveNativeInfo Mode Page
DriveNativeInfo Group
Byte:0192: PartNumber = 30 32 37 4A 4A 30 44 54 58
'027JJ0DTX'
Byte:019B: PartNumberWhitespacePad = 20 20 20 20 20 20 20 20
' '
Byte:01A3: PartNumberPad = 00
Byte:01A4: ProcessControlVersion = 00 00
Byte:01A6: CongenConfigurationState = 01
Byte:01A7: WrittenCount = 00
Byte:01A8: InternalSeagateModelNumber =
53 54 31 30 30 30 4C 4D 30 31 34 20 20 20 20 20
20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20
20 20 20 20 20 20 20 20
'ST1000LM014 '
Byte:01D0: BuildFlags = 00 00
Byte:01D0: Bit:0, QNR_SUPPORTED = 0
Byte:01D2: RealTimeUpdatedFlags = 08 00
Byte:01D2: Bit:3, CONGEN_READ_FROM_MEDIA = 1
Byte:01D4: CongenLastWriteCaller = 04

What do you think is head or pcb broken or do I have bad sectors?

Thank you for your help

Attachments

Linux boot error

[labtech]

High chance of bad sectors... Bad/weak head probably.
in terminal you can check SMART like this:
/1
N5
What does it show? Could you post here?

[byandrej]

Hi,
thank you for your replay.

S.M.A.R.T data - please note that I cleaned it few days ago
N5
Att
Num Flgs normlzd worst raw
1 000F 64 64 00000000000000
3 0003 63 63 00000000000000
4 0032 64 64 00000000000003
5 0033 64 64 00000000000000
7 000F 64 FD 00000000000000
9 0032 64 64 00000000000000
A 0013 64 64 00000000000000
C 0032 64 64 00000000000032
B8 0032 64 64 00000000000000
BB 0032 64 64 00000000000000
BC 0032 64 FD 00000000000000
BD 003A 64 64 00000000000000
BE 0022 41 41 00000023230023
BF 0032 64 64 00000000000000
C0 0032 64 64 00000000000004
C1 0032 64 64 00000000000003
C2 0022 23 28 00001500000023
C5 0012 64 64 00000000000000
C6 0010 64 64 00000000000000
C7 003E C8 FD 00000000000000
FE 0032 64 64 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
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000
0 0000 0 0 00000000000000

BTW, I tried to read (and download) few files using HyperTerminal and it works.

I only need to get personal key from disk I don't care if disk complity die after that.

[byandrej]

And one more question would cleaning g-list give me back access so can I clone it?

[labtech]

I think the drive is healthy.
Something logical is more likely to be going on.
No, clearing the g-list is not a good idea.

[byandrej]

Sorry for late replay. That means that only someone with proper hw (like PC-3000) can fix it?

Btw. last time when it was working was, when I merge 2 or 3 partitions and format it.