Barracuda 7200.12 ST31000528AS

[int0x13]

Hello, i have a faulty seagate 7200.12 HDD. Its not detected by windows anymore. It was in an external case.
DATA IS NOT IMPORTANT, JUST WANT TO FIX IT, I DONT CARE AT ALL ABOUT THE DATA.
Model is
Ive managed to detect it some times with windows, but cannot scan any sector into HDtune, all LBA are marked as bad.
Here the terminal log i have:

Code:

Rst 0x20M
(P) SATA Reset
PASS
RW: Error processing Performance Parameter File: 203C PASS
No Phy: Staggered spin bypass
InitiateMarkPendingReallocateRequest for disc_lba: 00000894
...
cut
InitiateMarkPendingReallocateRequest for disc_lba: 000008A6

I tried this:

Code:

F3 T>m0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewrite Retries = 14E8

User Partition Format   5% complete, Zone 00, Pass 00, LBA 00009A64, ErrCode 00000080, Elapsed Time 0 mins 30 secs   
Init SMART Fail
LED:000000CC FAddr:0024EE5D
...
Infinite loop

Here is the drive detailed infos:
ATA Device Properties:
Model ID ST31000528AS
Serial Number 9VP6QC5X
Revision CC44
World Wide Name 5-000C50-0204B6045
Device Type SATA-II
Parameters 1938021 cylinders, 16 heads, 63 sectors per track, 512 bytes per sector
LBA Sectors 1953525168
Physical / Logical Sector Size 512 bytes / 512 bytes
Multiple Sectors 16
Max. PIO Transfer Mode PIO 4
Max. MWDMA Transfer Mode MWDMA 2
Active MWDMA Transfer Mode MWDMA 2
Max. UDMA Transfer Mode UDMA 6
Unformatted Capacity 953870 MB
Rotational Speed 7200 RPM
ATA Standard ATA8-ACS

Physical infos:
Manufacturer Seagate
Hard Disk Name Barracuda 7200.12 1000528
Form Factor 3.5"
Formatted Capacity 1000 GB
Disks 2
Recording Surfaces 4
Physical Dimensions 146.99 x 101.6 x 26.1 mm
Max. Weight 622 g
Average Rotational Latency 4.16 ms
Rotational Speed 7200 RPM
Max. Internal Data Rate 1695 Mbit/s
Average Seek 8.5 ms
Track-To-Track Seek 1 ms
Interface SATA-II
Buffer-to-Host Data Rate 300 MB/s
Buffer Size 32 MB
Spin-Up Time 10 sec

Here are the result for the non resident G-list:

Code:

F3 T>V40
Nonresident GList                   64 entries returned
Total entries available: 86
    PBA    Len  Flags  Phy Cyl Hd  PhySctr    SFI
     77E    1     20        0   0    77E    EF4E8
     892    1     20        1   0     22    38A3D
...
cut
Nonresident GList                   22 entries returned
Total entries available: 86
    PBA    Len  Flags  Phy Cyl Hd  PhySctr    SFI
  1D2198    1     20       DD   0    35C    39B2E
  1D2F41    1     20       DB   0     25    3BD10
...
cut


[pcimage]

It has severe media issues and/or physical problems.

Not realistically repairable.

Bin it

[int0x13]

It has severe media issues and/or physical problems.

Not realistically repairable.

Bin it

Is this a try to discourage me or a real diagnostic? Without explaining it seems more to be the first. What makes you think what you said?

[Eleg]

As long as you clearly have stated that your data is not important, why would anyone discourage you?

[northwind]

It has severe media issues and/or physical problems.

Not realistically repairable.

Bin it

Is this a try to discourage me or a real diagnostic? Without explaining it seems more to be the first. What makes you think what you said?

As Eleg said, why would someone discourage you to do anything?
The terminal explains in details that your drive is not repairable in the way that you mean it.

[int0x13]

I've seen dozens of time the exact same case as mine on seagate 7200.12 drives. And i've seen an Indian Pro saying it's very easy to fix, and it's 100% sure. So yes, i think you want to discourage. I mean why would Pros help anybody for free? It's the "blackST" syndrome. There are some persons i've seen on this forum that really want to share knowledge like fzabkar and Spildit, but certainly not the the people like you that dont explain anything and just declare peremptorily that "this is not a job for you stupid amateur" or "your drive is dead, dont try to repair it".

[warnerr]

