The Solution for Seagate 7200.11 HDDs

[VideoRipper]

Electronically 7200.10, 7200.11 and probably a lot (all?) of other Seagate SATA drives

are "Identical", so *in theory* the 7200.11 trick *could* work with the others.

However, this thread is for 7200.11 drives in particular and while its procedure *could*

be used on similar drives, you do it entirely at your own risk and your results may (WILL!)

vary, so only do it when you're at least a bit comfortable with electronics.

We cannot advise you on drives other than the 7200.11 ones here; you will have to start

your own new thread or find a similar one for your specific drive.

Having that said: the PCB on a Seagate drive houses a simple, but effective, diagnostics

environment; even with no drive attached, it should give you a prompt when pressing CTRL+Z

after having connected it to a RS232-TTL level port and applying power to the board.

First get that working before proceding...

Greetz,

Peter.

[bastianber]

Yep, just give it a go

Connect it to your PC the normal way and see if it's recognized

in the BIOS (and as the correct size).

Don't forget to update us on the progress

Greetz,

Peter.

I used:

F3 T>m0,2,2,,,,,22

as my command, and I have been waiting for the past 12 minutes now without any text showing....does it/ can it take longer? is it ok to take power out and try again?

Help please

[Salami]

I have to ask this question...

After all the bad thing the Seagate 7200.11 comes with, isnt it a good thing you can unbrick it?

When i look at my new Western Digital drive, there are no Pins leading outside, like on the Seagate.

Maybe (if a serial error as on the Seagate should happen on a WD drive) you have to solder some cables to the PCB to communicate with it?

I have

Seagate 7200.7 not recognized in Bios

IBM Deskstar IC35SL klicking noise

Maxtor 6Y120 klicking noise

Maxtor 6Y200 klicking noise

beside my desk for YEARS.

Maybe these also can be unbricked? Well, i`ll never know...

Just some thoughts..

[VideoRipper]

does it/ can it take longer? is it ok to take power out and try again?

With my 7200.11 drive it only took a couple of seconds, but as seen in khobar's case

it took a bit longer, so you might want to wait...

If nothing happens after, let's say, an hour or so, you might want to give it another

try after a "Drive reboot", but that's entirely at your own risk (as always).

Good luck and keep us posted,

Peter.

[VideoRipper]

I have to ask this question...

You really should start a new thread for this...

After all the bad thing the Seagate 7200.11 comes with, isnt it a good thing you can unbrick it?

For us: yes

For drive-recovery firms: no

When i look at my new Western Digital drive, there are no Pins leading outside, like on the Seagate.

I can only tell for my older WD PATA-drives and they have a 2*5 pin header

between the power- and the IDE-connector (for the master/slave, etc. jumpers)

that might want to talk with the outside as well, though I've never tried...

Other drives, might not even want to communicate (diagnostics-wise) using

"Normal" RS-232 protocols; there are a lot of others (like JTAG), as well

as non-disclosed ones.

Maybe you have to solder some cables to the PCB to communicate with it?

I highly double that, since that would mean drive manufacturers have to do

the same to diagnose their own products, though a PCB *could* indeed

have some pads for that purpose, who knows?

I have

Seagate 7200.7 not recognized in Bios

IBM Deskstar IC35SL klicking noise

Maxtor 6Y120 klicking noise

Maxtor 6Y200 klicking noise

beside my desk for YEARS.

Maybe these also can be unbricked? Well, i`ll never know...

Seagate 7200.7 (which is PATA) uses 9600 baud using these connections:

(Remember: RX of drive go to TX of PC and vice-versa and are also using TTL-levels!)

But... as said before, this actually belongs in a new thread

Greetz,

Peter.

Edited June 12, 2010 by VideoRipper

[khobar]

Yep, just give it a go

Connect it to your PC the normal way and see if it's recognized

in the BIOS (and as the correct size).

Don't forget to update us on the progress

Greetz,

Peter.

