Gradius2

The Solution for Seagate 7200.11 HDDs

4,868 posts in this topic

I have already fixed my HD, thanks to all of you, specially JACLAZ!!

One last question, this solution works for all kind of Seagate HD's with firmware SD15??

Thanks again!!

Thanks Jaclaz!

I am not sure to understand the question.

AFAIK the SD15 is specific to 7200.11 family (and corresponding Maxtor ones).

Most Seagate HD's will have the same (or a similar) "internal language" and TTL connection, possibly at a different BAUD rate for older models, but there can be several reasons why a drive is bricked or however not functioning, and this thread is not a "heal 'em all miracle cure", it is specific to a model and to the two described type of problems.

Happy to know there is yet another happy bunny around :):

http://www.msfn.org/board/index.php?showtopic=128727&st=10

@bip

Take it easy, man, noone is hear specifically to help you within a 5 hour timeframe. :)

Try reading the above and this post:

http://www.msfn.org/board/index.php?showtopic=128807&st=2367

This thread is about solving TWO problems (and these two ONLY):

  1. 0LBA
  2. BSY

Read the first post of the thread, and check if what you are experiencing is #1 or #2.

If it is not #1 or #2 as described there, then NO, unfortunately this guide is NOT for you. :(

jaclaz

0

Share this post


Link to post
Share on other sites

I have already fixed my HD, thanks to all of you, specially JACLAZ!!

One last question, this solution works for all kind of Seagate HD's with firmware SD15??

Thanks again!!

Thanks Jaclaz!

I am not sure to understand the question.

AFAIK the SD15 is specific to 7200.11 family (and corresponding Maxtor ones).

Most Seagate HD's will have the same (or a similar) "internal language" and TTL connection, possibly at a different BAUD rate for older models, but there can be several reasons why a drive is bricked or however not functioning, and this thread is not a "heal 'em all miracle cure", it is specific to a model and to the two described type of problems.

Happy to know there is yet another happy bunny around :):

http://www.msfn.org/board/index.php?showtopic=128727&st=10

jaclaz

As SD15 is especific for 7200.11 Seagate family and Maxtor, I was asking if it works for all hd's independently from it's capacity (500, 750 gb, 1tb...)

0

Share this post


Link to post
Share on other sites

As SD15 is especific for 7200.11 Seagate family and Maxtor, I was asking if it works for all hd's independently from it's capacity (500, 750 gb, 1tb...)

Yes, b/c it is a firmware issue, not a capacity issue.

0

Share this post


Link to post
Share on other sites

Hello

i'm new of this forum.

I'm italian graphic designer and i have three years of my work on a seagate barracuda 7200.11 (st3500820as - firmware sd25).

The hard disk in block and return I/O error and error 1117 error.

This guide is for me? Can i recover my data?

Thans a lot.

ps. the hd make a little click sound and sometimes the pc seen it as 0 gb and somethimes 2 TB.

somebody help me?

Can i use this guide for my st3500820as hard disk whith firmaware sd25?

Though I'm not a data recovery expert by any means, I've seen & heard enough drives fail for various reasons to say there are a few general rules of thumb/steps that I keep in mind...

(1) All hard drives fail at some point.

(2) When they do it will likely be at the worst possible moment.

(3) The FIRST thing to do with a drive that is behaving strangely (viewable one time, not the next, etc.) is to DO *NOTHING* with it!

Do not run tests as these may use the last useful access you have to a drive.

-- Drive Sounds --

If the drive is making ODD SOUNDS, this is NOT a good sign.

It can mean that as the drive is running the head may also be scraping the platters holding your data -- and in the process making it totally unreadable (to anyone including data recovery experts). The sooner you stop using it, the better and the more likely you will have data that can be retrieved. Running the drive or doing tests won't help, instead it will make things worse. If the sounds are ODD for the drive, skip the next step and figure it will require some sort of physical recovery.

(4) Get your data off the misbehaving drive.

Either power down or connect another drive and get your most important data backed up FIRST.

( a ) Copy your Key Data Only

Start with your key data (not your OS or stuff you can re-install) but your business files -- financial, creative, things that you cannot reproduce.

- AND/OR -

( b ) Do an image of the failing drive.

