Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

I'm no expert by any means, but I have read in many places that it is best to start over from step 1 and try it all again since you said your pc crashed during the process. It is fortunate that it didn't happen while one of the procedures were running but in an intermediate step.

start over and see how it goes.

0

Share this post


Link to post
Share on other sites
The Solution for Seagate 7200.11 HDDs (final and revised version):

* Spanish Version here / Versión en Español aquí.

* Italian Version here / Versione Italiana qui.

Attention: This guide might not be to everyone. Is not hard to KILL your HD if you don't follow the instructions with extreme caution. I'm NOT responsible for any damage or data loss it can happen (so far no one lost anything, but accidents can occur).

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.

Seagate's explanation:

Description

An issue exists that may cause some Seagate hard drives to become inoperable immediately after a power-on operation. Once this condition has occurred, the drive cannot be restored to normal operation without intervention from Seagate. Data on the drive will be unaffected and can be accessed once normal drive operation has been restored. This is caused by a firmware issue coupled with a specific manufacturing test process.

Root Cause

This condition was introduced by a firmware issue that sets the drive event log to an invalid location causing the drive to become inaccessible.

The firmware issue is that the end boundary of the event log circular buffer (320) was set incorrectly. During Event Log initialization, the boundary condition that defines the end of the Event Log is off by one. During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing, firmware will increment the Event Log pointer past the end of the event log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further update s to the counter become impossible and the condition will remain through subsequent power cycles. The problem only arises if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, there is no path to resolve/recover existing failed drives without Seagate technical intervention. For a drive to be susceptible to this issue, it must have both the firmware that contains the issue and have been tested through the specific manufacturing process.

Corrective Action

Seagate has implemented a containment action to ensure that all manufacturing test processes write the same "benign" fill pattern. This change is a permanent part of the test process. All drives with a date of manufacture January 12, 2009 and later are not affected by this issue as they have been through the corrected test process.

Recommendation

Seagate strongly recommends customers proactively update all affected drives to the latest firmware. If you have experienced a problem, or have an affected drive exhibiting this behavior, please contact your appropriate Seagate representative. If you are unable to access your data due to this issue, Seagate will provide free data recovery services. Seagate will work with you to expedite a remedy to minimize any disruption to you or your business.

You'll need:

- 1 (one) adapter ($4)

http://alldav.com/index.php?main_page=prod...;products_id=11

I used this adapter ($13.95, yep expensive):

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

- 1 (one) RS232 cable ($3.78):

http://www.cispc.com/ssproduct.asp?pf_id=10480908

or (buy a RS232 to TTL adapter, or FT232BM/BL, not need both!)

- 1 (one) FT232BM/BL adapter (check below) and USB cable ($12.47):

http://shop.ebay.com/?_from=R40&_trksi...-All-Categories

Any other similar adapter will works fine, just need to be +3.3V DC (+5V will works too, but I recommend 3.0~3.3V). Is possible to find USB to TTL adapters too, they do USB to RS232 internally and then it converts to TTL. For example, some users used a cellular data cable for PC (lots them do RS232 to TTL).

- 1 (one) USB cable ($3.99):

http://www.optimization-world.com/details/prodid/320.html

- 1 (one) kit of Ten 5" Jumpers and 20 Headers ($5):

http://www.hobbyengineering.com/H2362.html

- 1 (one) mini Torx 6 screw driver ($3.29):

https://www.acehardwareoutlet.com/(jv21u13p...spx?SKU=2167237

- Soldering stuff (optional). Use 60W max.

You can buy a complete kit for $7.99 here:

http://www.radioshack.com/product/index.js...rodsInSession=1

The rest:

- 1 (one) computer with Terminal software (like HyperTerminal or similar) and a RS232 or USB port.

- A fixed firmware from Seagate here (Released in 22/01/2009 and 24/01/2009 for all affected drives).

- A little bit of patience and practice. :whistle:

