Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

THANK YOU everyone who has been so helpful in this thread, I finally got my drive back! I used the USB-TTL cable from Adafruit. I had no luck with a CA-42 cable I found online; the loopback worked, but as soon as I plugged it into the harddrive it became useless...couldn't even open a com port. I thought I shorted out the cable somehow, so I ordered the exact same one from the same place. I was more careful with the connections the second time, but the same thing happened. Considering the TTL cable comes with pins already attached, and the wide range of manufacturers and specs of the cell phone cables, I would really recommend you find a USB-TTL cable. That goes double for anyone on the east coast (Im in Boston), I could only find Nokia cables shipping from California.

I am having a problem updating my firmware. This came from an HP computer, and has the faulty firmware HP24 still installed. Their utility won't allow me to update to HP26, because I have upgraded to Windows 7. Burning the .iso to a disk can solve this for most people....but you have to change a SATA controller option in the BIOS to IDE. It seems their quad core BIOS does not have this option. Another awesome job HP.

Has anyone else been able to get around this? Is there another way to change the firmware (USB drive or through the hyperterminal connection maybe)? Will the seagate firmware run on this harddrive?

0

Share this post


Link to post
Share on other sites
That goes double for anyone on the east coast (Im in Boston), I could only find Nokia cables shipping from California.

Come on, anyone knows that Nokia cables coming from California are too ripe :w00t: to work properly (you know, too much sun, little water, etc.) however if squeezed provide an excellent cable wine.

:P

I am having a problem updating my firmware. This came from an HP computer, and has the faulty firmware HP24 still installed. Their utility won't allow me to update to HP26, because I have upgraded to Windows 7. Burning the .iso to a disk can solve this for most people....but you have to change a SATA controller option in the BIOS to IDE. It seems their quad core BIOS does not have this option. Another awesome job HP.

Has anyone else been able to get around this? Is there another way to change the firmware (USB drive or through the hyperterminal connection maybe)? Will the seagate firmware run on this harddrive?

I wouldn't risk flashing the "original" Seagate Firmware, it is possible that there are some settings that conflict.

I am not so sure about the changing in the BIOS to "legacy IDE".

It is very strange that such a setting is missing on a desktop (there are several laptops/notebooks I have seen missing this option, but never a desktop) are you really sure that such a setting isn't there - possibly renamed to something seemingly completed unrelated like "Data Bus translation" or "Foolproof setting" or "Install mode".

If such an option is actually missing it should mean that you are completely unable to install to that machine anything that has not Mass Storage drivers integrated. :ph34r:.

Maybe it is possible to have the .iso recognize the HD. :unsure:

Which exact .iso are you talking about (link please)?

jaclaz

0

Share this post


Link to post
Share on other sites

@jaclaz

hp is notorious for crippling original bios menus. I know what I speak of since I also own an hp from back in 99. It still runs but the bios stinks like no other.

@chinbender

unless hp has come out with their own updated firmware, i would not use seagates. hp and other oems use their own version of the firmware and you very well might brick it if you try using seagates.

as i said earlier, hp is notorious for crippling stuff possibly to keep their csr and tech support from having to fix people's mistakes in configuring this stuff.

regardless, the bios you get from buying your own motherboards is far superior. never again will i buy an oem computer and deal with the limitations there.

Edited by mundy5
0

Share this post


Link to post
Share on other sites
@jaclaz

hp is notorious for crippling original bios menus. I know what I speak of since I also own an hp from back in 99. It still runs but the bios stinks like no other.

Sure, I know :), but I would more happily "risk" udating a BIOS by installing temporarily the "original" motherboard manufacturer one (and then re-apply the OEM crippled one) then to apply a Seagate firmware to an OEM drive.

That is another possibility.

jaclaz

0

Share this post


Link to post
Share on other sites

@Gradius2 (and everyone else that contributed): thanks for this great solution to the BSY/LBA0-problem! :thumbup

Two weeks ago, I had this aweful BUSY-problem, but didn't know it was a known flaw in the HDD's firmware.

So after consulting Seagate, I sent my drive to the i365-branch here in The Netherlands (Europe).

Not long after, I roamed around the internet using Google (with the description of my problem) and found

that other post ("Seagate Barracuda 7200.11 Troubles") and discovered I wasn't the only one and soon

saw this thread ("The Solution for...")...

...but I'd already sent in my drive and when the guy of i365 rang me, I explained I wanted my drive to

be "Unlocked" so my BIOS would see it again and, if possible, to update its firmware (not telling him I'd

read your very informative posts) ;)

So I built the RS232 <-> TTL interface from spare parts I had lying around and tested it on some other drives

I have in my collection, to be sure it worked properly (even PATA drives work nicely).

rsconvertor.jpg

Because I didn't have to rush things (my drive was already away...) I even made it super-deluxe by putting

it into a small enclosure and separate switches for the drive's power and to disable the MAX-232 inside. B)

