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

[Andy_C_28]

Hi all,

I have an issue with the above drive. It was working fine as a date repository, used externally via a caddy. Then one day it just wouldn't work. It spins up fine but is not seen by the computer at all, not even in the BIOS. I have tried a couple of software tools but nothing will see it. I have tried another interface card from a 320AS and it can then be seen by Device Manager but not Disk Management so I am unable to retreive any data from it. It is very important that I get the data off of it. 

Do you think that getting an interface card for that exact model drive would help or is there something fundamentally wrong with it??

Any help will be much appreciated.

[canadian1969]

By interface card are you referring to the drives PCB? (printed circuit board).

I would simply try the drive outside of it's caddy,  as a regular internal SATA drive, if you have done this already (your post doesn't really say you have) then replacing the PCB may be an option, but I have NEVER replaced a PCB from a drive model other than the exact same model. I dont see how that could ever work otherwise, but maybe there are ways with proper tools, like sending it to Seagates data recovery labs. Problem then is finding a proper replacement PCB. Also, check the board for obvious defects, if it looks okay then it may be a blown IC or capacitor or something, in which case a PCB swap might work long enough for you to get the data off.

One note,  with more modern drives you often cannot swap PCB's becasue they contain flash memory that has drive specific calibration data, I'm not sure about this drive, Hopefully a Seagate tech will reply on this matter.

[fzabkar]

Your model may be showing symptoms of the 7200.11 BSY bug. The following firmware update was meant to address this problem.

Firmware Update for ST3500320AS, ST3500620AS, ST3500820AS, ST3640330AS, ST3640530AS, ST3750330AS, ST3750630AS, ST31000340AS [207951]:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951

AFAIK Seagate offers free data recovery for qualifying drives. What is your firmware version?

Alternatively the following URLs describe a simple DIY fix.

Seagate 7200.11 BSY bug and 0 LBA fix:
http://sites.google.com/site/seagatefix/
http://www.msfn.org/board/index.php?showtopic=128807
http://www.overclock.net/hard-drives-storage/457286-seagate-bricked-firmware-drive-fix-pics.html
http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/SOLUTION-FOR-7200-11-SERIES-MAXTOR-SEA...

BTW, I believe that the reason that you were able to get further with the replacement PCB is because it has different "adaptive" information. Therefore the drive would have been unable to locate and read the buggy code in the hidden System Area of the drive.

I suspect that you may get a response in BIOS if you detach the PCB from the drive and connect it to your SATA port on its own. If so, then this will tend to support the idea that the PCB is OK.

[Andy_C_28]

Thank-you very much for your advice guys.

Sorry, yes the drive is already out of it's caddy and I have been trying it plugged directly into the motherboard. The PCB (what I was calling the interface card as it is the board with the SATA connections on it!) that I tried as a donor was off of another 500GB Seagate drive, the only difference was that my faulty drive was a ST3500820AS and the donor was a ST3500320AS. Thought it was worth a try seeing as I had it to hand!

Thanks for the links to the step-by-step instructions on how to fix it. I have seen that Nokia cable used in a few discussions so I'm thinking that might be my best option! I will give it a go and post back on here if it was successful.

Many thanks again for taking the time to help me....much appreciated.

Andy

[Andy_C_28]

Hi guys,

I hope you can help me. I have followed the unbricking instructions step by step. All good until I get to the following step:

F3 1>N1

When I initiate this process I get the following error:

Unable to load Diag Overlay

I tried it a few times but always got the same error.

Can anyone shed any light on the above error?

Any help is appreciated.

Cheers

Andy

[Cantbecanit]

Only one thing I can think of is when you put the blanking card under the board place it where the central spindle goes underneath rather than at the side where most of the guides say to do it.

[Andy_C_28]

I will give it a go...thanks!

At the point where I initiate the N1 command I'd already taken the card out though...that's what the instructions I had told me to do...is this not right?

The card I have used completely covers the connector...is this not right??

[Cantbecanit]

Here's how I did it

http://forums.seagate.com/t5/Barracuda-XT-Barracuda-Barracuda/SOLUTION-FOR-7200-11-SERIES-MAXTOR-SEA...

You should have a read here as well

http://www.mapleleafmountain.com/seagatebrick.html

Also if you are using HT try Putty instead, and don't worry about the cable vs the TL board method, as long as you get connection through either you can fix it.

Think I have the answer, while you are commanding the blanking card should be in, you remove it after doing the 1st set of commands and then tighten the screws back up carefully, I just slackend the screws and enough to get the card under by the central spindle, *you are blanking off where the spindle moulding goes under the board*  make sure you know what you are fixing, there are two possibles, one is busy and the other is LBA0, I assume you are doing the busy fix.

[Andy_C_28]

Hi,

Thanks again for your latest response.

I have now sorted the problem and am able to get my data off!

I moved the cover paper to the spindle as you suggested, that also helped!  Not sure why some other instructions tell you to cover the other connector! Strange!

Anyway...thank-you again for all your help...it is very much appreciated  )

[Cantbecanit]

Good stuff Andy, now do the FW update on it and the drive will be 100% again, SD1a

@ Arti, this isn't for free advertising mate so I will be requesting your post to be removed, so if you wondered where it went, it went because it breaks the rules of the site, hope you understand.