Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

Just another suggestion (which appeared on the previous page) is that not all CA-42 cables

are created equal. :no:

It seems that some (non-Nokia) cables only work good upto 9600 Baud, while you'll

need 38400 Baud to unbrick your drive.

You can test by shorting the TX- and RX-leads of the cable and performing a loop-

back test:

  1. First make sure your cable is plugged in and can be selected
  2. Connect the TX- and RX-leads to each other, creating a loopback
  3. Open HyperTerminal, select the CA-42 and use 9600 Baud for the speed
  4. Type some characters on your keyboard: they should be echood back
    on the screen
  5. Now close the connection, select the connection-properties and set
    the connection-speed a bit higher: 19200 Baud
  6. Again: type some characters and see if they get echood back exactly
    on the screen as you type them
  7. If it does: go back to step 5, but now select 38400 Baud and check
    the output given when typing on your keyboard
    If it doesn't: you'll have to get yourself another (type of) cable

Also (another tip): make sure you disconnect first before removing the cable

from the USB-port or the COM-port stays in an open state and can only be

reset by restarting your computer.

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

BOOM made it 4 more partitions almost 500gb of data back YEEEEEEEEEEEEEEES!

i made it with my 4 cable combo :/ (Red,black,white,blue) got till the point where i should power off the drive , instead i powered down the whole system(not reboot) and back in 10 seconds removing the usb before that and disconnecting from hyperterminal

started all back up,put usb back in pc, run hyperterinal and directly ctrl+z and the m0,2,2,,,,,22 command, and it worked!! powered down again, back up and everythings back :) so happy now, really thanks for the help you two, and for thanks for this great thread!

0

Share this post


Link to post
Share on other sites

Congratulations Eaglemania! :thumbup

Another bad drive can be scrapped from the list :ph34r:

Now:

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

will do! thanks again!

happy happy happy *jumps in circles*

0

Share this post


Link to post
Share on other sites

A firmware update is only necessairy to prevent this same thing happening again in the future,

after 320 log-entries (though you should try to get rid of the drive if possible).

But maybe jaclaz (or someone else) can eleborate on this? :unsure:

Yes, to re-iterate once again.

Seagate has somehow admitted that a firmware bug (according to them affecting only a very limited number of drives made in a certain factory and in a given timeframe, and only some of them, coming from one or a few of the manufacturing lines) are affected by this "circular register" bug.

Supposedly these few lines had incorrectly set in-factory testing procedure that left the drive in such a condition that when the drive LOG hit (320+n*256) with 0<=n<=255, the drive will lock.

In English there is a term for the above, which I cannot write here, but is 8 letter long, starts with B, ends with T and has as middle letters LS, you get the idea. ;)

There are some posts dealing exactly with the issue and the reasons and the numbers possibly involved:

From here:

http://www.msfn.org/board/index.php?showtopic=128092&st=1007

for about 30 posts

From here:

http://www.msfn.org/board/index.php?showtopic=128092&st=1042

for about 50 posts

What is not (as I see it ) properly perceived is that the log getting at 320 is just one of the possible causes for a bricking.

Logically this should lead to EITHER a LBA0 OR a BSY problem, but since anything about the matter is actually hushed up by Seagate, and none has a way to investigate the matter properly, let's assume that the SAME problem with log can actually produce two DIFFERENT types of bricking. :rolleyes:

There may be several causes (or maybe tens of them), completely unrelated to the "log at 320" one, that may cause the bricking.

We have now evidence, after more than one year from the initial reports and published solution, that a number of drives manufactured in various factories AND NOT manufactured in the originally given timeframe, AND also of different model/revision can (and have :ph34r: ) bricked themselves.

So there may be MORE reasons than the original one.

The opposite thing is happening now, the solutions provided by this thread - meant to ONLY fix the original issue - are seen by everyone with a failed hard disk as a "miracle cure for everything", it is NOT the case.

Replacing the firmware with a new version is pretty much pointless, as I see it, I guess I need to explain this part in detail.

  • IF the original firmware is buggy (re:320 log) AND it is the cause for the bricking THEN, assumed that the new firmware is NOT buggy (re:320 log), it DOES make sense to update it.
  • but on the other hand:
  • IF the original firmware is buggy (re:320 log) AND it is the cause for the bricking THEN, the worst thing that can happen to you is the need (since you have now the tools and the knowledge) to re-unbrick it every 6 months to 1 year.

There is ANOTHER possibility:

  • There are MANY causes for the bricking, not necessarily linked to a given firmware, and the solutions given in this thread may TEMPORARILY cure them, but since the reason is NOT ALWAYS firmware related, updating the firmware WON'T DO anything that prevents the bricking to re-occur.

As I see it, once a drive has bricked, the right thing to do is:

  1. unbrick it
  2. salvage the DATA on it
  3. EITHER:
    • RMA it and get a new one (if still under warranty)
    • throw the drive in the dustbin
    • use it (either the original one fixed or the re-furbished/new one) for a low-low risk backup (like second or third backup copy - and yes, you NEED AT LEAST 2 (TWO) backup copies on different media of any DATA that is worth anything to you)

IMHO, people thinking to:

  1. use it as "main" drive
  2. use it as "only" storage

No matter if with the old or new firmware, are playing with fire, and it is statistically evident that when playing with fire burns happen more often than when playing with sand or mud. :whistle:

jaclaz

0

Share this post


Link to post
Share on other sites

Amen to that ;)

We should make a sticky of this thread... oh wait, it already is! :thumbup

0

Share this post


Link to post
Share on other sites

I am fixing the BSY Error, I wollowed the steps till turning the power off and on before pressing (after the i4,1,22 line). Now the terminal hanged up, i couldnt press ctrl+z and m0,2,2,,,,,22 ... The drive is running and I dont know what to do... Should I continue the procedure from ctrl+z and the m0,2,2... line? Or start from the beginning?

