Seagate st2000dm001 1ch164-301 cc24 Wrong capacity

[dndav76]

Hi, I have a problem with one of my HDDs. As a title, it is a Seagate ST2000DM001, from 2 Tb, but now, in the BIOS and in the OS it sees with a much lower capacity. This disk did not work like OS, but it contains a lot of important data, which unfortunately I do not have elsewhere. It worked very well, but suddenly it disappeared, even from the Bios. As a result of various articles read, I tried to solve it as if it were a BSY problem, but it did not solve my problem. At least now the disk is recognized, but not with its real capacity, but especially without being able to access my data, which is the only thing that I care about it. Having restored the operation with the recovery attempt via RS232, at least I got to test it with the SeaTools for Windows. Performed SMART test, OK result.
Quick and complete generic test, always with a "failed" result.
Can anyone tell me if replacing the PCB can I get my data back?
Thanks so much.

[dndav76]

Good morning and thanks for the quick reply.
Now I just hope that something serious has not happened with the record. Now I'm worried that I used the "m0,2,2,0,0,0,0,22 (Enter)" command.
I will try to contact @michael chiklis immediately
Thanks again for the answer.

[michael chiklis]

I've replied you via PM

[dndav76]

Hello
 Following the Post launched, I had contact with @michael chiklis, who confirmed what was also said by Spildit, I take this opportunity to thank them for the attention to the case, the thing has gone on, but I'm afraid it is in a negative sense.
I do a chronology, because maybe I can make the situation better understood.
HDD from nothing, it is no longer recognized by the Win7 64bit OS.
When restarted, the BIOS of my Asus Maximus VI Extreme does not recognize the disk.
I try to unlock it with RS232 and Hyper Terminal, with the known procedure for 7200.11 discs. I did not know mine is 7200.12. Attempt done by isolating the PCB from the physical disk. But from the terminal I had the white screen, any command I tried to insert. The commands used are those described in previous posts.
The disk was connected via RS232 (USB) to a notebook with Win7 and power from an external source. I tried both powering the disk before connecting it to the notebook, and later.
Since I did not see anything on the Hyper Terminal, I made several attempts. In one of the attempts I only had a screen with type:
LED: 00000047 FAddr: FFFFFFFE
LED: 00000047 FAddr: FFFFFFFE
LED: 00000047 FAddr: FFFFFFFE
Repeated 3 times with a separation line between them.
I only remember that they were with the word LED, but I'm not sure of the rest of the strings.
After I connected the disk to the PC, with the SATA cable and the disk was visible from the BIOS, but with a capacity totally different from the real 2TB.
Given the disk was recognized, but incorrectly, I tried to test with SeaTools, and as already written, SMART Test "Ok", Quick and Generic Test "Failed".
So far, it would seem to be a problem of sector allocation.
Just by doing a final test, connecting the disk via RS232 (USB) to the Notebook, starting Hyper Terminal, enter the link properties, just start the disk power (Without PCB isolation - Physical Disc), on Hyper Terminal I get out as follows:

Boot 0x40M
Spin Up
FAIL Servo Op = 0100 Resp = 0003
0100 0000
The rest all 0
ResponseFrame 1980 and then a series of hexadecimal numbers
Then again
FAIL Servo Op = 0100 Resp = 0003
0100 0000
The rest all 0
ResponseFrame 23C0 and then a series of hexadecimal numbers

The disk is not strange ticking. I hear the engine that makes 2 attempts to Boot as soon as I connect the power supply, but then it does not make any more noise. Since I have this problem, it has always behaved in this way.
Will it really be a physical problem, or maybe a PCB problem?

[dndav76]

Reflecting on the sequence of events, I think it should be a problem with the physical part, because only after connecting the complete disk, gave me that kind of error message.
But what misleads me is the fact that it makes no strange noises.

Thank you
Dndav76

[rogfanther]

As stated, it is not a pcb problem.

The way things are now, after running the 7200.11 commands, your best option for recovering the data is sending the drive to a specialized person. As you talked with him before, @michaelchiklis comes recommended from here.

There are other means to fix the drive, but as this is not a test subject, and you *need* the data, then send it to the correct place and avoid yourself more problems.

[dndav76]

I am afraid I must begin to lose hope for a real solution.

[rogfanther]

If you do not want to send the drive to someone with the tools to fix it, yes.

[dndav76]

Thanks Spildit,
  for what you said, I had already begun to make arrangements with michael chiklis. I have already bought the new disk, which I think to send along with the one with problems to michael chiklis tomorrow. Hoping that we can still do something for my data.

Thanks again for your continued attention.

[dndav76]

I will certainly publish the outcome, whatever it is. I think that certain information must be in the public domain, for the good and the common respect. The same respect I feel for those who are part of this forum. During the week I find it hard to make myself present, because of the work commitments, so I did not publish the information with michael chiklis and all the others.
Thanks again to those who have so far been interested and helped to divulge this news.

[dndav76]

Good morning,
  unfortunately the outcome of the verification made by michael chiklis, is not at all comfortable. Broken heads.

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 1AC0 0070 06CC 3F00 0008 0000 0000 0000 0E3A 0000 0000 0000 0000 0000 0000 0000 899D 6A25 9B3F AE57 4287 7511 3C43 5022 5164 CA5D 0000 007F 0004 0000 001C 0004 0000
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 2480 0073 06CC 4040 0008 0000 0000 0000 0DFF 0000 0000 0000 0000 0000 0000 0000 899D 6A25 9B3F AE57 4287 7511 3C43 5022 5164 CA5D 0000 007F 0004 0000 001B 0004 0000

To be able to try the recovery, you need a laboratory, which obviously involves some high costs and that unfortunately at this moment I can not afford.
I hope that in the future it can have this possibility.
I thank those who participated in this discussion and especially Michael Chiklis for his support.