A few days after I received an e-mail with a price estimate for retrieval of my data (I'm a programmer, so I

badly wanted my latest source-codes back) and it shocked me quite a bit :wacko:

So I returned the e-mail by stating that I didn't want my data recovered and asked him to return the drive.

Well... today the doorbell rang and a courier handed me a nice box with in it... my precious drive.

I immediatly went upstairs (to my study) and connected my proudly made interface to the drive on one end

and the other end to my test-computer... performed your instructions (I only needed to unlock it from the BSY-

state) and... it was working again!

It's now busy copying everything to a backup, but I'm sure it will work flawlessly again (though I'm considering

updating my firmware to SD1A... but I've heard that version didn't solve the BSY-problem...)

Gradius2... you really saved my day (or actually the last two weeks) and I'm forever in your debt :wub:

It saved me E900 excluding VAT and it puzzles me they actually try to charge you for something that can be

done by someone with a little bit of electronics knowledge for around E10 (if you don't already have the parts

lying around like I had).

I'm even under the slight impression that they just have a template e-mail with some difficult phrases and random

numbers to let n00bs believe the drive really is damaged...

Maybe I should start my own "Seagate 7200.11 Recovery Service"? :P

Thanks again and greetz,

Peter.

Edited by VideoRipper
0

Share this post


Link to post
Share on other sites
I even made it super-deluxe by ....

Apart the fact that you have a "queer" idea of what "super-deluxe" means :w00t:, happy you are once again in the happy bunnies basket ;):

http://www.msfn.org/board/index.php?showto...28727&st=10

To have an idea, THESE:

http://www.datamancer.net/projects/optitran/optitran.htm

http://www.datamancer.net/keyboards/ergo1/ergo1.htm

http://www.datamancer.net/keyboards/keyboards.htm

are actual "super-deluxe" :whistle:

:P

About i365, it seems to me like they plainly LIED :ph34r::

We have finished examining all physical and logical components of your storage media. Based on your situation we have determined that your media has sustained a logical damage to the storage media. The main cause of damage is bad blocks which are present on the media, as well as media surface damage which prevents the read write heads from locating the data stored on the platters.

For the recovery process we need to analyze and repair these bad blocks, read out all data on a sector level, and reconstruct the complete file system. Afterwards we will mount the data onto an offline server in order to check the integrity of your data(partitions, directories and the different file types).

Tech report:

Mirror complete with 532 errors.

I don't think they can have done a "mirror" or analyzed bad sectors WITHOUT "unbricking" the drive, which would consequently mean that they "re-bricked" it on purpose :w00t: before sending it back to you.

Unless they exchanged the drives, are you positive it is the "right" drive and it does contains your data? :unsure:

532 errors (presuming that 1 error=1 unreadable sector) means 532x512=272,384 bytes unreadable or missing from your whole set of data, which I guess can be recovered/rebuild through software/differential backups or also re-written form scratch for far less than 900€+VAT.

jaclaz

0

Share this post


Link to post
Share on other sites

Hi folks.

I'm new to this forum and procedure, but not a noob. I am attempting to get the drive to unbrick; I have gotten the terminal to work properly, and I get commands to work, however, I cannot spindown the drive.

I always get the error message. To add insult to injury, at random times, the drive spins down on its own. I have always gotten one of the CC or CE error messages when attempting to spin the drive down and like I said, I have tried boatloads of timings.

Here's what I do: I start hyperterm on an XP box and connect the session at the same time I hit the powerswitch on the pSU (independent for hdd & adapter).

I wait 5 seconds for ctrl+z, and another 5 secs (T+:.10) for the /2.

I then wait 20 seconds (T+.30) and issue Z, however, sometimes the drive will have spun down already ,and sometimes it will not, and I always get a similar message.

I try w/ different timings, waiting longer than 20 seconds, same thing. I always get an issue. This drive will not detect in OS, so I believe to be bricked.

I have attempted looking thru pages, but with over 60 pages just on one item, it's a lot of information to go through. If anyone has had a similar case and had a successful outcome, can you tell me what you did? Or if I'm doing something wrong, can you point it out to me?

Thanks to any and all for your time and assistance. I can provide help on other subjects (other HW, networking, OS, etc), but this one is beyond my usual skill.

0

Share this post


Link to post
Share on other sites

@videoripper,

My experience with i365 here in the states has been the same. They gave me the same story of how my hdd has read errors. Now to be fair, after I unbricked the hdd and backed up everything, I ran the seatools tests on it and it said that it failed the short DST. So I am not doubting their analysis. In fact, I have sent mine back to get it replaced after everything was backed up.

What I am upset about is that they did not unbrick it for me so I had to do it myself to retrieve the data. They wanted me to pay them $700 to get the data back which for me cost $8.35 to get the screw driver and the CA-42 cable.

Unfortunate. So I recommend that you run the seatools for Dos on your hdd and run the short DST. See what it says.

@aftrshock,

In my experience, here is what you are not doing.

