• On CHOW: Sexy vampire party
January 21, 2009 9:39 AM PST

Seagate fixes 7200.11 drives--except when it doesn't

by Craig Simms
  • Font size
  • Print
  • 22 comments

Seagate on Tuesday released a fix to a bug in its current generation of drives that caused them to become undetectable by a computer. Users have found, however, that the fix breaks 500GB drives--the fix has since been retracted.

A member of Seagate's community forums raised the issue in November, with Seagate taking close to two months to offer a fix.

Seagate logo

The bug affects a significant portion of not only Seagate's Barracuda 7200.11 drives, but Barracuda ES.2 SATA and Maxtor DiamondMax 22 drives. Forums across the Internet have been filled with warnings not to buy drives that feature the SD15 revision of firmware; however, Seagate's own documentation shows that SD16, SD17, SD18, and SD19 are also affected within certain model numbers.

This is not the first time Seagate has had a firmware issue with the 7200.11 series of drives. The SD04 and SD14 firmware revisions were found to be under-performing because they weren't accessing the full cache of the drives, and were replaced with version AD14 to fix this.

The new SD1A firmware was meant to be preventative only, but some users have found success updating and reviving already dead drives, according to Seagate's forums.

Users of Seagate's Barracuda 7200.11 500GB product, however, have found that the update "bricks" their drives--terminology used in the tech industry to mean the unit is dead.

Seagate has since removed the firmware update, claiming it is "in validation."

U.S. customers have been offered free data recovery should the firmware bug have resulted in data loss.

The affected drives are listed below.

Drive type Drive model Firmware revision
Barracuda 7200.11 ST3500320AS
ST3640330AS
ST3750330AS
ST31000340AS
SD15, SD16, SD17, SD18
Barracuda 7200.11 ST31500341AS
ST31000333AS
ST3640323AS
ST3640623AS
ST3320613AS
ST3320813AS
ST3160813AS
All
Barracuda ES.2 SATA ST3250310NS
ST3500320NS
ST3750330NS
ST31000340NS
All
DiamondMax 22 STM3500320AS
STM3750330AS
STM31000340AS
MX15 or higher
DiamondMax 22 STM31000334AS
STM3320614AS
STM3160813AS
All

Craig Simms reported for CNET Australia.

Recent posts from Crave
The 404 474: Where we love Katie Couric almost as much as we love Jill Schlesinger
iPhone app rounds up free Redbox rental codes
Something to eye this holiday: Lower-end processors in a large-laptop body
The LP/CD smackdown
Three pre-Black Friday deals you shouldn't miss
ErgoMotion mouse swivels, pivots to save your arm
Ditto Book: Custom e-readers for a niche market
Crave giveaway of the day: Sony Bravia KDL-32L5000 32-inch LCD HDTV
Add a Comment (Log in or register) (22 Comments)
  • prev
  • 1
  • next
by TotalKonfuzion January 21, 2009 9:55 AM PST
Yup...I'm bricked and we're still waiting on another firmware release. My drive was working fine until I took the preventative measure...which killed it :)
Reply to this comment
by Jahntassa January 21, 2009 11:17 AM PST
Well..it prevented it from making things..worse.. No..wait..
by sabret00the March 23, 2009 12:12 PM PDT
Same here...I'm totally devastated. I had just backed up all my data into the 500GB and now it died upon me. I have always been a die-hard seagate fanboy...well now I'm regretting that.
by timber2005 January 21, 2009 11:25 AM PST
Its more like a list of "currently identified products" which seems to grow every few days.
Reply to this comment
by AnonTip January 21, 2009 11:27 AM PST
Prediction: Seagate will never recover from this disaster.

What an amazingly far-reaching impact from a small group of programmers too lazy and/or stupid to do a competent job - and the QA staff who utterly failed even the most basic testing.

Wow.
Reply to this comment
by NocturnalCT January 21, 2009 12:17 PM PST
Of course it's quite possible that a) QA wasn't given enough time to test or b) that QA found the bug but for whatever reason release management decided to proceed anyway.
by ajhoughton January 22, 2009 6:57 AM PST
It's also entirely possible that the QA people simply couldn't reproduce the problem. It's *extremely* unfair to jump to the conclusion that the problem would have been picked up with "the most basic testing". The fact is that you don't know how much testing took place, and you also don't know what the problem actually is or indeed how likely it is that the problem would trigger under any given circumstance.
by djames42 June 9, 2009 7:53 PM PDT
Why not? Microsoft constantly recovers from the effects of having a group of programmers too lazy and/or stupid to do a competent job - and the QA staff who utterly failed even the most basic testing.
by bdaleypsu January 21, 2009 11:49 AM PST
I had nothing but problems with the last several Seagate drives I purchased. The drives are loud and slow.

The last retail Seagate drive I bought started going bad within 6 months. I RMAed it, but they sent me a refurbed piece of crap to replace it.

I'll never purchase a Seagate drive again.
Reply to this comment
by Kikketer January 21, 2009 12:48 PM PST
I feel the same way about Seagate drives. I've also had a drive that refused to startup consistently when I booted the computer.
The RMA system was nice, they simply took it back but my replacement was a refurbished beast. I paid for a new drive...

Now that I see this, Seagate has reached the bottom of my list of hard drive vendors. I wouldn't even take one for free, data loss is a real killer.
by firefoxluva95 January 21, 2009 1:09 PM PST
This is good to know, I was planning to purchase a drive from Seagate and was comparing prices with Western Digital but now am officially swung over to the Western Digital side of the fence by this news.
Reply to this comment
by man_w_balls January 21, 2009 6:37 PM PST
Man, I got one of those recently...
it's the ST3500320AS model with firmware SD15