TX and RX connections from a SATA Seagate 3.5":

connector.jpg

Photo with the real drive:

05.jpg

Connect TX and RX ports with RS232 to TLL adapter, you'll need something like jumpers in order to do that, or soldering directly to the PCB board. Connect GND and +5V to PC power supply, or similar. Keep in mind those are direct from Seagate sides, so you'll need to connect in this way:

- From PC (TX) to >>> RX (on Seagate)

- From PC (RX) to >>> TX (on Seagate)

You can use RED wire (+5V) from PC power supply. Blacks are GNDs (yellow is +12V so don't use it).

If you don't want to mess with power supply, just use a CR2032 (3V) battery:

https://www.isaleproducts.com/p-7709-3v-lit...ll-battery.aspx

An idea of whole setup (I used an USB to RS232 too):

fix04.jpg

Run HyperTerminal (or your favourite terminal software).

Configure the RS232 port to: 38400 8 N 1 (like this one):

01.jpg

02.jpg

04.jpg

post-225812-1240681002.jpg

Fixing 0 LBA error:

Note: All commands are case sensitive !

To correct 0 LBA error, you'll need to do a quick format in order to regenerate the partition, just with m0,2,2 and the rest can be left blank by putting only commas or filling out with zeros. At the end you need to use a "ValidKey" code, or 22.

Attention: The commands must be used 100% equal as showed here, wrong cmds could lead to data loss or HD loss! Double or triple check the cmd before to press enter!

So we'll have to enter:

F3 T>m0,2,2,0,0,0,0,22 (enter)

For reference: F3 T>m does:

Level T 'm': Rev 0001.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertif

yTrkRewrites],[ValidKey]

Now wait 15~30 seconds until something like this appears (it will vary a bit):

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 00, Max Certify Rewrite Retries = 0000

User Partition Format 5% complete, Zone 00, Pass 00, LBA 00008DED, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

ONLY after the message like above you can turn off everything.

Fixing BSY or CC errors aka BUSY (I recommend some practice before trying this):

Note: All commands are case sensitive !

First, make sure you have your hard drive accessible; on a table with open access to the drive is best.

Second, you need to remove the PCB (Printed Circuit Board) from HDA case using a Mini Torx 6 screw driver.

Third, connect RX & TX cables from your RS-232 adapter, verify that all is correct, and then connect the power supply to Hard drive circuit board.

Explanation: The problem with the drive is that the drive is stuck/halt in a BUSY state. This basically locks up the SATA port, causing the BIOS problem (cannot detect the drive at POST). In the terminal, you will see this sort of error (LED: 000000CC FAddr: 0024A051). Once you see this in the terminal, the terminal session to the drive is completely blocked and will not accept any more commands. In order to circumvent this, we'll need to disconnect the PCB (circuit board) from the hard drive case so that the LED: 000000CC FAddr: 0024A051 command cannot be sent from the firmware of the terminal session.

After you have connected the power to the circuit board, press CTRL+Z in your HyperTerminal session. You should now see a prompt like this:

F3 T>

If you do not see this prompt, check your RS-232 connections to the drive. (you may have the TX and RX flipped).

Now we'll need to access the Level 2, type:

F3 T>/2 (enter)

F3 2>

And type (to spind down the motor):

F3 2>Z (enter)

Spin Down Complete
Elapsed Time 0.147 msecs (the time will vary here)
F3 2>

Now the tricky part. Pratice a lot without any power before even trying this. You need to make sure that the screws don't touch the PCB board where they aren't suppose to or you will fry your PCB board. If you have been practicing and the power is not connected, start at STEP ONE.

With the POWER CONNECTED to the PCB board, as well as your TX/RX terminal wires, mount the board back on the HDA case. You must have the power connected when you do this.

Now type (to start the motor):

F3 2>U (enter)

You should get something like this:

Spin Up Complete

Elapsed Time 7.093 secs

