Sign in with
Sign up | Sign in
Your question
Closed

Seagate's Firmware Update Bricking Functional 500 GB Drives (*Update*)

Last response: in News comments
Share
January 20, 2009 2:31:42 AM

I am running Mac OS X (not hacked) on a 750 GB (ST3750330AS) drive, how the heck do I update the firmware now.... lol. I am not experiencing any issues till now though
Score
0
Related resources
Anonymous
January 20, 2009 5:45:51 AM

my ST3500320AS is ticking like a time bomb, i hope the new firmware can defuse it
Score
1
January 20, 2009 6:53:38 AM

My first ST3500320AS "died" and went to RMA-Land on August 23. I guess it must have been a prototype of the bad batch fron December..
My second ST3500320AS "died" last week and a new/fixed one is on the way.
Unfortunately, I have 4 more of the same model..
Life's not exactly wonderful when your RAID-0 dies.
Score
0
January 20, 2009 6:54:19 AM

fgdgmy ST3500320AS is ticking like a time bomb, i hope the new firmware can defuse it

I received a computer with two seagate ticking drives (2x250gb) last summer. I sent them to repair, as I didn't like the ticking, and was told that the ticking was perfectly normal, and not to worry.
I bought two western digital drives instead of using those ticking ones though. I just don't trust my company data to be on stuff that sounds like that...
Score
0
January 20, 2009 10:19:04 AM

I've always trusted Western Digital more. Back when warranties used to be the same, Western Digital was considered the higher quality brand. But when seagate bumped up their warranty time, everyone jumped on their bandwagon. Good marketing tecnique because everyone bought one. Now everyone's realizing that they're falling back on that warranty so much that the extra 2 years is worthless. :p  Irony.
Score
1
January 20, 2009 11:32:08 AM

Ha ha, I have two 7200.11 1.5TB in Raid 0 that I paid $199 each. They are selling for $129 after four months. Seagate SUX. Maybe I should buy three more and Raid 5 those drives.
Score
1
Anonymous
January 20, 2009 12:42:33 PM

That "December" stuff is rubbish. Seagate drives have been failing with the boot-of-death for the last six months and more. When mine went it was manufactured in July/August. When they say "through December", that's an Americanisation that doesn't mean "throughout December", it means "through until December".
Score
0
Anonymous
January 20, 2009 12:43:51 PM

"Users of 1 TB (ST31000340AS) and 750 GB (ST3750330AS) drives are reporting successful updates." Not true. My ST3750330AS firmware update failed on two different hdd controllers.
Score
0
January 20, 2009 1:10:55 PM

I've purchased 9 of the 1.5tb seagate drives in the last month or two. I got very lucky. They are all the exact same, except for the serial number and none of them are affected by the recent issues. We've got a ~5.5tb raid50 and a 3tb logical volume just chugging away, and we have a spare. It was risky, but nothing could match the storage density.

Considering that WD has their 2tb drives out soon though (or maybe they are out by now)...I probably won't buy seagate again for a while.
Score
0
January 20, 2009 1:12:06 PM

nekatrevenI've purchased 9 of the 1.5tb seagate drives in the last month or two. I got very lucky. They are all the exact same, except for the serial number and none of them are affected by the recent issues. We've got a ~5.5tb raid50 and a 3tb logical volume just chugging away, and we have a spare. It was risky, but nothing could match the storage density.Considering that WD has their 2tb drives out soon though (or maybe they are out by now)...I probably won't buy seagate again for a while.


This was for work btw...I only wish I was throwing that kind of money at my personal storage! :) 
Score
0
Anonymous
January 20, 2009 1:14:10 PM

They changed the language on the main article from "through December" to "in December" AFTER drives started getting bricked. They also revised and then removed the firmware after that.

"Note: This file has been updated as of Jan 19, 2008 4:15PM CST. Please re-download this if you have an earlier version."

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

Yes, Seagate thinks it's still 2008.


They also posted a serial number tool and then pulled it when things went bad; just like the firmware update.

It was located here: https://apps1.seagate.com/rms_af_srl_chk/

My drive's serial returned "IS affected" on that tool and it was PURCHASED in November. How can they then change the language to "manufactured in December" only when people start bricking their drives with the critical update.

This issue has been known for months and back in early January their customer support forum moderators started locking threads about it. Many users moved to another forum after that. http://www.msfn.org/board/index.php?showtopic=128092

