Seagate Barracuda 7200.11 Troubles

**DerSnoezie** · January 9, 2009

Sounds cool to me. And when things are finally wrapped up post the solution tutorial in a new thread so people won't have to filter through 14+ pages of posts.

That's true, but all I'm concerned about right now is getting the data back. They can keep their sodding POS drive for all I care. I want to keep this topic on fixing the problem, unless that's become an afterthought.
No, I don't think it's become an afterthought, it just requires some "behind the scenes" work that would cause the thread to become a bit obscure, especially to search engines. So the more updates we have on failed drives, the better this thread it will appear in Google and other search engines. So maybe what would be better thing to do, since this thread has a pretty good view count and listing in Google, is to start a thread dedicated towards writing the code for fixing it as both fatlip and pichi seem to be making strides in that area, and then relevant updates and links could be posted here. What does everyone think of that?

**waly2k1** · January 9, 2009

Hello I'm from Argentina and another user with this problem. My HD is ST3500320AS

SD15 firmware.

SerialNumber:Model:P/N:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:USername:Country Origin

======================================================================

9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet:Malaysia

9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule

9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie: Netherlands (no detect in bios)

9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:dskbrk

9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:ToKuRo:Chile (no detect in bios, reboot of death)

9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:jeroen__online

9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:quattro150:Malaysia

9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:Nichev

9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:PrOdiGy1

9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:AVINNC

9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage

9QM6354J:ST3500820AS:9BX134-505:SD15:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:rainshower

9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:fabio.cillo

9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia

9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:Taiketo

5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:Styleman

9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:roadstarter

9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:labraticmp3

9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:eli2k

9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:poim76

9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:caba212

9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:GrayGhost

9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09: timha

9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:viniciusferrao:Brazil

5QM1EYCG:ST3500320AS:9BX154-303:SD15:08383:WUXISG:jUL2008:02Jan2009:waly2k1:Argentina (no detect in bios). Product of China

**DerSnoezie** · January 9, 2009

Thanks

**pichi** · January 9, 2009

I each list had a flag, them would have 10 possible lists:

V001, V002, V004, V008, V010, V020, V040, V080, V100

Try it.

Some others lists have parts, merges, etc.

A lot of lists are reapeted on other indexes.

I don't know if only there are 10 lists or more.

**mikesw** · January 9, 2009

I bought 2 1TB 7200.11 ST31000333AS drives in the beginning of December 2008. I installed

one of them after Jan 1,2008 and have multiple partitions on it which only has 13gigs so far stored

on it. It isn't used for OS booting purposes. I haven't gotten around

to moving the Win xp sp3 OS from a 40gig seagate from around 2004 to this new drive yet.

The computer is a gx280 Dell with A08 BIOS version. The drive isn't set to go into hibernate mode.

It is booted up once a day and used for about an hour or two per day thus not 24/7 operation and

no RAID cards. The jumper on the drive was removed to let the BIOS and the 915G chipset auto-detect

the speed which will go to 150 MB/s since the chipset can't go faster.

The country of manufacture/origin is Thailand, firmware SD15, ST31000333AS SATA. Serial 9TE0....

So far no problems, but will keep an eye out. Others on the net have SD35 for this drive model.

No mention of SD2x where x is a number for these versions. Thus, hard to determine how many

different versions were released to the world between what I have and what others have.

Questions:

a). What is the affect of the bios clock and any internal timer/clock that the seagate drive has which

may be affected by the leap second that was added at the beginning of the year? MSoft had problems

with their Zune's which were dying all around the world. MSofts fix was to wait a little bit and the problem

would go away and thus wouldn't provide a firmware fix for this special case. Hmm, do the Zunes

use laptop Seagate drives? Which ones? Perhaps couldn't fix it since it was seagate related.

Do the drive internals have any clocks/timers in hardware or firmware that may cause the problem? What about the NCQ protocol or SATA Standard having any frame times being sent back and forth that work with the firmware that

could cause lockup/time syncing issues? Can someone set their BIOS clock before they bought the drive

and bootup to see if the BIOS detects the drive now?

b ). Is everyone using their drives as one partition (basic, logical, dynamic, raw) and maxing them out

or do they have multiple partitions.

c). Is it possible to turn off drive write caching and also NCQ'ng capability to see if the problem goes away?

I had to turnoff write caching for ZIP drives to make an Acronis software bug go away (as an example).

d). Here's a link to a person who's company bought 150 seagate drives. Within 4 months 37 died and

within 6 months they had an overall total of 51 new drives fail and 4 recertified drives fail.

See poster 9 at this weblink http://www.avsforum.com/avs-vb/showthread....21#post15419621

Edited January 9, 2009 by mikesw

**artpav** · January 9, 2009

Another st31000340as victim here, although I got my data recovered. I met the guy online, who swapped the data for me from faulty drive to a new one I gave him for a small fee. I wanted to ask him about details to help this discussion, but both times I met him, it was outside in freezing cold and so we couldn't talk for long, the only thing he said was to avoid 7200.11 series, and the fixed drive won't work for long before it locks with BSY signal again.

**icefloe01** · January 9, 2009

Here's a link to a person who's company bought 150 seagate drives. Within 4 months 37 died and
within 6 months they had an overall total of 51 new drives fail and 4 recertified drives fail.
See poster 9 at this weblink http://www.avsforum.com/avs-vb/showthread....21#post15419621

I just PM'd him on those forums asking if he would be willing to share his experience and drive information with us. That would make the list of drives even more impressive!

**criverock** · January 9, 2009

here my data!