F3 2>

Then go to Level 1 (by typing /1):

F3 2>/1 (enter)

Now lets do a S.M.A.R.T. erase (create S.M.A.R.T. sector):

F3 1>N1 (enter)

-------------------------------------------------------------------------------------

G-List step is optional:

Skip G-List step first, if after proceeding the whole BSY fix and the drive still remains under BSY error, then you'll need to repeat BSY process with G-List command below.

G-List Erase (Fix Defect List):

F3 1>/T (enter)

F3 T>i4,1,22 (enter)

For reference:

Level T 'i': Rev 0001.0000, Overlay, InitDefectList, i[DefectListSelect],[saveListOpt],[ValidKey]

-------------------------------------------------------------------------------------

Power OFF/ON the drive (very important!)

Wait 10 seconds and now Power ON your drive.

Press CTRL+Z on terminal and type:

Partition regeneration:

F3 T>m0,2,2,,,,,22 (enter)

For reference:

Level T 'm': Rev 0001.0000, Flash, FormatPartition, m[Partition],[FormatOpts],[DefectListOpts],[MaxWrRetryCnt],[MaxRdRetryCnt],[MaxEccTLevel],[MaxCertif

yTrkRewrites],[ValidKey]

You should get something like (in around 15~30 seconds):

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8

User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs

User Partition Format Successful - Elapsed Time 0 mins 05 secs

If you didn't get the msg above, then you skipped something important, and turning off your drive now will render an unreadable drive, so be careful.

ONLY after the message like above you can turn off everything.

A direct guide for BSY error (with photos):

http://www.msfn.org/board/index.php?showto...8807&st=100

Keep in mind I did my best to compile all this information and provide more and better details.

Gradius

Could this way to restore the data again arriving in the hdd?

Edited by kang roy
0

Share this post


Link to post
Share on other sites

Awesome work Gradius. I just fixed my drive following your instructions. Signed up to the forum to say cheers!!

0

Share this post


Link to post
Share on other sites

hi

my hyper terminal is not work

i press CTRL+Z

put is not show F3 T>

it is not work

please help me

0

Share this post


Link to post
Share on other sites
I'm no expert by any means, but I have read in many places that it is best to start over from step 1 and try it all again since you said your pc crashed during the process. It is fortunate that it didn't happen while one of the procedures were running but in an intermediate step.

start over and see how it goes.

Thanks anyway I still felt the hard disk and now works lighthouse lìaggiornamento firmware to see if everything ok

0

Share this post


Link to post
Share on other sites
Hi all, i'm new of this forums :)

I've read all this topic but i still have problem with my 7200.11 hd :(

The HD is in bsy mode.

I've tried with a RS232-TTL ADAPTER and TELNET (Putty or HyperTerminal) with no response.

The i used the paper method on motor contacts with the following results:

F3 T>