It's been working great for about a month now, no problems whatsoever.
What sort of issues should I be looking for?
Reply to this comment
by jaykay_rus January 21, 2009 11:09 PM PST
man_w_balls
In some of the techie forums it's been posted that the problems occur when the disk activity log file hits exactly 320 entries at the same time that the disk is booted. Thereafter the drive is not accessible and reports a size of 0kb. This is a firmware issue which Seagate are working to resolve; but as noted in the above report the data on the drive is intact and is not affected. If your drive is working OK now, the best advice is to keep it powered up, for the next few days, until a validated firmware revision is issued by Seagate. On the Seagate website you can register, by email, to receive the firmware revision specific for your drive - you don't need to send the drive back to Seagate.
Reply to this comment
by man_w_balls January 22, 2009 10:39 PM PST
thanks.
I may try the newly released firmware update mentioned on today's new Cnet article about this.

Or if it's a 320 entries in teh log file thing, maybe I should run 321 separate file I/O operations in rapid succession to get it past the 320-entry mark....
by reidjazz January 23, 2009 6:30 AM PST
"On the Seagate website you can register, by email, to receive the firmware revision specific for your drive - you don't need to send the drive back to Seagate."

man_w_balls, this is NOT true if you're on a non-Intel Mac...the firmware will not run on a PowerPC Mac...so, I'm stuck having to send my drive back to Seagate.
by seagatedrive January 22, 2009 10:08 AM PST
Update on Seagate's firmware upgrade:

Seagate has isolated a potential firmware issue in limited number of Barracuda 7200.11 hard drives and related SATA drives based on this product platform, manufactured through December 2008. In some unique circumstances, the data on the hard drives may become inaccessible to the user when the host system is powered on.

While we believe that the vast majority of customers will not experience any disruption related to this issue, as part of our commitment to customer satisfaction, Seagate is offering a free firmware upgrade to proactively address those with potentially affected products. This new firmware upgrade corrects compatibility issues that occurred with the firmware download provided on our support website on Jan. 16. We regret any inconvenience that the firmware issues have caused our customers.

To determine whether your product is affected, please visit the Seagate Support web site at http://seagate.custkb.com/seagate/crm/selfservice/news.jsp?DocId=207931

In the unlikely event your drive is affected and you cannot access your data, the data still resides on the drive and there is no data loss associated with this issue. Seagate is working with customers to expedite a remedy.

For assistance, customers can send an email to Seagate:
Americas: discsupport@seagate.com, disksupport@seagate.com
APAC: ssdc.apacsupport@seagate.com
EMEA: Euro.techsupport@seagate.com

Support is also available through Seagate?s call center: 1-800-SEAGATE (1 800 732-4283)
Reply to this comment
by sabret00the March 23, 2009 12:15 PM PDT
I hope somehow I can recover the data in my hard drive....I think that is the only way I'll ever get my faith back on Seagate
by nitrohelix August 24, 2009 11:06 AM PDT
I have posted a BSY error fix for Seagate 7200.11 model ST31000340AS FW 15

http://www.youtube.com/watch?v=29FztWJVxbM

Please rate and comment if it has been helpful to you, thank you!
Reply to this comment
by nitrohelix August 24, 2009 11:07 AM PDT
And btw, your data is totally recoverable after the fix. Just make sure to back it up immediately after!
Reply to this comment
by kinaton October 19, 2009 3:26 PM PDT
sorry to Bring up an old thread

But this article is incorrect.

Seagate/Maxtor say not all drives are effected.

stm3500320as
PN: 9GT154-325
FW: MX15
DC : 09221
SC: KRATSG

Are effected but only if your serial number is listed on their site.. I have had 2 of these drives that have failed with MX15 firmware, both serial numbers are showing as NOT AFFECTED on seagate site.

They are refusing to recover data, as they say these drives have mx15 firmware that isn't affect, now surely if you fixed firmware you'd give it a newer version..

Anyone have any ideas what I can do next.. as Seagate said they will only swap drive, and I should have backed up drives. (if you take that stance you'd need a room that could hold billions of drives, they suggested backing up, backups of backup etc etc.)
Reply to this comment
by daskinkaid October 27, 2009 11:18 AM PDT
I perform the unbricking programming on 7200.11 drives. Look me up under Wayman and Daskinkaid. Hope I can help you.
by Brian_Bates November 9, 2009 3:07 PM PST
Hey everyone!

My name is Brian and I own Nashville Tech Support in Nashville TN. We have recovered countless seagate harddrives and a lot of data for people with these Seagate 7200.11 harddrives. We have the special tools and knowledge to get data off these drives! We have started a flat rate deal for these drives! Even if your drive is in warranty we can repair it without voiding the warranty. My techs and I are Certified HP Mastertechs. Call us today and get your data back! You can either ship your drive to us or drop it off at our repair center!



Hours:

Monday - Friday: 10am - 6pm

Saturday: 11am - 2pm



Nashville Tech Support

1515 Elm Hill Pike Ste 105

Nashville, TN 37210

(615) 457-1330



http://www.nashvilletechsupport.com
Reply to this comment
(22 Comments)
  • prev
  • 1
  • next

About Crave

The name says it all. Crave is our blog about gorgeous gadgets and other crushworthy stuff. If you would like to contact Crave with a tip or comment, please write to: crave@cnet.com

Add this feed to your online news reader

Crave topics

Firefox hopes to one-up IE with fast graphics

Windows 7 features called Direct2D and DirectWrite will speed up Internet Explorer 9 performance. But Firefox hopes it might retool for the same benefit first.

E-tailers linked to 'scam' blame customers

Priceline, Classmates.com, and Orbitz say customers should read the fine print before complaining about being charged to join loyalty programs they didn't want.