After getting your important data off do an image of the failing drive.

This will allow you to have a copy of the data to work with if the data fails and leaves you without access.

(5) Setup your system again without using the failing drive.

If you can do this, set your failing drive aside to work with (and recover anything else you had) at your leisure instead of when you are busy with other business things. That way, if it can be repaired you can do so without time pressure which can result in mistakes.

(6) BACKUP, BACKUP, BACKUP!

Set up your backup system. You don't want to go through this again. After you're back in operation, do it first so you have a backup.

Regular backups are your friend. Whether that's another HDD or DVD or tape.

Having your important data in 2 places (at least) gives you an opportunity to recover when a drive fails.

(7) Figure out if you can recover the failing drive.

These are not hard & fast, but certainly something to keep in mind.

IMHO if you have years of important data on that drive, your first order of business would be to back it up by getting it OFF the failing drive -- but ONLY IF the drive sounds are normal. Be mindful that you may have only one shot to do this! So have everything ready before you power that drive back up. If you're doing a drive image have enough space to do the copy both on your OS HDD and the drive you're copying to.

If you have odd sounds, don't mess with it further as you may be ruining your data. A data recovery service may be able to help. One resource you may find helpful is a fellow by the name of Scott Moulton who runs courses and does data recovery (Google the name). I'm not affiliated but he provides some very helpful information (including YouTube videos) on general HDD data recovery. [The resource might be of interest to many on this thread. He has recovery services/courses at myharddrivedied.com ]

Sorry to sound negative here, but what you do next is important.

Others with experience with this particular firmware can certainly shed more light on your situation. For me, the sound aspect is very concerning, though it's hard to tell if 'little click' is the normal head positioning or something more sinister.

0

Share this post


Link to post
Share on other sites

(6) BACKUP, BACKUP, BACKUP!

Set up your backup system. You don't want to go through this again. After you're back in operation, do it first so you have a backup.

Regular backups are your friend. Whether that's another HDD or DVD or tape.

Having your important data in 2 places (at least) gives you an opportunity to recover when a drive fails.

Corollary:

In case you have any doubt about the meaning of the above, BACKUP! NOW! ;)

@bip

From a general standpoint, thus NOT necessarily applying to your particular case, a number of drives failing with a repetitive clicking sound can often be recovered by using professional tools, as they simply somehow "lost" some needed data.

The reviving is, again generally speaking, not at the level of knowledge of an hobbyist and needs very expensive tools, that are usually not worth the investment for anything but a number of drives (we are talking of tools in the US$3,000 to US$10,000 range). :ph34r:

The problem, without having seen the behaviour of the drive - and I seem to gather from your post that it is an "intermittent" problem of some kind, is that it is even difficult to give you some advice.

On a mechanical "sound" drive, performing properly any of the fixes detailed in this thread won't do any harm, BUT we don't know which kind of problem you are actually having, so, better be safe than sorry and leave it alone.

If you have three years of your work on that drive, I guess you should be VERY careful with the idea of messing with it.

A simple triage method:

  1. Is the data on the drive worth more than a couple thousand US$ to me? (no matter if actual commercial value or sentimental value)
  2. Can I afford spending, if I am very lucky, a few hundreds bucks or if I am unlucky a couple grands for the recovery?

If you reply "Yes" to both questions, you should ask a professional service.

If you reply "Yes" to the first only, you should do nothing.

If you reply "No" to both, you may want to continue trying with "hobby" methods.

If you reply "No" to the first only, you are a rich man and you really should not be here, and you should have already sent the drive to a recovery firm. ;)

jaclaz

0

Share this post


Link to post
Share on other sites

i did everything for the BSY error. when i did the last step i got:

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

Max Wr Retries = 00, Max Rd Retries = 00, Max ECC T-Level = 14, Max Certify Rewr

ite Retries = 00C8

User Partition Format Successful - Elapsed Time 0 mins 00 secs

im missing the line:

"

User Partition Format 10% complete, Zone 00, Pass 00, LBA 00004339, ErrCode 00000080, Elapsed Time 0 mins 05 secs"

is this bad?

0

Share this post


Link to post
Share on other sites

Well, me and a friend tried the BSY fix yesterday using an USB/SERIAL/TTL connection to the PCB.