Many, many thanks for the help. I was able to completely recover the drive and transfer the image to a different drive (WD). I've brought up my critical video project and it appears to be completely intact.

Again, thank you.

[VideoRipper]

I was able to completely recover the drive and transfer the image to a different drive (WD).

That's great news!

Now have the drive swapped or if possible: refunded

[khobar]

I was able to completely recover the drive and transfer the image to a different drive (WD).

That's great news!

Now have the drive swapped or if possible: refunded

I am just so very happy right at the moment.

Question: can the drive be salvaged via firmware update? Will that "cure" the problem?

[VideoRipper]

You should even be able to use the drive for, lets say, 18 months with the current SD15

firmware without problems and de-brick it again after that.

The drive itself is not at fault, there's only a small problem with "Some overflow in

the LBA/SMART/whatever table after nnn entries".

The SD1A firmware update *should* have fixed this, but this hasn't been confirmed yet.

You're free to update the firmware, but it's just as easy to start an RMA at Seagate

and have the drive swapped for free.

I did that a couple of months ago, only to set my mind at ease

Just my 2 €-cents B)

Peter.

[jdogz100]

Hi to all, just wanted to a say big thanks for the "0 LBA" fix/solution it worked great.

Drive affected was a 1.5TB 7200.11 with "CC1H" firmware (thought this firmware revision had these issues fixed), showed up as 0GB under bios. Anyways used a third party Nokia "CA-42" USB cable and followed the solution to the letter.

Only real issue I had was getting the darn driver (not official nokia cable) and figuring out which wire was GND (Ground)(solved with loopback test in hyper terminal).

Edited June 15, 2010 by jdogz100

[AngelGL]

Hi to all,

I´m just connected my 7200.11 correctly, but crt+z doesn't do anything. The hyperterminal only receives "LED:000000CC FAddr:002493D1" each minute since I have conected to the hard drive.

Anybody knows how to overide this?

Thank you.

Update: I powered it off to reconnect it in a better place and now its almost blocked. And I say almost because when I disconnect the PCB from the main hard disk, it responds to ctrl+z. It´s possible to reset the HD PCB or something like that?

Edited June 15, 2010 by AngelGL

[gard04]

F3 T>/2

F3 2>Z

Spin Down Complete

Elapsed Time 0.146 msecs

F3 2>U

Error 1009 DETSEC 00006008

Spin Error

Elapsed Time 21.964 secs

R/W Status 2 R/W Error 84150180

F3 2>

The Registry is corrupt.

LED:000000CC FAddr:00270B3B

LED:000000CC FAddr:00270B3B

LED:000000CC FAddr:00270B3B

any solutions for a maxtor diamondmax 22 500go

[VideoRipper]

The hyperterminal only receives "LED:000000CC FAddr:002493D1" each minute since I have conected to the hard drive.

Anybody knows how to overide this?

Yes... read the procedure to the letter

Hint: you have to disconnect the motor and/or head-contacts from the PCB before

powering up the unit.

You'll get this message when the controller on the PCB was able to load the firmware

off the drive (it is stored on the platters, that's why you have to put in a cardstock).

Greetz,

Peter.

[VideoRipper]

any solutions for a maxtor diamondmax 22 500go

Loop up

This thread is for Seagate drives running SD15 firmware only

Greetz,

Peter.

[AngelGL]

The hyperterminal only receives "LED:000000CC FAddr:002493D1" each minute since I have conected to the hard drive.

Anybody knows how to overide this?

Yes... read the procedure to the letter

Hint: you have to disconnect the motor and/or head-contacts from the PCB before

powering up the unit.

You'll get this message when the controller on the PCB was able to load the firmware

off the drive (it is stored on the platters, that's why you have to put in a cardstock).

Greetz,

Peter.

It's not that case. You are talking about a message like "LED:000000CC FAddr:0025BF67".

But now my case is worst, the drive seems to be bricked definetely. It doesn't shows anything in the hyperterminal and doesn't do anything with crt+Z even with the PCB isolated of the drive.

Can I consider it a brick forever?

Thanks