Most Popular
| Top Stories | Commented | Featured |
Weekend Open Forum: Your next hardware upgrade will be...? featured
4-Way Intel H55 Motherboard Shootout featured
Tech Tip of the Week: Customize Your Windows 7 Start Menu Button featured
Nvidia GeForce GTX 480 and 470 specs emerge
HP Slate coming with Atom and Flash in June for €400?
Microsoft removes XP Mode hardware requirements
TechSpot RSSHardware
Seagate offers new firmware for broken hard drives
It’s been a busy week for Seagate. After releasing a bug fixing firmware update earlier this week, which ended up causing more harm than good by bricking certain drives, the company is now giving it another go and has just shipped an updated firmware for all models of hard drives affected by the software flaw – namely the Barracuda 7200.11, ES.2 SATA and DiamondMax 22.
Seagate is assuring those with bricked hard drives due to the previous firmware that they shouldn’t lose any of their data as a result of the problems, but it has also pledged to provide recovery services at no charge if necessary. You can go to this website if your hard drive is affected and download the new working firmware – hopefully they’ll get it right this time.
Seagate is assuring those with bricked hard drives due to the previous firmware that they shouldn’t lose any of their data as a result of the problems, but it has also pledged to provide recovery services at no charge if necessary. You can go to this website if your hard drive is affected and download the new working firmware – hopefully they’ll get it right this time.
Related Stories
User Comments (8)
Post a comment| tonylukac on January 22, 2009 6:55 PM | They stated in some other article yesterday that they had
the firmware to fix the bricking issue. However, for my 1.5
terabyte ST31500341AS hard drive, the firmware still says
"In Validation". Lets get the story right, media. Luckily, I
didn't follow your previous instructions and brick my drive.
I think I will wait for failure before applying any
kindergarden flunkout firmware. The reason I found this
message board was for another Seagate drive issue.
|
| avoidz on January 22, 2009 7:16 PM | Seagate just screwed their reputation.
|
| avoidz on January 22, 2009 7:18 PM | Are you kidding? I can't type the word "rep-u-tation" here
because of the letters "p_u_t_a" in it? Ridiculous. Internet
censorship gone mad.
|
| Julio on January 22, 2009 10:53 PM | Not ridiculous censorship, just poor programming. Just fixed
that now 
|
| champmanfan on January 23, 2009 4:13 AM | Damn, don't Seagate test these at all? Like any new firmware/patches, leave it 2 weeks until the dust settles to see if people have issues. Anyone who jumps first always gets badly bitten.
|
| windmill007 on January 23, 2009 4:56 AM | Hummmm who updates there hard drive firmware anyways..... I
have always had Western Digital hard drives and never heard
of such a thing?
|
| MichaelLS on February 3, 2009 1:16 PM | Ahhhh, so this is what happens when your older staff retires
and you move the manufacturing off shore to save
money. Pssssst! Buy the SV drives. Working so far!! Nice new - very short - warranty Seagate! I think not!!! Lessons learnt the hard way Seagate.
|
| tonylukac on March 14, 2009 5:57 PM | Unusual that I cannot edit my remarks because it said they
expired. An update on the ST31500341AS 1.5 terabyte. It
started giving off a whining and clicking sound each boot
after about 4 minutes of runtime for a 30 second interval.
While it was whining, the data was unaccessable. Each time,
it then stopped whining and returned to normal. The serial
checker said the firmware didnt need upgrading. An email
reply explicitly said NOT to upgrade the firmware; to ship
it to them under the warranty. I was having luck that day,
so I upgraded the firmware from sd17 to sd1b against their
advice. The firmware was difficult to locate with 1000 or so
search results. The upgrade worked and the drive runs
normally without whining or clicking now. If I had sent it
in, I would have gotten a used, refurbished drive with the
same crappy sd17 firmware, which would have had the same
problem. Just wanted to let you know.
|
