36 Comments(s). 1 Pages(s). Showing page 1. [ 1 ]

   #36. Posted at 03:54 PM on Apr 5th 2009 Edit   Reply

how can you upgrade firmware on a HDD that is not detected by BIOS? who are we to call?
collapse

   #35. Posted at 05:14 AM on Mar 2nd 2009 Edit   Reply

My drive updated to the new firmware just fine...but the drive failed a couple weeks later anyway, heh. The replacement drive came already sporting the new firmware. Hopefully it doesn't die as quickly. Had one of their 200GB drives die on me in the last month, too. Seagate's beginning to aggravate me. At least I got a capacity bump to 250GB when they replaced the 200GB, heh.
collapse

   #34. Posted at 11:34 AM on Jan 26th 2009 Edit   Reply

Man, I'm so glad that I switched to WD drives years ago and not dealing with this bull.

Seagate lost me when they tried to charge me for an express RMA, not sure if WD does the same thing tho 8 (
collapse

   #33. Posted at 11:29 AM on Jan 23rd 2009, Edited at 11:30 AM on Jan 23rd 2009 Edit   Reply

(Oops, posted comment in wrong article... never mind.)
collapse

   #32. Posted at 12:17 AM on Jan 23rd 2009 Edit   Reply

I can report that my ST3500320AS updated without incident. The drive is now reporting that it is running the new firmware, and all data appears to be intact.
collapse

   #14. Posted at 03:28 PM on Jan 22nd 2009 Edit   Reply

How would you know that your drive is among the few that are affected unless it bricks on you? And if it is bricked, how would you update the firmware yourself?

Seagate's statements don't really make sense.
collapse

   #8. Posted at 02:48 PM on Jan 22nd 2009 Edit   Reply

EPIC FAIL
collapse

   #7. Posted at 02:44 PM on Jan 22nd 2009 Edit   Reply

Will the fixed firmware fix, fix the fixed fix?
collapse

   #1. Posted at 01:51 PM on Jan 22nd 2009 Edit   Reply

What is with Seagate and nvidia these days?
collapse

   #15. Posted at 03:48 PM on Jan 22nd 2009 Edit   Reply

Me too. I've got a 250, a 320, and 2 750 gb drives, only one of which is bricked. I'd like to get the data off it, though.
collapse

   #13. Posted at 03:26 PM on Jan 22nd 2009 Edit   Reply

Schadenfreude is too rich here.

My heart is bleeding.
collapse

   #12. Posted at 03:17 PM on Jan 22nd 2009 Edit   Reply

collapse

   #11. Posted at 03:01 PM on Jan 22nd 2009 Edit   Reply

We promise, this time, the firmware fix will not brick your drives. No, really.
collapse

   #6. Posted at 02:30 PM on Jan 22nd 2009 Edit   Reply

*facepalm*
collapse

   #5. Posted at 02:14 PM on Jan 22nd 2009 Edit   Reply

Let me download that fix to my hard drive. Oh wait that's right I can't see my hard drive now!
collapse

   #3. Posted at 02:08 PM on Jan 22nd 2009 Edit   Reply

By the looks of things, the fix was rushed and the QA was barely applied to it. Oh well... At this point in time i couldn't care less. I don't have any of the affected drives and i won't buy new ones due to the 5 year warranty removal. I'll make sure to spread the word as well.

Adi
collapse

   #2. Posted at 02:04 PM on Jan 22nd 2009, Edited at 02:04 PM on Jan 22nd 2009 Edit   Reply

Here's hoping this one does the trick.

I've actually still got five Seagate drives in service in three systems, albeit none newer or larger than 320GB. Up until the stuttering and bricking problems started, they were one of the better-regarded names.
collapse
36 Comments(s). 1 Pages(s). Showing page 1. [ 1 ]
 
Name/Password: / Remember
Reply to:
[click to clear]

[RED] [GREEN]
[BOLD]
[ITALIC] [STRIKE]
[UNDERLINE]

Notice: All posts should abide by the rules, please.
Note: Ctrl-Enter submits the post. (In IE)
DThread keys: Click on a reply to position the blue bar. 'A'/'Z' move it up/down.
Jazztags: (they MUST be closed)
    r{ red }r     g{ green }g     /[ italic ]/     *[ bold ]*
    _[ underline ]_     -[ strike ]-     s[ sample ]s     o[ spoiler ]o  q[ (QUOTE) ]q