Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[OracleGoat]

@bernhardinjo

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.

Message Edited by OracleGoat on 01-21-2009 05:20 AM

[womanmarine]

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.

Thanks,

Ruth

PS:  I have also explained this in a seagate support ticket  that was elevated to support, but no response so far.

Message Edited by womanmarine on 01-21-2009 05:32 AM

[OracleGoat]

@womanmarine

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)

[go_gatrz]

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.id=ata_drives&thread.id=6051), out of the millions of drives shipped, we are still hearing about a relatively small percentage.  And why does time seem to factor into a firmware issue?  If it were a compatibility issue related to firmware, these things would drop dead right out of the box.  Firmware doesn't change with time.  But system events do.  Therefore, it must be something that requires a confluence of events to occur.  

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.

[Onesolo]

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.

[AlanM]

Seagate Tech Support is working on collating all the firmware-related emails together and then sending out a catch-all for them.  That is hopefully why your case disappeared.   They are working on that as top priority, but the firmware has to be certified before they can do that.  I am really sorry about the delay, but I am confident that they are working on it as fast as they can.  As it stands now, though, I know they hope to have this all done by this afternoon, but I don't know if that is certain.  Again, I'm very sorry.


I have a suggestion.

Go to whatever link(s) apply to your drive(s).  

http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207969
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207957
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207975

Then 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. 

[plph]

Hi all,

I own a ST3500320AS with SD15 firmware ; I have my drive from September 2008 and this http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951 is confusing because as model and firmware i'm affected but as production date not

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?

[zickvon]

Thank you for letting us know the progress, and keep us updated!

[MicE]

---

AlanM wrote:
... 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.

---

Alan,
I did that several days ago, but I did not receive any email even though the articles *were* updated (i.e. when individual links to drive models were added to the main article /KB207931/).

[OracleGoat]

Me too...

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