01-21-2009 05:19 AM - edited 01-21-2009 05:20 AM
Your 1.5TB drive which comes with CC1H firmware ,reported by Seagate as it is "SAFE"
At least, i haven't see anyone report 1.5TB AS drive with CC1H firmware brick yet.
01-21-2009 05:30 AM - edited 01-21-2009 05:32 AM
Okay, I'm just a housewife trying to figure this all out. Do I have to worry? I have ST31000340AS [Hard drive] (1000.20 GB) -- SN 9QJ0R4RL Revision SD15 PN 9BX1A8-570
I've been trying to follow this issue, my Everest shows this drive as Buffer: Unknown, Seatools doesn't work. This is my operating system drive.
I'd appreciate any of you tech guys to give me some advice here. I am backing up to the best of my ability with the tools and resources I have.
PS: I have also explained this in a seagate support ticket that was elevated to support, but no response so far.
01-21-2009 05:38 AM
You are doing right things -> Backup whole drive to another brand's HDD or optical media
This drive comes with SD15 firmware is affected by the bug.
When the next firmware released...you may have to flash your drive.
(Of course .... only after you complete the backup)
01-21-2009 06:43 AM
Actually, his accounting is the first I've read that makes sense. As I questioned on my first post (http://forums.seagate.com/stx/board/message?board.
Normally, there is always a statistical probability that a drive will randomly fail. But if you have an additional design flaw that requires a confluence of low probability events to occur for a failure, it takes time to become a statistically significant outlier. And while the confluence of events may be a low probability for an individual drive, Seagate is dealing with large numbers on the total population side (anybody familiar with Blackjack & card counting?).
So while the probability of a single occurrence may be small (lets say 1/1000), that's still probably 10 times greater than what they normally expect. And that might mean an extra 10000 drives failing. For a company like Seagate, this becomes financially significant. But from an individual standpoint, you shouldn't get hysterical. But 10000 people screaming all over the internet 10 times a day makes for a lot of noise.
The real sin is that Seagate has not been very forthcoming on the issue and they prematurely released a "fix" that made the situation 100x worse than it should have been.
01-21-2009 06:46 AM
I'm the IT manager of a company, and last year I bought three Barracudas 7200.11, one 1TB (main disk of a workstation), one 750GB and another 500GB (main disk of a workstation).
I've been watching this thread since the beggining and I feel a bit lucky cause still none of my hard drives were affected by this problem and I still didn't applied any firmware.
I'm very disappointed with Seagate with their slow move on this subject, lack of testing and resolution for the problem.
01-21-2009 06:57 AM
01-21-2009 06:57 AM
I own a ST3500320AS with SD15 firmware ; I have my drive from September 2008 and this http://seagate.custkb.com/seagate/crm/selfservice/
I think a lot of you have drives made before Dec.2008 and we don't have a clue if we're affected or not.
Can anyone answer to this?
01-21-2009 08:15 AM
... in the top right corner, click on "Subscribe" and give it a valid email address. Thus, when those articles are updated, you will be notified.
01-21-2009 08:18 AM
I haven't see any e-mail notification about the KB updates after i subscribed them.
The only e-mail i got from Seagate is the case number notification after i sent them the service request e-mail