Thank you for any help, I am very worried for my drive, because on the first site it is written that if I turn the drive off I can lose all data :(...

0

Share this post


Link to post
Share on other sites

The Solution for Seagate 7200.11 HDDs (final and revised version):

Press CTRL+Z on terminal and type:

Partition regeneration:

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

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.

Gradius

hey,

iv'e accidentally turned the off the drive before getting the messages back from "m0,2,2,,,,,22".

now, when i powering up the drive, its making weird sounds of "beep, beep, beep".

did i totally bricked my drive? or there is a way back?!

thanx.

0

Share this post


Link to post
Share on other sites

I'm afraid so (but I can't say for sure of course) :}

You *could* try the following (untested and at your own risk):

  • Remove PCB from drive or insulate the contacts to the actuator/motor again
  • Apply power to PCB
  • Type: CTRL+Z which should give you the "F3 T>"-prompt
  • Type: "/2" to get to level 2 (prompt gives: "F3 2>")
  • Type: "Z" to "spin down" the motor
  • Reseat the PCB back to the drive (or remove the insulation)
  • Type: "U" to spin up the motor again (you should hear it spinning up)
  • Type: "/1" to go to level 1 (prompt shows: "F3 1>")
  • Type: "m0,2,2,,,,,22" (and hope for the best...)
  • WAIT until you see a message like:
    Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewrite Retries = 00C8
    User Partition Format Successful - Elapsed Time 0 mins 00 secs
  • If you get an error-message or the drive is "Beep-beep-beep"-ing again, it
    apparently didn't work and the drive is f****d up :wacko:
    (Or someone might have other suggestions?)

Above commands need to be entered without the "Quotes" of course.

Good luck,

Peter.

0

Share this post


Link to post
Share on other sites

BSY and the LBA0 problems do not have any beeping sounds associated with them. I'm afraid you now have a different problem.

hey,

iv'e accidentally turned the off the drive before getting the messages back from "m0,2,2,,,,,22".

now, when i powering up the drive, its making weird sounds of "beep, beep, beep".

did i totally bricked my drive? or there is a way back?!

thanx.

0

Share this post


Link to post
Share on other sites

I'm afraid so (but I can't say for sure of course) :}

You *could* try the following (untested and at your own risk):

[*]Remove PCB from drive or insulate the contacts to the actuator/motor again

[*]Apply power to PCB

[*]Type: CTRL+Z which should give you the "F3 T>"-prompt

[*]Type: "/2" to get to level 2 (prompt gives: "F3 2>")

[*]Type: "Z" to "spin down" the motor

[*]Reseat the PCB back to the drive (or remove the insulation)

Until here all fine.

this is the terminal output:

F3 T>/2

F3 2>Z

Spin Down Complete

Elapsed Time 0.135 msecs

[*]Type: "U" to spin up the motor again (you should hear it spinning up)

once im typing 'U', (terminal output: F3 2>U), this weird noise starts (and no output returned). maybe it's the motor not spinning?

any suggestions? im very frustrated.

thanx again.

Edited by sons
0

Share this post


Link to post
Share on other sites

i can get the drive to spindown F3 2>z spin down complete elapsed time 0.140 msecsbut get error 1009 DETSEC 00006008 spin error elapsed time 1min 57sec r/w status 2 r/w error 8415

gftfvnvfdsx

F3 2>Z

Spin Down Complete

Elapsed Time 0.140 msecs

F3 2>U

Error 1009 DETSEC 00006008

Spin Error

Elapsed Time 1 mins 57 secs

R/W Status 2 R/W Error 84150180

F3 2>

0180 please help or advise thanks

0

Share this post


Link to post
Share on other sites

@sons: if your drive was working normally before the BSY/LBA0-problem occured, I find

it highly unlikely, the drive motor suddenly stopped working while unbricking it...

But... anything is possible, of course. :whistle:

If you carefully tap the side of the drive with the handle-end of a screwdriver while trying

to spin up the drive-motor again, does it sound like it's spinning or is it still making all

kinds of unhealthy noises?

@hurn: of course I can't be sure about this (since I got my drive working at the first try),

but I guess that either the contacts of the motor or those of the actuator don't touch

the PCB properly...

Are they bent perhaps, or maybe they're dirty?

Normally it should only take about 5 to 10 seconds for the motor to spin up again,

not almost 2 minutes:

F3 2>U

Spin Up Complete

Elapsed Time 6.824 secs

Does it sound like it's spinning or is it staying dead silent?

Otherwise, it *could* mean the PCB is defective... :(

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

hi it sounds as though it is trying to spin up

0

Share this post


Link to post
Share on other sites

Ok...So, I have this problem, just found this thread, I've read several different versions of the instructions, even the ones on the google page.

BUT, my sata power cable I think for the harddrive? all the sections are black, and there's only four wires, whereas the ones pictured have six I believe with easily distinguishable colors.

I also don't have a serial port, so i'm assuming I'll have to use the nokia thingy for usb.

But the instructions seem like they're for advanced DIY'ers, I am far and away, an amateur. So is it possible to get the steps in laymens terms X:

Also perhaps a list of links to everything I would need to buy that I might not have? A retail list would be amazing.

Or perhaps there's a simpler way just to get the data off the drive? I care little for the drive it self, There's just a few folders I wish to save, maybe 10~20 gb's.

Any help is GREATLY appreciated, the 'bricking' of this drive has made the computer unusable[i'm saving up to build a whole new computer, didn't feel like spending the money on a replacement harddrive for this outdated one.

OH, also a list of programs I might need to do it? XP was on the harddrive so I'm not really sure what all I need.

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.