Seagate ST2000MD001 2tb hdd shows 3.86gb

[Kishore22]

Seagate st2000dm001-1er164 cc43 firmware 2tb hdd shows 128gb
Any solution to recover data. Suddenly my HDD stops working
Not recognized in BIOS but shows in Windows as 128gb not initialized

[data-medics]

I think we already discussed this topic here: https://www.data-medics.com/forum/seaga ... t1845.html

Not likely a DIY case.

[jono-ats]

Most likely bad heads. Is the drive still spinning?

[colanco]

Most likely bad heads. Is the drive still spinning?

According to the post in the forum of data-medics

"No clicking sounds but it's spins continuously"

I would say a head problem is unlikely

[jono-ats]

Most likely bad heads. Is the drive still spinning?

According to the post in the forum of data-medics

"No clicking sounds but it's spins continuously"

I would say a head problem is unlikely

You are right -- I thought the original problem was the 3.86 GB message -- but this poster is describing a different problem (shows 128 GB). Assuming it is still spinning.

[fzabkar]

I carved out the following Identify Device block from a Brinks ROM. I don't understand how Windows arrives at a capacity of 128GiB.

Code:

Offset(d) 00   01   02   03   04   05   06   07   08   09

00000000  0C5A 3FFF C837 0010 0000 0000 003F 0000 0000 0000  .Z?ÿÈ7.......?......
00000010  2020 2020 2020 2020 2020 2020 514E 525F 4246 5720              QNR_BFW
00000020  0000 1000 0004 2E2E 3031 2020 2020 5354 5F4D 3133  ........01    ST_M13
00000030  4651 424C 2020 2020 2020 2020 2020 2020 2020 2020  FQBL               
00000040  2020 2020 2020 2020 2020 2020 2020 8010 0000 2F00                €.../.
00000050  4000 0200 0200 0007 3FFF 0010 003F FC10 00FB 0110  @.......?ÿ...?ü..û..
00000060  715E 007B 0000 0007 0003 0078 0078 00F0 0078 0000  q^.{.......x.x.ð.x..
00000070  0000 0000 0000 0000 0000 001F 0102 0000 0000 0000  ....................
00000080  007E 001B 346B 7D01 4003 3469 3C01 4003 407F 0000  .~..4k}.@.4i<.@.@...
00000090  0000 FEFE FFFE 0000 FE00 0000 0000 0000 0000 0000  ..þþÿþ..þ...........
00000100  715E 007B 0000 0000 0000 0000 0000 0000 0000 0000  q^.{................
00000110  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000120  0000 0000 0000 0000 0000 0000 0000 0000 0001 715E  ..................q^
00000130  007B 715E 007B 2020 0002 42B6 0100 008A 3C06 3C0A  .{q^.{  ..B¶...Š<.<.
00000140  0000 07C6 0100 0800 0F78 0500 0002 0280 0000 0000  ...Æ.....x.....€....
00000150  0008 0002 0000 FE03 0050 0000 0000 0000 00A9 000B  ......þ..P.......©..
00000160  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000170  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000180  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000190  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000200  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000210  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000220  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000230  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000240  0000 0000 0000 0000 0000 0000 0000 0000 0000 0000  ....................
00000250  0000 0000 0000 0000 0000 0000                      ............

word 57 -> 0xfbfc10 x 512 bytes = 8.46 GiB
word 60 -> 0x7b715e x 512 bytes = 3.86 GiB
word 100 -> 0x7b715e x 512 bytes = 3.86 GiB

[fzabkar]

You are right -- I thought the original problem was the 3.86 GB message -- but this poster is describing a different problem (shows 128 GB).

Google seems to suggest that the two different symptoms actually reflect the same problem.

Here is one example:

http://community.covecube.com/index.php?/topic/1767-anyone-having-problems-with-seagate-8tb-archive-drive/

I run both StableBit Scanner and Drivepool on my home server. It already has two 4TB Seagate drives, but when I tried adding one of Seagate's new 8TB "archive" drives, I get nothing but problems initializing it. I've tried connecting to drive both directly to the ASUS E35M-1M Pro motherboard and also to the SYBA SYBA SI-PEX40064 controller that the 4TB drives use -- Windows Disk Management and Stablebit Scanner both report the former configuration is a 3.86 GB drive while the latter configuration is reported as 128 GB, instead of 8TB.

I suspect that the two scenarios use different drivers.

The only odd thing I can see in the Identify Device block is the absence of a checksum at the end. Technically this makes it invalid. A capacity of 128GiB would correlate with a value of 0xFFFFFFF in word 60.

[michael chiklis]

3.86 GB issue can be solved as shown in this video if is not due to mechanical problem
https://www.youtube.com/watch?v=k0hTEu9bx5A

[lcoughey]

3.86 GB issue can be solved as shown in this video if is not due to mechanical problem
https://www.youtube.com/watch?v=k0hTEu9bx5A

Has anyone ever seen this issue, as shown in the video?

[pcimage]

Can't say I have.

As I recall, only times I've seen the 3.86gb issue is when either the heads are bad or the PCB is non-native.

But no doubt I'll get flamed

[michael chiklis]

I have seen 3.86gb issue with not knocking heads only once, but i've solved the case by cleaning heads.

[HddDonorMarket]

I have 4 HDD same case.

ST2000DM001
ST31000524AS
ST31000528AS
ST31000528AS

Same Error with serial

And not connect Bootcode mode


Not possible to connect teminal. Not responding. Says serial connection problem. but i checked my connection does not any fault.

ScreenShot_20190106205555.png (19.39 KiB) Viewed 23996 times

i tried to short circuit . not working

[AlexanderXXXVI]

I have 4 HDD same case.

ScreenShot_20190106210053.png

ST2000DM001
ST31000524AS
ST31000528AS
ST31000528AS

ScreenShot_20190106210105.png

ScreenShot_20190106205516.png

ScreenShot_20190106205332.png

ScreenShot_20190106204650.png

Same Error with serial

And not connect Bootcode mode


Not possible to connect teminal. Not responding. Says serial connection problem. but i checked my connection does not any fault.

ScreenShot_20190106205555.png

i tried to short circuit . not working

What is the terminal feedback ?

[HddDonorMarket]

That was garbage HDD.
Now I have a real case with ST2000Dm001

Identifying device...
model:ST2000DM001-1CH164 firmware version:CC43 serial number:W1E1H84J


Getting detailed firmware version...
Failed to get firmware version!
Physical sector size : ..............Failed to get
physical sector size of service area : .....................................Failed to get
Number of physical heads : ..........Failed to get
Get System module information ...
ID length Description
=========================

Failed to get system module information!
Getting service area size.......
Service area size: : .................Fail
Getting list of sys files.......
Serial port error!


Terminal window empty.

Power off and on again.
And terminal mesage like this

Code:


Boot 0x40M
Spin Up
FAIL  Servo Op=0100 Resp=0007
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 1AC0 004C 03B3 4240 0008 0000 0000 0000 0D9F 0000 0000 0000 0000 0000 0000 0000 8913 7C7A FFFF 2000 E0B4 0000 0000 0000 0000 2830 0000 007F 0006 0020 001B 0004 0010
FAIL  Servo Op=0100 Resp=0007
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 2340 004E 03B3 4380 0008 0000 0000 0000 0D63 0000 0000 0000 0000 0000 0000 0000 8913 7C7A FFFF 2000 209E 0000 0000 4380 0000 4380 0000 2247 0000 0020 001A 0007 0000


3 slow cliking sound not like as head issue that I hear before.

I tried to do do in this video

3.86 GB issue can be solved as shown in this video if is not due to mechanical problem
https://www.youtube.com/watch?v=k0hTEu9bx5A

But ıts error Exchange comands step
Failed to exchange commands!

I searched forum. Cannot find more than Head Swap advice.

And dolphin Lab website says its head issue.
https://www.dolphindatalab.com/fail-servo-op0100-resp0003/


Is this Bad Head issue?

[pcimage]

Yes, it’s bad heads.

Often media damage too.

[HddDonorMarket]

Yes, it’s bad heads.

Often media damage too.

As I guessed (also afraid)
Thanks

[mhp666]

I think it's about bad heads.

Anyway to have access to the SA in these models, the first thing you have to select is the correct family.
Then unlock the firmware.
And finally exchange commands.

[colanco]

You cannot exchange commands because this is not a model with firmware or terminal locked (P/N: 1CH164)

To access the terminal you have to short-circuit the correct points or apply a Virtual Loader.

Anyway if the disk clicks (and by the terminal log) all the above is useless. Most likely bad heads

[HddDonorMarket]

Tried to short points . Result same
Also trried to isolate PCB . Result same.
Cannot access terminal also nothing. Sa , modules etc

[pcimage]

Why are you still messing with this?

You’ve already been told it’s almost certainly a heads issue, yet you’re still spinning it up and down making it click and potentially causing even more damage.