Sign in / up

* Posts by verdilith

2 publicly visible posts • joined 19 Jan 2009

Seagate promises second fault fix in 24 hours

verdilith
Unhappy

oh no they haven't

"I'd still rather have a Seagate, while they acknowledge the problem and work on it"

Except customers have been begging them to do something about this problem for six months or more. My first ST3500320AS died in July 08, it was replaced and I didn't think anything of it because these things happen - sometimes you get a DOA. It's replacement died last week, and I'm thanking the gods of procrastination that I hadn't done anything with my old HD.

What annoys me most about this whole thing is that before El Reg and other online techie journals got wind of it, Seagate didn't want to know about the f/w problem. This could have been dealt with months ago.

0 0

Seagate isolates 'potential' Barracuda flaw

verdilith

not just 1TB drives...

it should be noted that it's not just the 1TB drives that are affected - mine is a 500GB one and bricked without warning a couple of days ago. Go onto Seagate's forums and you'll find that there are others too.

While it's good that Seagate are acknowledging the problem (at last!) it seems to me that unless you read techie forums and news sites, you may never know about this issue til it's too late. When the drive goes, it goes. No warning, no strange noises, no odd behaviour.

Incidentally, I'm starting to read on some forums about people who have attempted to use the firmware fix and the prog has crashed while denying the drive exists. IMO, Seagate have denied this issue for too long, then rushed a fix.

0 0