Jump to content

The Solution for Seagate 7200.11 HDDs


Recommended Posts

@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
Link to comment
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?

Link to comment
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.

Link to comment
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
Link to comment
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.

Link to comment
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. ;)

Link to comment
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.

Link to comment
Share on other sites

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.

At least they could.

At data recovery service it is not unusual if you except the electronics to be broken to exchange it with a working one.

That would not work on our desktop because the new electronic does not have the correct drive parameters.

But a skilled service guy has probably a patented "One - Button - Drive Calibration" software ;-).

BTW: Seatools for windows can finish non of the tests on my laptop hdd. This is rather a sign of bad tool and not of bad drive... (seatool does not give a usefull error message either).

Regards

Chilli

Link to comment
Share on other sites

@chinbender

The linked to .exe is nothing but a "self-burning" .iso image, El-torito floppy emulation DOS 2.88 Mb image.

I creates an 8 Mb ramdisk, and unzips to it:

  • brnkmoos.cfs
  • FDL.bat
  • fdl.exe
  • flash.BAT
  • HP26CE2D.bin
  • HP26CE3D.bin
  • HP2ACE2H.BIN

Contents of flash.BAT are pretty much straightforward:


cls
Echo off
set model=%model1%

Echo ************************************************************
Echo * *
echo * WARNING! F/W update will take approximately 1 minute! *
echo * DO NOT REMOVE POWER DURING THIS TIME!! *
echo * *
echo * You will see the command prompt when it is safe *
echo * to remove power. *
echo * *
echo ************************************************************

echo Seagate Firmware Download Utility v4.71

set softrst=none
fdl -s -b -x -v -h BrnkMoos.cfs


if errorlevel=9 goto ALREADY
if errorlevel=4 goto error
if errorlevel=2 goto WRONGMODEL
if errorlevel=0 goto done

:done
echo.
echo ****************************************************************
echo * *
echo * Eject the CD and power down your PC. *
echo * *
echo * After you power down the firmware update will be complete *
echo * and you can restart your PC. *
echo * *
echo ****************************************************************
goto end

:ALREADY
cls
echo.
echo ()========================================================()
echo () ()
echo () You drive already has correct firmware version. ()
echo () ()
echo ()========================================================()
goto end

:WRONGMODEL
cls
echo.
echo @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
echo @ @
echo @ Specific hard disk model not found or not a Seagate drive @
echo @ @
echo @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

goto end

:error
cls
echo.
echo ************************************************************
echo ************************************************************
echo ** **
echo ** DRIVE NOT DETECTED **
echo ** **
echo ************************************************************
echo ************************************************************
:end

Which ultimately sums up to:

echo Seagate Firmware Download Utility v4.71

set softrst=none
fdl -s -b -x -v -h BrnkMoos.cfs


if errorlevel=9 goto ALREADY
if errorlevel=4 goto error
if errorlevel=2 goto WRONGMODEL
if errorlevel=0 goto done

It seems to me quite obvious that if - for any reason - the drive is not detected, you get the "error".

Is this what you get when you run it? :unsure:

The CD seems to me like pretty much "portable", in the sense that it doesn't *look* like making any check about running on HP hardware, so the easiest solution is:

  • buy, rent, borrow, steal :ph34r: ANY other PC which has in it's BIOS a "IDE compatibility mode setting and flash your drive on that PC

The HP tool in other words, seems very like the "normal" Seagate ones:

http://seagate.custkb.com/seagate/crm/self...&NewLang=en

(I mean the .iso's there)

JFYI, and in case of further problems:

http://forums.seagate.com/stx/board/messag...ssage.uid=37144

An alternative would be getting the Seagate .exe and modify it's contents (look into "config.xml" ;)), but it is however risky business, and I would not personally update the firmware of anything under Windows, as there are more things that can go wrong than those that can go right, unless you have a very, very clean system disconnected from anything, etc., etc.

jaclaz

Link to comment
Share on other sites

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

It took some more effort than I expected.

For some reason the DOS-version of SeaTools can't see my drive while it's on a Promise SATA-controler and

the Windows version does detect it, but can't do any tests on it :angry:

So I had to connect it to another PC with another type of controler and tried the short DST test... which failed..

But a long DST test could be done (it took about 90 minutes to do) and it was able to detect a number of errors

that could be fixed.

Don't know if this is of any interest, but here's the log-file created:

--------------- SeaTools for DOS v2.17 ---------------

Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5
Max Native Address 976773167
Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB )
This drive supports Security Features
SMART Is Supported And ENABLED
SMART Has NOT Been Tripped
DST Is Supported
Logging Feature Set Is Supported
POH 5994 Current Temp 23

