Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Gradius2

The Solution for Seagate 7200.11 HDDs

Recommended Posts

Yep, just give it a go :yes:

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 :hello:

Greetz,

Peter.

Share this post


Link to post
Share on other sites

After all your suggestions was successful in getting the 7200.11 out of the BSY state. A big thank you to all who helped out. I followed the step by step procedure at - http://sites.google.com/site/seagatefix/

Now I recalled that I had a couple of other drives which had similar problems where in the drive spins power ons, but is not detected in the BIOS. A problem similar to the BSY in the 7200.11 series drives.

I have a 160GB & 320GB SATA and 80GB & 250GB IDE drives all from the 7200.10 series. They spin fine but are not detected by the bios. Any DIY Fix in this regard via which I could try and fix these drives like the DIY Fix for the 7200.11?

Seems almost similar to the issue faced in the 7200.11 but these are 7200.10 disks and putting a plastic between the PCB and Head the drive does not spin. So am I missing on something. And I think the terminal commands may be different.

I found a post http://www.msfn.org/board/seagate-7200-10-hdds-fix-bsy-state-too-t133604.html

but if I place a plastic between the Head & PCB the HDD does not spin. But if I remove the plastic the head does spin, but nothing comes up in the terminal window. Hence is there more to it than what I am doing?

Thanks in advance for all the help.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

Yep, just give it a go :yes:

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 :hello:

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

Share this post


Link to post
Share on other sites

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..

Share this post


Link to post
Share on other sites
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... :unsure:

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). :whistle:

Good luck and keep us posted,

Peter.

Share this post


Link to post
Share on other sites
I have to ask this question...

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

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

For us: yes :thumbup

For drive-recovery firms: no :whistle:

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... :no:

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:

seagate_pata_diag.png

(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 :yes:

Greetz,

Peter.

Edited by VideoRipper

Share this post


Link to post
Share on other sites

Yep, just give it a go :yes:

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 :hello:

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.

Share this post


Link to post
Share on other sites
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 :thumbup

Share this post


Link to post
Share on other sites
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 :thumbup

I am just so very happy right at the moment.

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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 by jdogz100

Share this post


Link to post
Share on other sites

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 by AngelGL

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...