Jump to content

The Solution for Seagate 7200.11 HDDs


Recommended Posts

Hello I have Barracuda ST3500320AS drive. IT is connected like secondary drive and have problem with drive then it goes offline in windows and all partitions is lost and I must create partitions again. I have updated my drive firmware to SD1A but this problem don't disappear. So it is the drive problem ( 0 LBA and BSY errors ) or the motherboard SATA drivers ?

Link to comment
Share on other sites


The adapter gives output when im doing the loopback test(YAY) But nothing when connected to the drive. Im sure im settin up the hyperterminal right. And i have read maple leaf mountain twice. Im not sure what you mean by grounding as my setup has the black power wire connected to the powersupply and the red to the red on the power supply as well so pardon my stupidity if theres something else i must do?

Sometimes GROUNDING is required, but usually the problem is in "garbled characters", not "NO response"

Look at this photo:

05.jpg

and read here:

http://www.msfn.org/board/solution-seagate...-page-1661.html

BUT you are using this board:

http://www.sparkfun.com/commerce/product_i...products_id=449

Try reading attentively this part of the description:

Shifter SMD is powered from the target application and can run at any voltage! That's right - power the board at 5V and the unit will convert RS232 to 5V TTL. Power the board at 2.8V and the Shifter board will convert RS232 to 2.8V CMOS TTL.

Chack against this:

http://www.msfn.org/board/solution-seagate...-page-2023.html

and a few posts later.

Now, you may want to try powering it with 3 V, i.e. it is very possible that you are sending "ununderstandable signals through the line", compare with this:

http://www.interfacebus.com/voltage_threshold.html

jaclaz

Link to comment
Share on other sites

Please help.

The situation is:

I have used a serial ttl adaptor which works ok for the 38400 speed (verified by running the loopback test).

I am using a separate PSU than that of the PC running the HyperTerminal software.

I have grounded the separate PSU and the PC PSU together.

I have connected the GND pin to the separate PSU molex connector (black wire).

I have connected the TX/RX cables in the right order (I have aslo tried the reverse).

The ttl adaptor has two LED indicators labeled TX and RX (TX:Green RX:Red).

When I run the Loopback test the HyperTerminal software identified the baud rate and correctly displayed it on its window (38400 8-N-1) and both LEDS were blinking on every keystroke and were not lit when nothing was pressed on the keyboard.

When i connected the ttl adaptor to the HDD both LEDS were lit constantly (not blinking) and there was no output on the HyperTerminal screen (regardless of pressing any key or not) nor was the baud rate identified.

When i reversed the TX/RX cables the only difference was that the RX LED (Red) was constatly lit and the TX LED was not lit at all (Green).

The HDD is able to spin if only the SATA power cable is connected and this must indicate that the disk and the pcb are still alive.

Finally I have tried isolating the spin motor connector as well as the data connectors (not at the same time of course).

Guys please help...

Link to comment
Share on other sites

Hi all,.

Big thanks to all those who've worked out how to unbrick these hdd's, got two 1Tb units here to get running,....

After following the instructions on how to hook up a max323 ttl adaptor, and finally getting HyperTerminal to co-operate, I thought I'd look at what error code the drives report, and got a different number to those I've read so far.

Before I go and reset the hdd's, does anyone know of a list of all the LED Addr: error codes and what they refer too?

PiDicus.

Link to comment
Share on other sites

I successfully resuscitated my Seagate drive today, and wanted to heap thanks on all the people that have taken the time to create guides etc. I also want to outline my situation and hiccups encountered, in the hope they help someone else.

Drive: ST31000340AS Barracuda 7200.11 SATA 1TB.

Thanks to Cantbecanit at the Seagate forums:

http://forums.seagate.com/stx/board/messag...ding&page=1

He led me to this thread and told me about the Nokia cable option (which made it a lot less daunting for me). Importantly he exlained that the cable must be plug and play recognised when plugged in. In the end my local phone shop sold me his own cable that he used for unlocking, as it was P&P compatible and worked as Cantbecanit described.

I ended up getting a DKU-5, which worked for me fine as an alternative to the CA-42.

It took me ages to find USB-UART drivers for the cable to work, but I found drivers here:

http://members.driverguide.com/driver/deta...driverid=647160

Then in the cableitself I only had three wires, and this guide explained my yellow, red and blue wires:

http://www.nslu2-linux.org/wiki/HowTo/AddASerialPort

I then followed the guide at the beginning of this thread, alone with this guide:

http://sites.google.com/site/seagatefix/