Started Short DST 2/12/2010 @ 11:37.4
DST -- FAILED - Read Element LBA = 0
Your SeaTools Test Code: A7E7D56A
Short DST FAILED 2/12/2010 @ 11:37.16
--------------- SeaTools for DOS v2.17 ---------------

Device 0 is Seagate Device ST3500320AS 9QM22HVN On Intel ICH5
Max Native Address 976773167
Device is 48 Bit Addressed - Number of LBAs 976773167 ( 500.108 GB )
This drive supports Security Features
SMART Is Supported And ENABLED
SMART Has NOT Been Tripped
DST Is Supported
Logging Feature Set Is Supported
POH 5994 Current Temp 23

Started Long Test 2/12/2010 @ 11:38.8
Your SeaTools Test Code: A7E7D55A
DST -- FAILED - Read Element LBA = 963648851
Short DST FAILED 2/12/2010 @ 13:20.9
[ 963580219 -- Repaired ][ 963581115 -- Repaired ]
[ 963582011 -- Repaired ][ 963628659 -- Repaired ]
[ 963629555 -- Repaired ][ 963631507 -- Repaired ]
[ 963632403 -- Repaired ][ 963633299 -- Repaired ]
[ 963634195 -- Repaired ][ 963635091 -- Repaired ]
[ 963635987 -- Repaired ][ 963636883 -- Repaired ]
[ 963638835 -- Repaired ][ 963639731 -- Repaired ]
[ 963640627 -- Repaired ][ 963641523 -- Repaired ]
[ 963642419 -- Repaired ][ 963643315 -- Repaired ]
[ 963645267 -- Repaired ][ 963646163 -- Repaired ]
[ 963647059 -- Repaired ][ 963647954 -- Repaired ]
[ 963647955 -- Repaired ][ 963648851 -- Repaired ]
[ 963649747 -- Repaired ][ 963650643 -- Repaired ]
[ 963652594 -- Repaired ][ 963652595 -- Repaired ]
[ 963653490 -- Repaired ][ 963653491 -- Repaired ]
[ 963654386 -- Repaired ][ 963654387 -- Repaired ]
[ 963655282 -- Repaired ][ 963655283 -- Repaired ]
[ 963656178 -- Repaired ][ 963656179 -- Repaired ]
[ 963657074 -- Repaired ][ 963657075 -- Repaired ]
[ 963659026 -- Repaired ][ 963659027 -- Repaired ]
[ 963659922 -- Repaired ][ 963659923 -- Repaired ]
[ 963660818 -- Repaired ][ 963660819 -- Repaired ]
[ 963661714 -- Repaired ][ 963661715 -- Repaired ]
[ 963662610 -- Repaired ][ 963662611 -- Repaired ]
[ 963663507 -- Repaired ][ 963664402 -- Repaired ]
[ 963664403 -- Repaired ][ 963666355 -- Repaired ]
[ 963667251 -- Repaired ][ 963668147 -- Repaired ]
[ 963669043 -- Repaired ][ 963669939 -- Repaired ]
[ 963670835 -- Repaired ][ 963671731 -- Repaired ]
[ 963673682 -- Repaired ][ 963673683 -- Repaired ]
[ 963674578 -- Repaired ][ 963674579 -- Repaired ]
[ 963675474 -- Repaired ][ 963675475 -- Repaired ]
[ 963676370 -- Repaired ][ 963676371 -- Repaired ]
[ 963676372 -- Repaired ][ 963980854 -- Repaired ]
[ 963980855 -- Repaired ][ 963981750 -- Repaired ]
[ 963981751 -- Repaired ][ 963982646 -- Repaired ]
[ 963982647 -- Repaired ][ 963983542 -- Repaired ]
[ 963983543 -- Repaired ][ 963985494 -- Repaired ]
[ 963985495 -- Repaired ][ 963986390 -- Repaired ]
[ 963986391 -- Repaired ][ 963987286 -- Repaired ]
[ 963987287 -- Repaired ][ 963988182 -- Repaired ]
[ 963988183 -- Repaired ][ 963989078 -- Repaired ]
[ 963989079 -- Repaired ][ 963989975 -- Repaired ]
[ 963990870 -- Repaired ][ 963990871 -- Repaired ]
[ 963990872 -- Repaired ][ 963992822 -- Repaired ]
[ 963992823 -- Repaired ][ 963992824 -- Repaired ]
[ 963993718 -- Repaired ][ 963993719 -- Repaired ]
[ 963993720 -- Repaired ][ 963994614 -- Repaired ]
[ 963994615 -- Repaired ][ 963994616 -- Repaired ]
[ 963995510 -- Repaired ][ 963995511 -- Repaired ]
DST -- FAILED - Read Element LBA = 964028566
Short DST FAILED 2/12/2010 @ 13:21.0
Long Test PASSED After Repair 2/12/2010 @ 13:21.0