The recent reports still use the "through December" language that was originally report BY Seagate.
http://techreport.com/discussions.x/16246
Score
0
Anonymous
January 20, 2009 2:11:25 PM

I have two of those 500GB doorstops now... and of course, I could not afford having two other drives to backup all my data on. I work from home, so most of my work stuff is on those two drives. I hurried and patched them so as not to loose my data. I look like an idiot now!

And BTW, I also have two WD drives... top of the line Raptors too. And guess what? One of them died on me in spring of last year and the other in December. And Hitachi? Well my brother got two of their 500GB drives and put them in a RAID 0 array... and guess what? One of them crapped out and he lost his data.

And Samsung's are noisy and unreliable drives.

So I don't know, SSDs maybe?

Oh, no wait... there less reliable than HDD.
Score
-1
Anonymous
January 20, 2009 2:39:59 PM

This is not about technical issue, any manufacturer can encounter it from time to time (remember IBM Deathstar?), the problem is about customers getting tired of being lied to again and again by this deceitful company. I have three 1TB Seagates, luckily they are in an array protected by parity, so unless they will go bust together as a group, I should have my data even after this type of failure, but I'm going to replace them with WDs anyway and not buying anything from Seagate in the future.
Score
0
January 20, 2009 6:56:00 PM

I see a class action lawsuit coming up this year...
Score
0
Anonymous
January 20, 2009 7:39:59 PM

I spoke with a Seagate tech support guy, he said the firmware update to fix the SD1A bricked 500GB drives is due within 24-48 hours.
Score
0
January 20, 2009 8:22:54 PM