(even though that's not about my BSY problem, I referenced it sometimes)

Along with the reassurance of this YouTube video and the card trick to make things way easier:

http://www.youtube.com/watch?v=29FztWJVxbM

Finally, the cable worked but disaster struck, and I got this error as I tried to spin up the drive:

Error 1009 DETSEC 00006008

Spin Error

Elapsed Time 25.907 secs

R/W Status 2 R/W Error 84150180

I thought I was doomed, but thankfully found mymate's post where he said he isolated the motor contacts instead of the head contacts, as per this guide:

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

And that was the trick! I had to do the motor contacts.

So now all is working, and I've updated the firmware.

Again a HUGE thank you to everyone. At times like this I really appreciate the internet and everyone's effort!

Link to comment
Share on other sites

Hallo i unbricked mine too: ST3500320AS with SD15.

Thanks to all of you.

I found the best manual on:

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

The most importand thing is to power off the drive before the final command (m0,2,2,,,,,22). I was missing that on:

http://www.overclock.net/hard-drives-stora...e-fix-pics.html

between step 12 and step 13.

regards mad68

Link to comment
Share on other sites

situation remains the same. any idea? anyone who can assist? do not know what else to try... pls pls pls

Please help.

The situation is:

I have used a serial ttl adaptor which works ok for the 38400 speed (verified by running the loopback test).

I am using a separate PSU than that of the PC running the HyperTerminal software.

I have grounded the separate PSU and the PC PSU together.

I have connected the GND pin to the separate PSU molex connector (black wire).

I have connected the TX/RX cables in the right order (I have aslo tried the reverse).

The ttl adaptor has two LED indicators labeled TX and RX (TX:Green RX:Red).

When I run the Loopback test the HyperTerminal software identified the baud rate and correctly displayed it on its window (38400 8-N-1) and both LEDS were blinking on every keystroke and were not lit when nothing was pressed on the keyboard.

When i connected the ttl adaptor to the HDD both LEDS were lit constantly (not blinking) and there was no output on the HyperTerminal screen (regardless of pressing any key or not) nor was the baud rate identified.

When i reversed the TX/RX cables the only difference was that the RX LED (Red) was constatly lit and the TX LED was not lit at all (Green).

The HDD is able to spin if only the SATA power cable is connected and this must indicate that the disk and the pcb are still alive.

Finally I have tried isolating the spin motor connector as well as the data connectors (not at the same time of course).

Guys please help...

Link to comment
Share on other sites

I am late to this forum but familiar with the problem of the Seagate bricked drives. I have a 1.5 TB primary drive and also have 2nd drive for Vista and a 3rd drive for Xp. I would like to apologize for a simplistic question, but I have been unable to find the answer in the last 111 pages.

The drive functioned for 6 months, booted daily under Win7 RC, and one day would not boot. It hung at the post and would only proceed to the BIOS if the F1 key was depressed. The BIOS indicated that the drive was present but was ZERO megabytes in size. I can boot from the other disks, and the affected drive cannot be read by any other computer. Pressing F1 does not allow booting from the primary disk.

I have been wrestling for three weeks with the CA-42 data cable issue for reprogramming the PCB. After trying SIX different cables I finally found one that communicates with the PCB. (It's amazing how many different and unmarked CA-42 cables there are.)

My question is basically that I am not sure which error I have. It seems likely it is one of the two previously cited: 0 LBA or the BSY problem. I read the posts by Gradius2 where he states:

There are two common errors on Seagate 7200.11 HDDs (caused by bugs on firmware):

- 0 LBA error: it happens when your BIOS can recognize your HDD at POST moment, but as an 0MB drive.

- BSY error: it happens when your HDD enter on a halt state, or BuSY state. In this condition, your HDD will not be recognized by BIOS at POST moment.

I'm not sure if the drive is not booting because it is not recognized as having more than ZERO megabytes or is it not proceeding because it is in a perpetual BSY state. The fixes are different, and I do not want to screw things up now.

Is there any post in this thread that can clarify my problem?

Link to comment
Share on other sites

Hi jroymd

Most of the times a virus will cause such problem. And sometimes partition table corrupt. You can solve boot problem with fdisk /mbr command but you have to recreate partition for reach your folders and files.

You can search on internet there is a cd image called "PE recovery tools" . This is a CD and you're booting your system with that CD, it's containing many disk/data recovery tools and diagnose tools as well.

Meanwhile you can try to use "DI Partition Recovery" tool for check your HDD

Good Luck

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...