(i don't remember now cause i'm at work, but here i've removed the paper from motor contacts as the guide of gradius2 show)

F3 T>/2

F3 2>Z

Spin Down Complete

Elapsed Time 10.163 secs

* leaved paper from motor contacts and CTRL+z then *

F3 2>U

Spin Up Complete

Elapsed Time 21.017 secs

F3 2>/1

F3 1>N1

Unable to load Diag Overlay

F3 1>

The problem is the message "Unable to load Diag Overlay".

Any idea??

PS: Excuse me for bad english :(

up, anyone have ideas?

The method with CA-42 cable may resolve something?

0

Share this post


Link to post
Share on other sites
up, anyone have ideas?

Yes and No.

It should be possible to by-pass it:

http://hardmaster.info/eng/articles/09-04-2009.html

but it's well beyond the DIY level.

The method with CA-42 cable may resolve something?

Of course NOT, the CA-42 is (the good ones actually working) nothing different from a USB-to-TTL converter.

It is possible, though, that the contacts are not good:

http://forum.hddguru.com/1tb-seagate-hdd-d...d81-t12290.html

It can happen that the pins are forced a bit too much by the card, check previous pages there are a few reports about this issue.

Completely removing the PCB, thoroughly cleaning the contacts, check if any contact is twisted, etc., etc. may solve the problem, as well as re-tightening the screw nearest to the contacts once you remove the card.

jaclaz

0

Share this post


Link to post
Share on other sites
up, anyone have ideas?

Yes and No.

It should be possible to by-pass it:

http://hardmaster.info/eng/articles/09-04-2009.html

but it's well beyond the DIY level.

The method with CA-42 cable may resolve something?

Of course NOT, the CA-42 is (the good ones actually working) nothing different from a USB-to-TTL converter.

It is possible, though, that the contacts are not good:

http://forum.hddguru.com/1tb-seagate-hdd-d...d81-t12290.html

It can happen that the pins are forced a bit too much by the card, check previous pages there are a few reports about this issue.

Completely removing the PCB, thoroughly cleaning the contacts, check if any contact is twisted, etc., etc. may solve the problem, as well as re-tightening the screw nearest to the contacts once you remove the card.

jaclaz

ok, thanks jaclaz!

This evening when i return from work i try to remove PCB and i hope that work then..

i've also checked the previous page but i didn't found nothing similar to my problem :( i''ll probably look bad :(

i hope isn't a mechanical problem :(:(:(

0

Share this post


Link to post
Share on other sites
ok, thanks jaclaz!

This evening when i return from work i try to remove PCB and i hope that work then..

i've also checked the previous page but i didn't found nothing similar to my problem :( i''ll probably look bad :(

There are, at the moment of this writing 121 pages in this thread, it is not at all easy to find the "good" info distinguishing it from requests of help and unuseful info.

Here two examples:

http://www.msfn.org/board/index.php?showto...807&st=2152

http://www.msfn.org/board/index.php?showto...807&st=2100

Basically a common error people tend to do is putting a very thick "insulator" AND NOT loosen enough the screws around it.

This can slightly bend either the contact or the PCB, and you need to re-tighten the screws very hard to have contact, or check the contacts/PCD and/or leave them un-screwed long enough for the bent things to recover their original state.

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites
hi

my hyper terminal is not work

i press CTRL+Z

put is not show F3 T>

it is not work

please help me

What type of connection are you using? RS232 to TTL or the CA-42 USB cable? Either way, you need to connect the RX and TX wires together to see if hyperterminal comes up. then you connect it to the HDD. If it still does not work, switch the RX and TX wires.

0

Share this post


Link to post
Share on other sites

Hi all.

Well it's been a few weeks since I fixed my Seagate SATA 500GB with SD15 Firmware as it had the BSY state error, I had fixed it and recovered all my data back and now I can't believe it has done it again, well done Seagate you stupid pricks. Turned on my PC today and just like the 1st time, it doesn't detect my hard drive in BIOS. After I fixed it the first time, I didn't update the Firmware but I did back up my data so lucky for that.

So to everyone with these errors, just a reminder, it can happen again just like it did to me, so after recovering your hard drives get your data back not too long after fixing it and update your Firmware.

The only reason I didn't update my Firmware is because the first few Firmwares Seagate released were actually bricking some peoples hard drives when updating to the new Firmware, but now I have read the Firmware is stable. Another reason is I'm waiting on my 4 Western Digital hard drives and didn't think this error would come back so soon after fixing it.

I have sent the whole Seagate hard drive error story to one of our big TV News channels here in Australia with links and pictures and they will be airing it all over Australia soon and warning people to check if they have the faulty Seagate hard drives currently installed to be aware and backup immediately.

And to those Seagate employees who have registered here pretending they're an end user and sticking up for Seagate, PLEASE, I dare you, to bring me a story of another Hard Drive company that has faulted to this extent, with SO MANY people affected it by it, and still SO MANY more to come. Whatever story you tell me, I can guarantee you it hasn't affected as much people as this Seagate fault has. I have searched and searched for something as big as this Seagate fault and I can only find small problems compared to this world wide Seagate anger.

Folks, I too had the BSY problem and fought with seagate for a while. Ran into this topic and was relieved to find many others in the same boat. So I contacted seagate again and they offered a free solution. Unfortunately i365 said that it didn't work. So I got it back and was able to go through the solution posted here and success!

Now my HDD is working again and I'm actually typing from that computer right now. If anyone is in the STL area and wants to get your HDD restored using this method, shoot me an email. I've got the CA-42 cable and it worked magically

mundy5 are you telling me that you sent your Seagate hard drive to Seagate's hard drive recovery Department which is i365 and they said that they couldn't fix it and it didn't work ?? Then you fixed the hard drive YOURSELF using internet guides ?? Am I reading this right ?? Please confirm if this is what happened, because I'm really feeling sick right now.

Also kang roy why would you quote the WHOLE guide and then ask "Could this way to restore the data again arriving in the hdd?" I mean what a stupid question. After NUMEROUS people have confirmed fixing their hard drives with the guide, you still don't believe people or something ?? And even if you wanted to ask that, you don't have to post the guide.

Edited by the$#!Za.
0

Share this post


Link to post
Share on other sites
mundy5 are you telling me that you sent your Seagate hard drive to Seagate's hard drive recovery Department which is i365 and they said that they couldn't fix it and it didn't work ?? Then you fixed the hard drive YOURSELF using internet guides ?? Am I reading this right ?? Please confirm if this is what happened, because I'm really feeling sick right now.

You read my post correctly. I was able to restore the functionality of the drive which i365 claimed was inaccessible. I was then able to backup all the data and flash the new firmware. Shame on i365.

0

Share this post


Link to post
Share on other sites
And to those Seagate employees who have registered here pretending they're an end user and sticking up for Seagate, PLEASE, I dare you, to bring me a story of another Hard Drive company that has faulted to this extent, with SO MANY people affected it by it, and still SO MANY more to come. Whatever story you tell me, I can guarantee you it hasn't affected as much people as this Seagate fault has. I have searched and searched for something as big as this Seagate fault and I can only find small problems compared to this world wide Seagate anger.

Though I am not eligible as "undercover Seagate employee" ;), I can tell you a story :whistle: :

DeskStar/DeathStar

http://en.wikipedia.org/wiki/Hitachi_Deskstar

We had a report from a satisfied guy that got the drive repaired for free by i365

http://www.msfn.org/board/index.php?showto...807&st=2356

http://www.msfn.org/board/index.php?showto...807&st=2358

http://www.msfn.org/board/index.php?showto...807&st=2360

http://www.msfn.org/board/index.php?showto...807&st=2361

but I don't think he is an i365 "undercover agent".

@mundy5

I presume a "glitch in the matrix" :blink: , I guess that a single mistake can happen, nothing like the thousands (or tens or hundreds of thousands) bricked drives originating from Seagate mistake. (and as said many times, by the absolute unhelpfulnness of their asssistance :realmad: )

jaclaz

0

Share this post


Link to post
Share on other sites
mundy5 are you telling me that you sent your Seagate hard drive to Seagate's hard drive recovery Department which is i365 and they said that they couldn't fix it and it didn't work ?? Then you fixed the hard drive YOURSELF using internet guides ?? Am I reading this right ?? Please confirm if this is what happened, because I'm really feeling sick right now.

You read my post correctly. I was able to restore the functionality of the drive which i365 claimed was inaccessible. I was then able to backup all the data and flash the new firmware. Shame on i365.

Very strange indeed! One would think that Seagate's own data recovery service would know how to recover the data on their own products, especially when only looking at the label (7200.11 SD15) should ring all alarm bells. :rolleyes:

Edited by MadOCer
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.