Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[VeganFanatic]

if you have already tested it on several rigs, then get an RMA and send it back

[Yannick]

---

VeganFanatic wrote:

if you have already tested it on several rigs, then get an RMA and send it back

---

We (well at least I am) are trying to find a way to get the data of the bricked drives, so sending them in RMA is not really an option..
Like I said in one of my previous posts, there's a dude on the salvation data forum who has fixed these kind of hard drives with the 'firmware problem'. If he managed to do it, more people should have been able to fix their drive, right?

[VeganFanatic]

Recovery is going to be expensive

I am not well equipped to do that, search Google for providers

[Yannick]

I know... Why do you think I'm looking for a DIY fix? 

[freesty]

I'm looking for recovery, too.

[freesty]

I'm in contact with salvationdata forum support and will try to get access to seagate vip threads.

[Yannick]

This is what the post said. There's also an image that shows which pins you should short. Haven't tried it ouy yet because I didn't had the time...

HI EVERYBODY
I HAVE FIXED THIS 2TB LP SEAGATE DRIVE.YOU DONT NEED TO SCARED JUST FIND OUT THOSE TWO PINS TO SHORT.SHORT IT FOR A WHILE AND YOU WILL GET READY IN STATUS BAR.THAN JUST POWER DOWN AND POWER ON YOU WILL GET YOUR DRIVE BACK .I AM STILL USING THIS DRIVE.DONT WORRY WHEN YOU HEARD SOME TYPICAL SOUND WHEN YOU SHORTING THESE PINS.ITS A PART OF THIS PROCESS.
KIND ATTN:PLS REFER THIS PIC GIVEN BELOW IF YOU HAVE SAME DIAG ERROR AS PEOPLE SHOWN HERE IN TERMINAL LOG.
THE PEOPLE WHO HAS NEW HARD DRIVE AND FIRST TIME PROBLEM OF NOT DETECTING BY BIOS OR BUSY IN TERMINAL OR DOING NO TERMINAL JOB SHOULD FOLLOW ONLY OLDER 7200.11 SYSTEM.PLACE ONE VISITING CARD JUST UNDER CONNECTION OF HEAD CONNECTOR WHICH CONNECTED TO PCB AND THAN GO TO TERMINAL /2
F32>Z
spin down
NOW REMOVE THE VISITING CARD AND TIGHT THE SCREWS THAN,
F32>U
SPIN UP
CTRL+Z
F3T>i4,1,22
clear g-list
F3T>/1
F31>N1
smart cleared
just power down 
power on
you can see your hdd is back with all data

DONT GIVE m0,2,2,,,,,22 m,6,2,,,,,22 OR ANY SAME
ALL THE TERMINAL LOG AS YOU CAN SEE REGARDING "No HOST FIS-ReadyStatusFlags 0002A1E1" THIS IN THIS POST ARE VICTIM OF THIS M-FORMAT COMMAND AS PER MY KNOWLEDGE EVEN I HAVE MADE SAME MISTAKE.


HERE I HAVE ATTACHED ANOTHER JPG WITH CIRCLE ON POINT TO BE SHORTED ALL THE BEST. I HAVE WRITTEN WHAT I HAVE DONE.AND I GET SUCCESS EVEN JUST BEFORE THIS POST I HAVE APPLIED ON ANOTHER SAME DRIVE.SIMPTOMS HDD BECOMES INITIALIZED NO NOISE SMOOTH SPINING AND LOG FILE YOU ALL HAVE.THE PROBLEM START WITH YOU PEOPLE APPILED V4 V1 ANm format you will get this errror.So all the best to all and enjoy and share your success with others .

[Agent24]

That is very interesting...

If his fix works, does this mean that this is in fact a firmware issue, even though Seagate say it's not?

Not sure if the previous firmware fix cleared the g-list as this one appears to. Could this point to some kind of hardware issue causing it?

I wonder if the drives are "safe" to use even after this fix?

[cwong2910]

1 year since i first posted the problem and have been using the RMA-ed HDD.

I upgraded the firmware to CC32 once i took possession of the ST2000DL003 HDD.

Has been working fine for this one year (touch wood). 

Oh and i have since bought 2 more WDD Green Drives and 1x Buffalo since then.

All working fine and i will switch all my remaining Seagate drives to WDD once they hit 3 years.

[VeganFanatic]

ST2000DL003 is on my server where it hosts computer chess files. The load on the disk keeps it very busy.

I got my disk 2 days before the floods.

Hoperfully it stands up until prices fall back to sensible.