Everything seemed to go as expected and we followed each step exactly as stated. After the last step we got the "User Partition Format Successful" with the only real difference from the one in the guide being that it said "User Partition Format 5%".

The harddrive did begin to spin after we unplugged/replugged it in before the last steps when the PCB was screwed back on. Anyway, so then AFTER the last step we plugged it into the computer for reals, and BAM. Nothing at all, not even a spin up. I disconnected the PCB again and re-connected the TTL adapter, and now I can't even get a connection to it using the hyperterminal.

Any ideas? The harddrive contains a lot of data that we'd need to backup. Would a PCB switch do any good or would it potentially wreck the harddrive?

Edited by HamsterMan
0

Share this post


Link to post
Share on other sites

Once fixed the 0LBA and BSY problem, has anyone get the problem again? What do you recommend? To update the firmware version? To stay with SD15 (and to fix it again if the problem comes back)?

Has anyone tried to contact with SEAGATE in order to replace the 7200.11 for a new 7200.12 without problems?

0

Share this post


Link to post
Share on other sites

Once fixed the 0LBA and BSY problem, has anyone get the problem again? What do you recommend? To update the firmware version? To stay with SD15 (and to fix it again if the problem comes back)?

Has anyone tried to contact with SEAGATE in order to replace the 7200.11 for a new 7200.12 without problems?

Of course you upgrade the firmware! That's the firs thing that you should be doing right after fixing your hard drive.

I have heard that people get their data salvaged for free if you send it to Seagate and explain what happened. It's a known bug, so you don't have to pay for the data recovery.

0

Share this post


Link to post
Share on other sites

Not sure if I should start a new thread for this, but since it's related to the 7200.11 (& 7200.10) firmware issues, I'll post here.

We have several (too many!!) Seagate hard drives of various flavors & firmware:

1.5TB

+ CC1H – 7200rpm (7200.11 model)

+ CC34 – 5900rpm (LP model)

500GB

+ 3.AAE – 7200.10 model

+ 3.AAF – 7200.10 model

+ SD15 – 7200rpm (7200.11 model)– FAILED

320GB

+ 3.AAC – 7200.10 model

250GB

+ 3.AAH – 7200.9 model

Seagate's s/n tool indicates a firmware update is required only for the SD15 500GB drive that failed.