You should disassemble the drive just for fun with no expectations of truly repairing it. Maybe the platters will have grooves where the should not! Take out the heads- amazing how small it is- perhaps one is torn off? Have fun with it.
The reason I suggest that is that the tools to do this work are expensive- really expensive. Guessing you might need new heads right away- you must an exact match doner drive- that will cost a premium. Likely you will transplant the heads- you will need a good tool- expect around 500 there. You will need a laminar flow bench or cleanroom- expect many thousands there on up so it doesn't get contaminated. The likelihood you will do it right the first time is very low- repeat cycle buying new heads. Maybe that wasn't your problem and you just needs to fix the drive itself's operating system- The tool of choice for that is about $12,000. I have not begun to list the tools these pros use! I am an amateur at this and mu hardware investment is over $9,000 and would not attempt any operation opening the drive. Its not discouragement- its just improbable to have any success. Do enjoy exploring it instead!

[Eleg]

Answering against better judgement, but I already got my toes wet into this discussion...
When people on this forum discourage anyone from tinkering with their hard drives, it is usually to protect a DIY-er from making permanent damage to his/her important data.

@int0x13:
The purposes of this forum have been discussed many times. No single correct answer exists. I don't know anything about your technical knowledge. But reading between the lines, the question and info provided, and choice of tool to check the hard drive, you are probably not in the data recovery business. This might be wrong, it is just the idea I get from your post.

How people perceive your DR knowledge will affect the answers you receive. Providing a short answer, or clue, to a knowledgeable person is much less work, compared to writing an essay to a less knowledgeable person. The latter implies detailing all the buts and ifs.

Your patient hard drive does not contain important data, so what you are asking for is essentially free education. This is fine, this is after all a web forum. But you can't demand answers. If people respond, then fine. If they don't, that is also fine. A recognized DR technician did spend time responding to your post. Based on your attitude, I will be surprised to see further helpful posts.

[int0x13]

It has severe media issues and/or physical problems.

Not realistically repairable.

Bin it

Eleg, you call this an answer? I have already explained what i think about this kind of answer. Its worst than, no answer at all, because it is disinformation. What about explaining which logical path has led to this conclusion would be valuable answer, but not this, sorry.

[Dmitri]

There are some persons i've seen on this forum that really want to share knowledge like fzabkar and Spildit

You have chosen people you'd like to work with. Send the drive to one of them and that's all.

[int0x13]

There are some persons i've seen on this forum that really want to share knowledge like fzabkar and Spildit

You have chosen people you'd like to work with. Send the drive to one of them and that's all.

Ohhh, you're upset Dmitri?

[int0x13]

I did some victoria scandisk, and the SMART result after the scandisk:

Attachments

[HaQue]

Correct me if I am wrong, but didn't you try a 7200.11 BSY or 0 LBA bug fix on a 7200.12?

May be a much better usage of time to dedicate the hours spent on mucking about with this drive you supposedly don't care about actually reading what all these commands do, and what effect it has on the drive. I hazard to think that the 2 people you mention would be grateful that the hours THEY spent writing all the information for people like you was actually READ.

Sometimes "bin the drive" is the best advice. Yes you may learn something in the process, but how long will it be until the stuff you learn can be put in context. do you anticipate many more drives with the exact same problem as this one for some reason?

on a side note, MANY interesting Docs and folders can be found with the Google search term: "F3 T>m0,2,2,,,,,22"

[int0x13]

Correct me if I am wrong, but didn't you try a 7200.11 BSY or 0 LBA bug fix on a 7200.12?

May be a much better usage of time to dedicate the hours spent on mucking about with this drive you supposedly don't care about actually reading what all these commands do, and what effect it has on the drive. I hazard to think that the 2 people you mention would be grateful that the hours THEY spent writing all the information for people like you was actually READ.

Sometimes "bin the drive" is the best advice. Yes you may learn something in the process, but how long will it be until the stuff you learn can be put in context. do you anticipate many more drives with the exact same problem as this one for some reason?

on a side note, MANY interesting Docs and folders can be found with the Google search term: "F3 T>m0,2,2,,,,,22"

Hello HaQue, well it's a long story but yes, during the process i did the very common mistake to try that command to regen translator which is

Code:

m0,2,2,,,,,22

When you're searching for this problem here on hddguru i found that:
http://forum.hddguru.com/viewtopic.php?t=18907&f=1&start=20#p143165
As i had the same model but just different firmware (mine is CC44) i thought i would try it. So yes, i felt into the 7200.12 well known trap like many others like here Spildit:
http://forum.hddguru.com/viewtopic.php?f=1&t=27290
But at the start of the story the HDD could not be accessed, and i had just this:

Code:

Rst 0x20M
(P) SATA Reset
PASS
RW: Error processing Performance Parameter File: 203C PASS
No Phy: Staggered spin bypass