Well I'm running a 750GB 7200.10, 1TB 7200.11, and 1.5TB 7200.11. I really hope they don't all die on me. That would be a lot of lost data (I don't have any of it backed up).
Score
0
January 20, 2009 8:48:26 PM

Quote:
I spoke with a Seagate tech support guy, he said the firmware update to fix the SD1A bricked 500GB drives is due within 24-48 hours.

I've got a new (12-12-08 from Newegg) Seagate Barracuda 7200.11 ST3500320AS (500 GB) SATA drive with Firmware SD15 - seems to be one of the possibly defective drives. I just tried to call Seagate but they are reporting "phone problems" with internal hard drive tech support ... strange :sarcastic: 

I sent an email with details to them, but no way I'm installing that drive until I get some "firm" answers to my questions.
Score
0
January 21, 2009 12:23:02 AM

anonymous333Note: This file has been updated as of Jan 19, 2008 4:15PM CST. Please re-download this if you have an earlier version.""Note: This file has been temporarily taken offline as of Jan 19, 2008 8PM CST for validation."Yes, Seagate thinks it's still 2008.

I didn't notice that, haha. Well, it's a quote, so I don't see any reason to change it :lol: 
Score
0
January 22, 2009 2:58:12 AM

Seagate just released new updaters. My ST3500320AS now works again.
Whew.
Score
0
January 22, 2009 4:04:14 PM

Seagate has released new firmware ISO's for effected HDD's. See this Seagate Knowledge Base article: Firmware Update for ... ST3500320AS, ST3500620AS, ST3500820AS, ST3640330AS, ST3640530AS, ST3750330AS, ST3750630AS, ST31000340AS [207951]

Please note that these updates appear to be drive specific and are ISO files. You will need to create a bootable CD to update the appropriate firmware. Seagate has included instructions on How to burn an .iso image onto a CD [201431]

Note that Alex Feinman’s ISO Recorder (Freeware) is the only free burning software they mention, but I believe you would be successful using the excellent (and free) ImgBurn version: 2.4.2.0. Just follow the instructions for creating a bootable disc from an ISO file.

Hope this helps.
Score
0
January 22, 2009 5:07:35 PM

The title of this topic has been edited by Jake_Barnes
Score
0
January 22, 2009 6:16:21 PM

Downloaded the ISO for ST31000340AS and burned a CD. The update from SD15 to this SD1A went without a hitch, except I had to exit the boot window and the menu listed my drive model along with the others, so you had to pick the drive model again. Probably 2 or 3 different ISO's for the different listed drive models with 3-4 on each ISO.
Score
0
January 26, 2009 5:11:36 AM

SOS : I am having ST3500320AS hard disk & today suddenly the computer is not recognising the Hard Disk. I am having important Data & programs on hard disk which needs to be retreived. I have purchased the drive towards end of november. I have downloaded the latest firmware from the site http://seagate.custkb.com/seagate/crm/selfservice/searc... & also downloaded the ISO to update the firmware.

Please advise will update will solve the problem & will I be able to restore the data ?
Score
0
January 26, 2009 5:13:02 AM

If it doesn't show up in the BIOS you can not flash the firmware and will need to RMA it.
Score
0
January 27, 2009 6:23:35 AM

I have tried detecting my Hard Disk in 2-3 different systems & in one system the drive is being detected in BIOS but having 0 GB capacity.
Can I update my firmware now ?
Score
0
January 27, 2009 9:26:31 PM

You can give it a try. If it's being seen it might work, but you'll have to just give it a go to find out.
Score
0
Anonymous
February 11, 2009 10:28:38 AM

My two hds with problems were bougth in 2008/04 and 2008/03.
Score
0
Anonymous
February 22, 2009 1:56:23 AM

can anyone tell me if the bricking issue is a problem for drives used in external USB cases too, or only for drives that are booted from? I have a ST31000340AS (SD15) as an external drive for backup data, so it has only had maybe 6-7 hours of actual usage..

However I've just noticed while drive sticker tells me its a ST31000340AS, the box it came in says ST310005N1A1AS... and the serial numbers dont match! This is the 2nd time this has happened to me, the first being when I bought 2 750gb for a raid1 work machine, which the boxes both said 7200.11, but one was actually 7200.10 (again wrong serial#)

Are the factory workers in Thailand idiots, with no packaging QC oversight? or is this a scheme to deprive people of warrantying/returning drives, since if they check and see mismatch serials they wont let you return it??
Score
0
Anonymous
March 31, 2009 12:05:33 AM

I had 2 bricked drives (250GB) and seagate Australia were very helpful in fixing them. They had the drives picked up by DHL, and I got them back within 3 days all in perfect running order. All free of charge.
Score
0
December 10, 2009 3:33:40 AM

I've had a terrible problem with reliability of Seagate 7200.10 and 7200.11 drives lately. Specifically, they fail out of RAID all the time. Seagate doesn't say much of anything about this in the public literature, but after multiple RMAs, I contacted them directly and their RMA "Engineer" said that the AS drives were not designed for, and would not be reliable in "Enterprise RAID" which he defined as RAID 5 or RAID 10.
When I pointed out that the RAIDs it was failing out of were on desktops, which these days come with on-board RAID controllers almost universally, he continued to insist that what I was doing was "enterprise".
It's well documented that there are firmware issues, but the real problem is that seagate is selling a product that isn't suitable for a large, and growing, segment of the market: anyone using RAID, and not making it clear that the product won't work reliably in that configuration.
I've been a loyal Seagate customer for decades (all the way back to Shugart Technologies drives in Northstar Horizons), but I have to abandon their products at this point. The combination of disingenuous marketing with testy RMA people (it's the luck of the draw, I've had some who helped, and others who were adamant that it was my fault) means that I can't rely on the things, and I have much better uses for my time than recovering data and waiting for RMAs.
Score
0
March 1, 2011 7:21:11 PM

El problema de este disco esta en el firmware de fabrica. Vino fallado. Hace mas de dos años que continuan los problemas ya que aun hay discos en el mercado con el firmware malo.
Lo que hay que hacer es actualizar el firmware antes de que falle. Si ya fallo, no se podra,

Otra opcion para recuperar datos es la de mandar el disco a una empresa de recuperaciones. Yo conozco estas tres por renombre: OnRetrieval, Ontrack y Onrescue.

Si se precisa, llamar y pedir presupuesto.
Saludos
Score
0
October 7, 2011 9:18:16 AM

Hi my 7200.11 with SD15 firmware 500 GB drives has just bricked and using a ridiculous procedure, I have managed to retrieve the drive with everything intact and securely backed up all data. I see most of the posts go back to 2009 so as at Oct 11, the question is do I apply the SD1A firmware upgrade or not? Any thoughts or experiences?
Score
0
October 7, 2011 9:34:14 AM

My drive model No is Model: ST3500320AS 7200.11 with SD15 firmware 500 GB drives
Score
0
July 9, 2012 11:04:33 AM

Hi Starman202, what kind of method do you employ to retrieve the drive? I am in the same situation as you were.
Score
0
!