Jump to content
bnew

DO NOT update your firmware if you have a ST3500320AS drive

Recommended Posts

PSA:

 

As of the time of posting this thread, the latest update from Seagate to fix the firmware issue with the 7200.11 drives seems to be bricking the 500GB models (ST3500320AS). Basically, the firmware update process appears to work correctly, but when you next restart the pc the drives can't be accessed (appear in bios, but not much else). In addition, the firmware update program updates ALL valid drives that it can find without prompting, so some people that where trying to just update 1 of 2 drives are screwed too.

 

http://seagate.custkb.com/seagate/crm/self...sp?DocId=207951 is where the new firmware used to be able to be downloaded, but it has been pulled today as a result of the issue.

 

http://forums.seagate.com/stx/board/messag...ding&page=1 the saga unfolding on the Seagate forums.

 

Some people have had luck reflashing the drives with an older firmware. Personally, I'll be waiting for the offical word from Seagate.

 

Myself, I'm looking at 2 dead drives. I've got backups thankfully.

 

Be careful everyone.

Share this post


Link to post
Share on other sites

From the link

This file has been temporarily taken offline as of Jan 19, 2008 8PM CST for validation

 

Looks like it didn't fix anything that one ...

Share this post


Link to post
Share on other sites

From the link

This file has been temporarily taken offline as of Jan 19, 2008 8PM CST for validation

 

Looks like it didn't fix anything that one ...

From what I've read, it does seem to be working for other drives in the 7200.11 series like the 750GB and 1TB models. Just the 500GB ones are being stuffed.

 

The 'new' firmware download link was up for at least 5-6 hours, it was only pulled a couple of hours ago.

 

These jokers can't even get the date right. Try Jan 19, 2009

Edited by bnew

Share this post


Link to post
Share on other sites

I went back to WD...

 

Only because they were the cheapest drives that MSY had at the time

 

My WHS has Seagate, WD and Samsung drives.

Share this post


Link to post
Share on other sites

The fix for the Barracuda ES.2 drives is out

http://seagate.custkb.com/seagate/crm/self...sp?DocId=207963

 

It's the SN06 firmware but oddly, there's the AN05 firmware for the drives too to confuse people.

The AN05 seems to work better with some RAID cards according to the RAID card makers.

Edited by Jeruselem

Share this post


Link to post
Share on other sites

Not really much official word from Seagate thus far. The following is a comment from the Slashdot article which, if you believe the author, is from a current Seagate employee (and yes, wall of text does + 100 damage):

 

I work for Seagate. I was there when the fit hit the shan, and I saw everything going in internally, as well as externally.

I really love my job, so please excuse the sock-puppet nature that creating a brand new account and claiming to be an authority on the subject I must seem to be. But I am a geek, and I really think you all need to know the true story behind the scenes.

 

This whole thing started with the 1.5 Terabyte drives. It had a stuttering issue, which at first we all thought was a simple bad implementation of SATA on common chipsets. Seagate engineers promptly jumped in and worked to try to duplicate the issue and prove where the problem was. This wasn't a massive rush as 1.5tb drives are what? 5% of the drives on the market. When it became obvious that the issue was more widespread, they buckled down and put out a couple of firmware revisions to fix it.

 

Now, in the 1.5tb drives, there are 2 main revisions. the the product line that gets the CC* firmware, and the line that gets the SD* firmware. They came out with firmware CC1H and SD1A to fix these issues and started issuing them.

 

But, seagate has always been restrictive of handing out their firmware, so such updates required calling in with your serial so that the people who had access to hand out the firmware could check a) model, b) part number, and c) current firmware just to make absolutely sure that they were giving the right firmware out. This has been a procedre that has worked for YEARS up until now.

 

Then the bricking issue came to their attention. It took so long because it's an issue that's hard to track down - pretty much the journal or log space in the firmware is written to if certain events occur. IF the drive is powered down when there are 320 entries in this journal or log, then when it is powered back up, the drive errors out on init and won't boot properly - to the point that it won't even report it's information to the BIOS.

 

This is a rare, but still obviously bad issue. Up until now, we all figured it was just some standard type of failure, as it was such a rare event, so we'd RMA the drives.

 

So, for whatever reason, mid management started freaking out (as it could be a liability for seagate, I suspect - ontop of the already potentially liable issue of the stuttering problem causing drives to fail in RAIDs). So, they pushed the release of the SD1A firmware to the general public. They took a few days to 'test', though it was mostly just including some code in the batch file that kicks off the firmware updater, to check that it is a BRINKS drive, and the proper model number. Then it was kicked out to the public.

 

Please understand, this firmware had to go through five different checks to make sure it applies to the specific conditions to qualify sending to a customer, before now. 5 chances for us to go your drive needs the other (or none) firmware update. Suddenly, it's down to ONE check, and even that was more designed for a contingency just incase the wrong firmware was sent out.

 

Of course, it starts bricking drives.

 

Right now, the engineers are crapping themselves, the firmware's been pulled, the support agents are told to say "The firmware will be released soon" and no real procedure to fix this issue is in place. Our phones are flooded so bad that it locks the system up when there are too many calls in queue, and emails are coming in at hundreds an hour.

 

We simply cannot keep up.

 

The good news is, the chance of your drive simply not spinning up one day is very low. And for those of you who flashed the wrong firmware - be patient. It's not bricked, just unable to write data to the platters properly. When they have a *GOOD* firmware out, a new flash should un-brick the drives. If not, flashing it back to SD15 should make it work again.

 

Seagate really pushes the idea of being open and honest as much as we can without being sued to hell. They let agents make choices and use their skills instead of scripting us to death. They worked hard to bring their support back to the USA.

 

Seagate does care about their customers. They just got caught with their pants down, twice in a very short period of time! So, they're wanting to double, triple, and quadruple check the firmware so it doesn't brick anymore drives.

 

As for why it takes so long before an issue is reported and before seagate makes an announcement - we get a dozen 'reports' of issues that are really just one-off problems a day. It takes time for an issue to be 'significant' enough to escalate to the product teams, and time before they can provide a fix.

 

I hope this clears up a few things. I may or may not be able to answer questions if you have any.

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

×