So i just tried this:

Code:

F3 T>m0,2,2,,,,,22
Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 16, Max Certify Rewrite Retries = 14E8

User Partition Format   5% complete, Zone 00, Pass 00, LBA 00009A64, ErrCode 00000080, Elapsed Time 0 mins 30 secs   
Init SMART Fail
LED:000000CC FAddr:0024EE5D
LED:000000CC FAddr:0024EE5D
LED:000000CC FAddr:0024EE5D


And after reading tons and tons about that i've understood that there is a "trap" into 7200.12 with those NRG-LIST sector that make the regen translator command a disaster. So the right command to regen translator to take into account those NRG-List is this one:

Code:

m0,6,3,,,,,22

And to answer you HaQue, yes i've read a lot of background about that, but a little too late. What do you think? That i didnt spend hundreds of hours searching all over the web? Then you're wrong. And i dont anticipate to have others 7200.12 HDD to play with, i just do that to learn more about seagate firmware, and HDDs generally.
I attach the initial terminal troubleshoot when i received the drive.

Regards,

Attachments

notes.txt

(65.34 KiB) Downloaded 1207 times

[int0x13]

I dont know which command led me to this result, now i have this when i connect the HDD with sata data cable:

Code:

Jumping to Power On Reset▒
Rst 0x20M
(P) SATA Reset
PASS
RW: Error processing Performance Parameter File: 203C
(P) SATA Reset
PASS
RW: Error processing Performance Parameter File: 203C
Send Status: COMRESET seen
ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5

ABORT!
SenseCode = 03310000
ReadyStatusFlags = 0002A1A5


Also i have no more SMART table access, i can detect the drive into Victoria, but now it gives me this:

Do you have any idea wich CULPIT command did this?

Attachments

[warnerr]

No I don't know. Damage is increasing exponentially. Perhaps time to open it up and clean platters with CRC spray.

[int0x13]

No I don't know. Damage is increasing exponentially. Perhaps time to open it up and clean platters with CRC spray.

Yes, but i did mistaked with terminal commands. But no problem because i dont care about this drive, it's just a playground for 7200.12 type for me.
I wonder if there is a copy of the most important module into the F3 arch? So i can just restore them to go back to initial point?
warnerr, you said you have invested 9000$ in a DR lab, just curious what did you buy for this money?

[warnerr]

Only the most basic items. Started with Media Tools Professional, then bought Atola Insight. Several docking bays, a portable cpu and a very powerful workstation. Many misc software R-tools, CnW, BadCopy pro, Isobuster, Jpeg recovery4,Paragon hard disk manager, Zero Assumption recovery, Ufs Explorer,DMDE... and a bunch more are a few of the licenses I have that come to mind. I do not open drives- if a recovery is not within this scope of equipment I send it out to the pros on this forum.

[HaQue]

-Performing commands you don't know is one mistake.
-Not Documenting each step so you actually know which changed your drive is another.
-Spending hundreds of hours reading all over the web, while obviously exaggerated, is another. Reading is one part, experience is key.
-reading tons and tons about this trap is overkill. Almost every tutorial on the 7200.11 fixes start with "Do Not try this on a 7200.12", yet you still did it.

-Wanting to "fix" a drive no one in their right mind would ever use for data is another.

-not listening to Pro's is another.

If I drain the oil out of my car and run the engine until the con rods smash out the engine block, I can flatten the battery trying to start it. So I ask a Pro and he says my engine is dead. get a new one. Do I say, no, I bought new battery and now the engine turns over so it must be nearly fixed?

just because you hammered commands into the drive, and now terminal says something different does not mean you have got it on the way to being "fixed".

What criteria are you using to decide the Pro's don't know what they are talking about?

I would be interested to know what, specifically, you have actually learnt so far. Aside from don't apply 7200.11 fixes to 7200.12 of course.

Anyway what evs

[thatdellguy]

DATA IS NOT IMPORTANT, JUST WANT TO FIX IT, I DONT CARE AT ALL ABOUT THE DATA.

The hddguru forum gets a lot of posts like this to make it look like the data is not needed when it actually is. Posters are more relaxed about answering posts where data recovery is not in question. I have to ask myself what is purpose of your post. You obviously have a drive that is failing and have zero knowledge on how to fix it. Are you expecting to become an expert overnight? Maybe? Why are you running random terminal commands on the drive? Who knows why... It just doesn't add up and I truly believe this is misinformation. Nobody in their right mind would spend almost an entire month fixing a broken drive to reuse it. Send it to a professional or buy a new drive.