Thanks again for all your help and greetz, :hello:

Peter.

Edited by VideoRipper
Link to comment
Share on other sites

@chinbender,

I've had success using iso recorder found here:

http://isorecorder.alexfeinman.com/isorecorder.htm

when it comes to burning iso image into a CD-R.

@Videoripper,

your error messages are basically identical to the ones I had. I sent it back for an exchange after I backed up everything. Mine ended up running so slow because of all these read errors, and I read somewhere that the short DST detects errors in the pcb and/or electronics portion while the long DST tests the physical disk itself.

Anyway, I'd recommend that you get your replaced via warranty if you can. My HD was running very slow.

Link to comment
Share on other sites

I was already planning on that, though I haven't experienced any performance issues (yet) ;)

Already backed up the entire drive... now I'm looking for a lean way to brick it again without

raising suspicion (these guys at the shop always check things before they'll swap them) :angel

Greetz,

Peter.

Link to comment
Share on other sites

actually, by failing the short DST you already have justification to get a swap. that is what I did. It does not need to brick. You need to copy that code that Seatools gave you ("Your SeaTools Test Code: A7E7D56A") and go to their website and request an RMA # under the warranty link. they will ask you for the code from the seatools test. then everything else is self explanatory and you'll get a replacement hdd.

Link to comment
Share on other sites

Hey there.

First, thanks for the guide, it's great. :)

Second, I've got a straange problem...

I have a Seagate Barracuda 7200.11 with the busy error, and I have finally managed to construct the circuit to access the disk. Checked with the loop, no prob.

So far, so good.

I managed to get trough all of the instructions until this line:

F3 1>N1 (enter)

I turned off power and waited for a few seconds ( can't remember how long, sadly...) then swapped it in, but after 20 seconds I didn't get the expected F3 T>...

I got F3 1>ÿ....

WTF...

Do you guys know what the heck happened?? The prompt froze after that and became unresponsive. I tried starting over, but no go. No response... I tried it again after restarting the comp and the whole shebang, but no response.

I checked with a loopback again after the reboot, and that worked just fine.

Any information or suggestion right now would be deeply appreciated.

Link to comment
Share on other sites

I got F3 1>ÿ....

WTF...

Do you guys know what the heck happened?? The prompt froze after that and became unresponsive. I tried starting over, but no go. No response... I tried it again after restarting the comp and the whole shebang, but no response.

I checked with a loopback again after the reboot, and that worked just fine.

Any information or suggestion right now would be deeply appreciated.

If you are in level 1, you need to type /T to get to the lower level. Try the whole process again. I do not understand what you mean by "and the whole shebang, but no response" do you mean by this that when you start over by inserting the card between the pcb and the motor connection etc? Or do you mean after N1 you get no response?

Try the steps again and be meticulous. As Gradius2 warned us, it is very easy to ruin the hdd so please be very careful and follow exactly what he says.

Also, after you unplugged and plugged it back in, did you hit ctrl-z like it says in the instructions?

Edited by mundy5
Link to comment
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.
×
×
  • Create New...