[ Seagate S/N Lookup Tool Link https://apps1.seagate.com/rms_af_srl_chk/ ]

Even though the tool states the other firmwares are fine, I'm wary. So I've done google searches for the others without much success.

As near as I can tell and from what I’ve found so far – the CCxx and 3.AAx firmwares do not require updates.

Can anyone point me to additional information on any of the non-SD15 firmwares?

Any experience suggesting that my conclusion that the CCxx and 3.AAx firmwares don't require updates is incorrect?

0

Share this post


Link to post
Share on other sites

Once fixed the 0LBA and BSY problem, has anyone get the problem again? What do you recommend? To update the firmware version? To stay with SD15 (and to fix it again if the problem comes back)?

Has anyone tried to contact with SEAGATE in order to replace the 7200.11 for a new 7200.12 without problems?

Of course you upgrade the firmware! That's the firs thing that you should be doing right after fixing your hard drive.

I have heard that people get their data salvaged for free if you send it to Seagate and explain what happened. It's a known bug, so you don't have to pay for the data recovery.

I got in contact with Seagate and explained what happenend. The told me to contact with I365 and explain to them it was about the firmware problem. They told me to send it to them, they will upgrade my firmware and send the hd back to my home.

Well, i send it to them and they replied me this:

Buenos Dias, (Good morning)

Lamentamos informarle que el flasheo no ha sido suficiente para volver a hacer funcionar su disco normalmente. (We are sorry but flashing wasn't enough to make the hd work well)

El disco tiene también errores de lectura. (HD has reading errors)

Encontrara ajunto un presupuesto para el proceso de recuperación de sus datos. (Attached you will find a budget for the data recovery: IT WAS 775€)

Si no le interesa la recuperación, podemos mandarle de vuelta su disco ( 25 euros de gastos de envió) o pasarle al servicio de garantía para que le cambian. (If you are not interested in data recovery we can send your hd back (25€ shipping cost) or forwarding it to the warranty service to get it changed.

Saludos, (Greetings)

Jean-Philippe Richard

Customer Support

T 0031 20 655 6477

F 0031 20 655 6499

jeanphilippe.richard@i365.com

WWW.i365.com

As you can see, they were lying, because i could repair my hd without any problems and it works well. They just want to earn MUCH money from costumers that want their data desperately. I think that 775€ for 10 minutes is VERY MUCH.

So you recommend to upgrade to the new firmware, don't you? Aren't there any know problems related with this new firmware?

Thanks a lot to all of you!

0

Share this post


Link to post
Share on other sites

@jengitsme

My experience confirms yours with i365. They do not appear to be interested in fixing the problem anymore. I ended up having to fix it myself, backed it up and then sent it in for exchange with Seagate since it also failed the short DST test.

I'm very disappointed in i365 for their lack of desire to help. They only want money.

@valkyrio

What you said might have been true say 1 year ago but now the standard line is that the flashing of new firmware did not take place, there is nothing they can do except to try to recover the data costing us $700. I actually sent an email to my i365 agent shaming him and his tech for not doing their jobs knowing full well that this is a fixable problem without having to go to data recovery.

anyway, enough i365 bashing for the day.

Edited by mundy5
0

Share this post


Link to post
Share on other sites

I will not start bashing i365 again (I already did on page 123) :sneaky:

I have heard that people get their data salvaged for free if you send it to Seagate and explain what happened.

In fact they don't...

They don't even acknowledge there's a problem with the firmware and they'll direct you to the company I will

not mention here and these guys will ask you money for the operation :angry:

(900 Euro's in my case... excluding VAT)

Has anyone tried to contact with SEAGATE in order to replace the 7200.11 for a new 7200.12 without problems?

After having resolved the problem myself (for around 10 Euro's on parts and a few minutes of

my time), I backed up all essential data, did a zero-fill format using SeaTools for DOS and

returned the drive under warranty.

A few days later I got this drive in return:

ST3500320AS_Repaired.jpg

As can be seen, it's a repaired 7200.11 drive with the newer SD1A firmware, not another type of drive.

Greetz,

Peter.

0

Share this post


Link to post
Share on other sites

I will not start bashing i365 again (I already did on page 123) :sneaky:

I have heard that people get their data salvaged for free if you send it to Seagate and explain what happened.

In fact they don't...

They don't even acknowledge there's a problem with the firmware and they'll direct you to the company I will

not mention here and these guys will ask you money for the operation :angry:

(900 Euro's in my case... excluding VAT)

Has anyone tried to contact with SEAGATE in order to replace the 7200.11 for a new 7200.12 without problems?

After having resolved the problem myself (for around 10 Euro's on parts and a few minutes of

my time), I backed up all essential data, did a zero-fill format using SeaTools for DOS and

returned the drive under warranty.

A few days later I got this drive in return:

ST3500320AS_Repaired.jpg

As can be seen, it's a repaired 7200.11 drive with the newer SD1A firmware, not another type of drive.

Greetz,

Peter.

So it would be the same to upgrade the firmware by myself...

The drive you returned was working? Did they asked something about why did you sent it?

0

Share this post


Link to post
Share on other sites

At first glance it worked without any problems (even didn't update the firmware), but mundy5

advised me to do a "Short DST" test with SeaTools for DOS...

...which failed misserably :angry:

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

...but a "Long DST" test would run (only it took over an hour and a half) :wacko:

--------------- 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 ]
// JUST A LONG LIST OF REPAIRS HERE //
[ 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

I then filled in an RMA, giving the test-code returned by SeaTools ("A7E7D56A")

and I had to ship the drive back to Seagate (after I had done the full wipe) ;)

A couple of days later they return the other drive pictured in my previous post.

So check the drive first with SeaTools for DOS: if it does give you an error test-code

return it to Seagate, if not: I think it's safe to say it's okay (and then you could do

the firmware update if you wish).

Please be aware that SeaTools for DOS does not support all types of SATA chipsets; it

refused to see my drive when connected to a Promise controler (as I soon found out).

Greetz,

Peter.

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.