Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

Hi,

Normally when you hit any key you cannot see anything on the screen Pls try to press Ctrl + Z keys than you have to see F3 T>

0

Share this post


Link to post
Share on other sites

thanks, but even with Ctrl+Z, nothing appears on the screen... this is my problem.

0

Share this post


Link to post
Share on other sites

Hi,

Means problem is on the cable. You can buy CA-42 this is the cheap one. And easy to use I have also professional recover kit on my hand most of all I'm using it

0

Share this post


Link to post
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?

0

Share this post


Link to post
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

0

Share this post


Link to post
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...

I have the exact same problem! I'm wondering if the HDD itself is busted as I'm seeing some strange voltage readings on the three hdd pins (gnd, rx, and tx), but given my current lack of understanding I'm not confident enough to say what I'm seeing is unexpected. Have you had any luck?

0

Share this post


Link to post
Share on other sites

Alright I'm obviously a noob at this. Turns out I had confused the purpose of the pins... and was trying to use the two furthest from the SATA connector as RX and TX.

*face palm*

But at least now I see data from the hdd, and the code confirms i have the BSY issue.

0

Share this post


Link to post
Share on other sites
My question is basically that I am not sure which error I have.

It seems to me like you answered yourself to your question :):

The BIOS indicated that the drive was present but was ZERO megabytes in size.
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.

jaclaz

0

Share this post


Link to post
Share on other sites

To jaclaz,

It looks like you are right; it turned out to be an LBA 0 error and a bunch of bad cables. The 1.5 TB drive is back to its old self, ready to crash another day.

0

Share this post


Link to post
Share on other sites
To jaclaz,

It looks like you are right; it turned out to be an LBA 0 error and a bunch of bad cables. The 1.5 TB drive is back to its old self, ready to crash another day.

Glad to hear that there is another happy bunny in the basket :):

http://www.msfn.org/board/cant-access-repa...27-page-10.html

The problem is that the sky may fall on our head tomorrow....

abraracourcix.gif

http://www.asterix-international.de/asterix/characters.shtml

Abraracourcix, called Vitalstatistix in the English books, the chief of the tribe. Majestic, brave and hot-tempered the old warrior is respected by his men and feared by his enemies. Abraracourcix himself has only one fear; he is afraid the sky may fall on his head tomorrow. But as he always says, 'Tomorrow never comes.'

;)

jaclaz

0

Share this post


Link to post
Share on other sites

Hi All,

I was able to successfully recover my 500GB seagate HDD. Gradius, your tutorial is very nice. Thanks for all for their valuble suggestions.

During my recovery, i faced the following issue.

F3 T>/2

F3 2> Z

Spin Down Complete

Elapsed Time 0.154 msecs

(Paper card Removed)

F3 2> U

(Drive begins to emit a quiet Buzzing noise every 1.5 seconds. Seven Minutes later..)

Error 1009 DETSEC 00006008

Spin Error

Elapsed Time 7 mins 27 secs

R/W Status 2 R/W Error 84150180

I then with HDD power ON, tightened all the screws on the PCB. In my case, the issue was with the PCB and HDD contacts. SO i set all the screws and tightened the screws. Then i issued the command 'U' and got the spin complete message. And then i followed the remaining steps to get the HDD recovered. And then updated the firmware.

Salute to the msfn gurus :thumbup

Salute to Gradius :thumbup

Thanks

guru

0

Share this post


Link to post
Share on other sites

Hi, i recovered my hd from BSY error.

My hd is Barracuda 7200.11 500 GB ST3500820AS with firmware SD81.

First didn't work breaking the contact of the motor with the peapar, then i tried with the peapar on heads contact and didn't work also.

So i tried breaking both the contant and it worked.

So now i should upgrade the firmware to SD1A version but i'm scared, if something goes wrong??

Even if it goes well, it's that sure i will not have some issue in the future (example read and write speed limited performance)??

So now i ask you, there is a way to backup my original SD81 firmware?

So in case i may restore it again!!

Edited by michael chiklis
0

Share this post


Link to post
Share on other sites

Hi

Mabye this is a stupid question. :wacko:

Do I have to cover both conatct? The one in the right lower side with the screw in it and the one that looks like it would go to the spindle motor? Or only one of them? If only one, which one? I can connect to the PCB via terminal. But I get errors. If I cover only the one with the screw hole in it it get errors, CC or CE, cant remember at the moment.

Thanks alot

0

Share this post


Link to post
Share on other sites

By the way, could someone post the photos from Jan 20 2009, 04:45 PM, I cannot see them.

0

Share this post


Link to post
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.