1. Open up your hyperterminal and have it ready to go.

2. connect the SATA power to your hdd and wait until everything is silent on the hdd. This usually took me about 30 or more secs.

3. Then connect the RS232 or USB cable to your computer.

4. Run the commands on hyperterminal.

In my experience, if I ran the commands while the hdd was booting on, it gave me the error message.

Edited by mundy5
0

Share this post


Link to post
Share on other sites

@mundy5

Thanks for the response. I timed it, and within ~28 seconds, the HDD had spun down on its own. This is I believe the relevant issue; I originally thought the paper I used was not enough to break the connection inbetween the data heads and the pcb. I am using a business card, so I'm fairly certain it is no longer making contact, but again, same thing. I will try just supplying power, and seeing how long until it turns off.

Within 35 seconds of power supplied, the drive stops spinning of its own volition.

Ideas?

0

Share this post


Link to post
Share on other sites

so after it spins down, you can now start the terminal process by hitting ctrl-z, etc.

my hdd would give me an error message if I tried to hit ctrl-z before it finished its boot process.

so wait 35 sec and go through the process of ctrl-z, Z etc.

0

Share this post


Link to post
Share on other sites

Amazing.

I swear I did that. It worked this time.

However, I'm getting spinup errors. I am wondering if it is because I connected the PCB incorrectly somehow, or if it is from the drive really having errors. I wonder if I can proceed anyway.

its Error 1009, DETSEC 00006008. The drive is indeed spinning however. Should I proceed anyway, or send it off for recovery?

I appreciate your time again.

-- edit

I'm probably just going to send this out for recovery. I don't want to damage anything; this has been a good learning attempt, but time to get back to regular work.

Thanks to everybody and especially mundy5 and Gradius for the expert help.

Edited by aftrshock
0

Share this post


Link to post
Share on other sites

I hope that you are following the steps exactly. After spin down, you need to remove the paper and reconnect the pcb and screw down the torx screws. then go onto the next steps. If you want to send it for recovery, it'll cost you a lot.

0

Share this post


Link to post
Share on other sites

The drive would indeed respin, only that there were errors involved like I mentioned. I think that this was bricked for damage, not from a firmware issue. Regardless of what I do, I get the error spinning up. Indeed I carefully removed the card and verified the connection afterwards.

The cost is not something I am concerned for; I am doing this for a friend and he wanted all low-cost, least-volatile attempts done before elevating. We're elevating. ;)

0

Share this post


Link to post
Share on other sites

Thanks for the responses. In hindsight, I'm not sure I know what to do with the .iso file. I thought if I burned it directly to a disk it would boot itself, but that may not be the case. I took a shot at making a bootable disk with Nero, using the Bootimage.img found within the .iso, but that didn't work either.

The .iso comes from HP, its called sp40966

HP tech support assures me that the BIOS settings do not interfere with the boot disk, but I'm not sure how much that's worth.

So if I can't get the boot CD to work, I think these are my options:

-Try to install the Seagate firmware. Risk possible permanent brick.

-Install manufacturer's BIOS to the motherboard, retry bootable CD. (I'm not sure if that's what you were saying mundy & jaclaz)

-Leave existing, faulty firmware. Unbrick HDD every few months.

Any other recommendations? The third option doesn't seem so terrible, I really am relieved just to have the drive and my data back.

I am having a problem updating my firmware. This came from an HP computer, and has the faulty firmware HP24 still installed. Their utility won't allow me to update to HP26, because I have upgraded to Windows 7. Burning the .iso to a disk can solve this for most people....but you have to change a SATA controller option in the BIOS to IDE. It seems their quad core BIOS does not have this option. Another awesome job HP.

Has anyone else been able to get around this? Is there another way to change the firmware (USB drive or through the hyperterminal connection maybe)?

Will the seagate firmware run on this harddrive?

I wouldn't risk flashing the "original" Seagate Firmware, it is possible that there are some settings that conflict.

I am not so sure about the changing in the BIOS to "legacy IDE".

It is very strange that such a setting is missing on a desktop (there are several laptops/notebooks I have seen missing this option, but never a desktop)

are you really sure that such a setting isn't there - possibly renamed to something seemingly completed unrelated like "Data Bus translation"

or "Foolproof setting" or "Install mode".

If such an option is actually missing it should mean that you are completely unable to install to that machine anything that has not

Mass Storage drivers integrated. :ph34r:.

Maybe it is possible to have the .iso recognize the HD. :unsure:

Which exact .iso are you talking about (link please)?

jaclaz

unless hp has come out with their own updated firmware, i would not use seagates. hp and other oems use their own version of the firmware and you very well

might brick it if you try using seagates.

as i said earlier, hp is notorious for crippling stuff possibly to keep their csr and tech support from having to fix people's mistakes in configuring

this stuff.

regardless, the bios you get from buying your own motherboards is far superior. never again will i buy an oem computer and deal with the limitations there.

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.