Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Seagate 7200.11 fail & fine dataset

- - - - -

  • Please log in to reply
271 replies to this topic

#1
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09
Initial credits for the idea of this list go out to poolcarpet: http://www.msfn.org/...p...st&p=824992

To all seagate barracuda 7200.11 SD15 (and other version) owners, either broken down (by "no detect in bios", 0GB reported disc size & "the click of death") or still functioning fine:

Please register to the msfn forum and add your data to the list below so we can take a stand against seagate corporate practices. Moderators on the official seagate forum claim that our problems are not statistical significant, but judging from numerous complaints spread out over the internet we think they are! However, without a serious dataset (1000+ cases, from different countries) we don't stand a chance proving it statistically wise. So please help by adding your data.

Although the list is not helpful in restoring acces to the defective drive, we believe it is needed to:

1: Give an overview of the international spread of the problem
2: Document enough failures to disprove the claim of seagate moderators that this problem is statistically insignificant (And yes I consider this to be feasible, just look at how many people have viewed the main thread already! Their data (if relevant) is more than welcome)
3: Provide insight in the history and nature of the problem; when did the excessive failing start & do drives manufactured before a certain date last longer?

Personally I think that when the dataset includes enough drives over a large enough timespan (preferably including drives manufactured from september 2007 - present) patterns will emerge from the data, probably showing an increase in the rate of failures after a certain point in time. Ofcourse this is part speculation, but can you find (online) evidence of prior events where 7200.11 drives crap out at such a scale? If this point in time can be linked to a change in seagate production lines, like the arrival of new designs, new components, relocation to a new factory, etc. and combine this with the technical findings of fatlip, pichi, etc. we'll have a better chance understanding why this present massive failure event is happening.

Most of the data can be collected from the sticker on top of your harddrive (please keep in mind that you preferably do this when the computer is powered down, be safe). For purchase & fail date, use your memory or check receits/bills. If you are afraid that seagate will "blacklist" your drive, then only add the first 3 or 4 characters of the serial number. We will use a simple seagate date code calculator tool to translate the 5 digit code listed on your harddrive to the date it was manufactured. Thanks for your time and spread the word!

At the main thread sieve-x recently posted an official statement of seagate regarding the nature of this issue:

http://www.msfn.org/...mp;#entry830686


Upload your data in the following format:

Number:Serial N°:Model:Part N°:Firmware:DateCode:(manufac. date):SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of User:fail reason/fine:OS:PSU
====================================================================================================

1:9QM7****:ST3500320AS:9BX154-303:SD15:09146:2008-10-09:KRATSG:2008-10-15:2008-12-24:N/A:poolcarpet:Malaysia::
2:9QM6****:ST3500320AS:9BX154-303:SD15:09115:2008-09-17:KRATSG:2008-10-01:2008-12-28:N/A:DaftMule:UK::
3:9QM6****:ST3500320AS:9BX154-303:SD15:N/A:N/A:KRATSG:2008-12-05:2008-12-19:N/A:DerSnoezie:Netherlands:(no detect in bios):Vista Basic 64 bit:CM620W
4:9QM4****:ST3500320AS:9BX154-303:SD15:08503:2008-06-16:KRATSG:2008-08-01:2008-11-01:N/A:dskbrk:::
5:9QM3****:ST3500320AS:9BX154-568:SD81:08464:2008-05-20:KRATSG:2008-08-01:2008-12-23:N/A:ToKuRo:Chile:(no detect in bios):
6:9QM7****:ST3500320AS:9BX154-501:SD15:09134:2008-09-30:KRATSG:2008-10-28:2009-01-07:N/A:jeroen__online:Netherlands::
7:9QM2****:ST3500320AS:9BX154-303:SD15:08406:2008-04-10:KRATSG:2008-04-12:2008-12-23:N/A:quattro150:Malaysia::
8:9QJ0****:ST31000340AS:9BX158-303:SD15:08496:2008-06-12:KRATSG:2008-09-01:2009-01-08:N/A:Nichev:::
9:9QM7****:ST3500320AS:9BX154-303:SD15:09114:2008-09-16:KRATSG:2008-10-13:2008-12-14:N/A:PrOdiGy1:UK::
10:9QJ1****:ST31000340AS:9BX158-303:SD15:09063:2008-08-11:KRATSG:2008-11-01:2008-12-27:N/A:AVINNC:USA::
11:9QJ1****:ST31000340AS:9BX158-303:SD15:08515:2008-07-02:KRATSG:2008-08-01:2009-01-04:N/A:Ruddrage:UK::
12:9QM6****:ST3500820AS:9BX134-505:SD25:09084:2008-08-26:KRATSG:2008-07-01:2008-12-20:N/A:rainshower:Germany::
13:9QM3****:STM3500320AS:9GT154-325:MX15:08396:2008-04-03:KRTASG:2008-09-01:2008-12-30:N/A:fabio.cillo:Italy::
14:9QM*****:ST3500320AS:9BX154-303:SD15:08367:2008-03-14:KRATSG:2007-12-01:2008-12-01:N/A:Death_Angel:Malaysia::
15:9QK*****:ST3750630AS:9BX146-621:HP24:08511:2008-06-21:TK:2008-10-01:2009-01-07:N/A:Taiketo:::
16:5QJ*****:ST31000340AS:9BX158-303:SD15:09121:2008-09-20:WUXISG:2008-10-01:2008-12-28:N/A:Styleman:::
17:9QM8****:ST3500320AS:9BX154-303:SD15:N/A:2008-10-13:KRATSG:2008-12-06:2008-12-24:N/A:roadstarter:Philippines::
18:9QM6****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-15:2008-12-29:N/A:labraticmp3:USA::
19:9QM6****:ST3500320AS:9BX154-303:SD15:N/A:N/A:N/A:2008-10-01:2009-01-02:N/A:eli2k:::
20:9QM5****:ST3500320AS:9BX154-303:SD15:09063:2008-08-11:KRATSG:2008-11-06:2008-11-27:N/A:poim76:::
21:9QM2****:ST3500320AS:9BX154-303:SD15:08382:2008-03-23:KRATSG:2008-08-01:2008-11-30:N/A:caba212:Spain::
22:9QJ1****:ST31000340AS:9BX158-303:SD15:08496:2008-06-05:KRATSG:2008-07-01:2008-12-26:N/A:GrayGhost:USA::
23:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:2008-08-12:2009-01-09:N/A:timha:::
24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:2008-06-11:KRATSG:2008-10-01:2009-01-02:N/A:viniciusferrao:Brazil::
25:9QM6****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-31:2008-12-01:N/A:RiderZen:Australia:(BSY):
26:9QJ0****:ST31000340AS:9BX158-335:SD15:08457:2008-05-16:KRATSG:2008-07-01:2008-12-20:N/A:Macprk:USA::
27:9QM5****:ST3500320AS:9BX154-303:SD15:09071:2008-08-16:KRATSG:2008-11-04:2009-01-09:N/A:BigSilverHotdog:USA::
28:9QM2****:ST3500320AS:9BX154-303:SD15:08382:2008-03-23:KRATSG:2008-08-01:2009-01-01:N/A:Keddar:USA::
29:5QM1****:ST3500320AS:9BX154-303:SD15:08383:2008-03-24:WUXISG:2008-07-01:2009-01-02:N/A:waly2k1:Argentina:(no detect in bios):
30:9QM5****:ST3500320AS:9BX154-303:SD15:09063:2008-08-11:KRATSG:2008-07-01:2008-12-25:N/A:criverock:Italy:(no detect in bios):
31:9QM*****:ST3500320AS:9BX154-303:SD15:09076:2008-08-21:KRATSG:2008-10-01:2008-12-20:N/A:sarahcoco:France::
32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104:2008-09-09:KRATSG:2008-10-10:2009-01-03:N/A:artpav:Canada::
33:9QM*****:ST3500320AS:9BX154-303:SD15:08371:2008-03-15:KRATSG:2008-05-07:2008-12-29:N/A:KillerB:Korea:(no detect in bios):
34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:2008-07-30:WUXISG:2008-08-01:2008-12-24:N/A:Fuzzy_3D:Canada::
35:9QJ0****:ST31000340AS:9BX158-303:SD15:08356:2008-03-06:KRATSG:2008-03-01:2008-06-01:N/A:TheName:Croatia:(maxtor!):
36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:2008-07-01:2009-01-05:OEM:BARAKASPEED:Thailand::
37:9QM1****:ST3500320AS:9BX154-303:SD15:08364:2008-03-11:KRATSG:2008-05-01:2008-12-12:OEM:taa:Russia:(no detect in bios):
38:9QM6****:ST3500320AS:9BX154-303:SD15:09096:2008-08-12:KRATSG:2008-09-01:2009-01-07:OEM:kiave:Poland:(no detect in bios):
39:9QM0****:ST3500320AS:9BX154-303:SD15:08315:2008-02-06:KRATSG:2008-03-31:2009-01-11:N/A:laz:Canada:(no detect in bios):
40:9QM6****:ST3500320AS:9BX154-303:SD15:09082:2008-08-24:KRATSG:2008-12-01:2009-01-11:OEM:SeaGAYBarracuTARD:Canada:(no detect in bios):
41:9QM0****:ST3500320AS:9BX154-303:SD15:08243:2007-12-17:KRATSG:2008-01-01:N/A:N/A:dragtop:Canada:fine:
42:9QM8****:ST3500320AS:9BX154-303:SD15:09174:2008-10-28:KRATSG:2008-11-14:2008-01-11:OEM:harwin:Singapore:(no detect in bios):
43:9QM*****:ST3500320AS:9BX154-335:SD15:09054:2008-08-05:KRATSG:2008-09-26:2008-12-19:RETAIL:matildasmith:USA:(BSY):
44:9QM*****:ST3500320AS:9BX154-335:SD15:09085:2008-08-27:KRATSG:2008-12-30:N/A:RETAIL:matildasmith:USA:fine:
45:9QM*****:ST3500320AS:9BX154-335:SD15:09085:2008-08-27:KRATSG:2008-12-30:N/A:RETAIL:matildasmith:USA:fine:
46:9QM1****:ST3500320AS:9BX154-303:SD15:08337:2008-02-22:KRATSG:not sure(at least 1 year old):N/A:OEM:harwin:Singapore:fine:
47:9QM6****:ST3500320AS:9BX154-303:SD15:09085:2008-08-27:KRATSG:2008-09-30:2009-01-11:N/A:bp2411:UK:(no detect in bios):
48:9QJ2****:ST31000340AS:9BX158-303:SD15:09086:2008-08-28:KRATSG:2008-09-22:2008-12-26:OEM:Lippy:UK:(BSY):
49:9QM5****:ST3500320AS:9BX154-303:SD15:09062:2008-08-10:KRATSG:2008-09-04:2008-12-01:OEM:prim:Spain:(no detect in bios):
50:5QJ0****:ST31000340AS:9BX158-303:SD15:08516:2008-06-26:WUXISG:2008-11-13:2009-01-14:RETAIL:Karlston:Australia:(no detect in bios):
51:5QJ0****:ST31000340AS:9BX158-302:SD04:08185:2007-11-07:WUXISG:2008-04-06:2008-06-21:RETAIL:hallwal:USA:(0GB reported):
52:9QM8****:ST3500320AS:9BX154-303:SD15:09167:2008-10-24:KRATSG:2008-12-01:2009-01-11:OEM:s1lencer:Malaysia:(no detect in bios):
53:9QJ0****:ST31000340AS:9BX158-303:SD15:09012:2008-07-06:KRATSG:N/A:N/A:OEM:rimask:Singapore:(no detect in bios):
54:9QK0****:ST3750330AS:9BX156-303:SD15:09024:2008-07-15:KRATSG:2008-11-28:2008-12-30:OEM:valdas:Lithuania:(no detect in bios):
55:9QJ1****:ST31000340AS:9BX158-303:SD15:08526:2008-07-03:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:Debian GNU/Linux
56:9QJ1****:ST31000340AS:9BX158-303:SD15:08526:2008-07-03:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:Debian GNU/Linux
57:5QJ0****:ST31000340AS:9BX158-303:SD15:08524:2008-07-01:WUXISG:2008-08-01:N/A:OEM:me0w:Sweden:fine:Debian GNU/Linux
58:9QM4****:ST3500320AS:9BX154-303:SD15:08525:2008-07-02:KRATSG:2008-08-01:N/A:OEM:me0w:Sweden:fine:Debian GNU/Linux
59:9QM1****:ST3500320AS:9BX154-303:SD15:08345:2008-02-27:KRATSG:2008-03-30:N/A:OEM:me0w:Sweden:fine:Debian GNU/Linux
60:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FreeBSD 7.1
61:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FReeBSD 7.1
61:5QJ0****:ST31000340AS:9BX158-303:SD15:09133:2008-09-29:WUXISG:2009-01-01:N/A:OEM:jkc120:USA:fine:FReeBSD 7.1
62:9QM7****:ST3500320AS:9BX154-303:SD15:09116:2008-09-18:KRATSG:2008-11-25:2009-01-13:N/A:DeadST3500320AS:USA:(no detect in bios):
63:9QJ1****:ST31000340AS:9BX158-303:SD15:09107:2008-09-12:KRATSG:2008-11-01:2009-02-01:OEM:SSKEV:Greece:(no detect in bios):
64:9QM5****:ST3500320AS:9BX154-303:SD15:09077:2008-08-22:KRATSG:2008-08-30:2009-01-10:N/A:D3m3nt0r:Germany:(no detect in bios):
65:5QM0****:ST3500320AS:9BX154-303:SD15:08225:2007-12-05:WUXISG:2008-01-21:N/A:N/A:Jack_Steel:Austria:fine:WinXP_32bit
66:9QM*****:ST3500320AS:9BX154-303:SD15:09075:2008-08-20:KRATSG:2008-09-01:N/A:OEM:CheshireCat:Israel:fine:xp32pro_vista32ult_now
67:9SZ*****:ST3320613AS:9FZ-162-300:SD11:08391:2008-03-29:TK:2008-08-01:2008-12-22:OEM:kadolf:Germany:(0GB reported):WinServer 2k8 x64
68:9QM2****:ST3500320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:(unsure):2009-12-01:N/A:AlexLilic:Sweden:(no detect in bios):N/A
69:9QJ2****:ST31000340NS:9CA158-784:HPG6:09131:2008-09-27:KRATSG:2009-01-09:N/A:OEM:CGremlin:US:fine:Solaris
70:9QJ2****:ST31000340NS:9CA158-784:HPG6:09131:2008-09-27:KRATSG:2009-01-09:N/A:OEM:CGremlin:US:fine:Solaris
71:9TE0****:ST31000333AS:9FZ136-300:SD15:09101:2008-09-06:TK:N/A:RETAIL:toudoku:Japan:fine:w2k:
72:9QM1****:ST3500320AS:9BX154-303:SD15:08366:2008-03-13:KRATSG:Spring08:2008-12-01:RETAIL:idshark:Germany:(no detect in bios):Linux:BeQuiet750W
73:9QM4****:ST3500320AS:9BX154-303:SD15:08481:2008-05-31:KRATSG:2008-06-27:2009-01-15:N/A:sunne2k:Spain:(2100GB report in linux):linux kernel 2.6.24-21
74:9QM6****:STM3500320AS:9BX154-303:SD15:09083:2008-08-25:KRATSG:2008-11-12:2009-01-16:OEM:Schoolisoutfan:Germany:(no detect in bios):Vista Business 64Bit: Antec 430W
75:5QM1****:ST3500320AS:9BX154-303:SD15:08386:2008-03-27:WUXISG:2008-07-15:N/A:Roonster:Germany:STILL WORKS FINE
76:5QJ0****:ST31000340AS:98X158-335:SD15:09036:2008-07-24:WUXISG:2008-11-04:N/A:Roonster:Germany:STILL WORKS FINE
77:9QM2****:ST35000320AS:9BX154-303:SD15:08381:2008-03-22:KRATSG:2008-04-30:N/A:OEM:TerTop:MY:fine:WinXP_x86_x64:NMB 460W
78:9QM8****:ST3500320AS:9BX154-303:SD15:09165:2008-10-22:KRATSG:2008-12-15:2009-01-03:OEM:mahk:Germany:BIOS hung:XPPRO32/Linux2.6.xx:HEC300W
79:9QJ1P***:ST31000340AS:9BX158-303:SD15:09075:2008-08-20:KRATSG:N/A:2009-01-15:OEM:Coltrane69:U.S.:No Detect In Bios
80:5QM2****:ST3500320AS:9BX154-303:SD15:09105:2008-09-10:WUXISG:2008-10-21:NOT YET:OEM:bigjimmcbob:CANADA:file:DSN-323(Linux based):N/A
81:90j1****:ST31000340AS:9BX158:SD15:08527:2008-07-04:KRATSG:2008-08-01:2009-01-15:OEM:chrisbkr:USA:(no detect in bios):WinVista:650W
82:9QM6****:ST3500320AS:9BX154-303:SD15:09075:2008-08-20:KRATSG:2008-09-01:2009-01-18:OEM:bertm:Netherlands:(no detect in bios):N/A:N/A
83:9QM6****:ST3500320AS:9BX134-505:SD25:09085:2008-08-27:KRATSG:2008-10-01:2009-01-03:RETAIL:wirefall:Germany:0GB:Win XP Home:500W
84:5QJ1****:ST31000340AS:9BX158-303:SD15:09127:2008-09-26:WUXISG:2008-10-15:2008-01-18:OEM:donnerzusel:Germany:Failed after firmware upgrade recommended by Seagate to AD14:Linux 2.6.28:Enermax PRO82+ 425W
85:5QM3****:ST3500320AS:9BX154-303:SD15:09142:2008-10-05:N/A:WUXISG:2009-01-06:N/A:OEM:ciobi:Romania:fine:Linux:N/A
86:5QJ0****:ST31000340AS:9BX158-303:SD15:09056:2008-08-07:WUXISG:2008-11-01:2009-01-18:N/A:aalexandre:Russia:(no detect in bios):winXP:N/A
87:9QM3****:STM3500320AS:9GT154-325:MX15:08401:2008-04-05:KRATSG:2008-10-30:2009-01-18:RETAIL:sellig:FRANCE:(not detected in bios):XP pro:N/A
88:9QK0****:ST3750330AS:9BX156-303:SD15:08495:2008-06-11:KRATSG:2008-07-01:2008-08-14:OEM:Gradius2:Chile:POST error (it recognize, but returns error on POST):Vista Ultimate SP1 x64:N/A
89:9QK0****:ST3750330AS:9BX156-303:SD15:09023:2008-07-14:KRATSG:2008-08-10:2008-08-14:OEM:Gradius2:Chile:BSY error:Vista Ultimate SP1 x64:N/A
90:9QK0****:ST3750330AS:9BX156-303:SD15:09023:2008-07-14:KRATSG:2008-08-10:2008-08-14:OEM:Gradius2:Chile:BSY error:Vista Ultimate SP1 x64:N/A
91:5QM3****:ST3500320AS:98X154-303:SD15:09233:2008-12-08:WUXISG:2009-01-07:N/A:RETAIL:rook-ie:MALAYSIA:fine:winXP:N/A
92:9QM*****:ST3500320AS:9BX154-335:SD15:09085:2008-08-27:KRATSG:2008-12-15:N/A:RETAIL:Anon-E-moose:USA:fine:Linux/XP/win7x64:Antec500W
93:9QK0****:ST3750330AS:9BX156-303:SD15:08054:2007-08-07:KRATSG:2008-12-15:2009-01-10:OEM:Tristano:ITALY:(not detected in bios):N/A:N/A
95:9QM2****:ST3500320AS:9BX154-303:SD15:08385:2008-03-26:KRATSG:2008-05-12:2008-12-01:RETAIL:qdr:Kazakhstan:F/K:WinXPx86:N/A
96:9QM8****:ST3500320AS:9BX154-303:SD15:09155:2009-10-15:KRATSG:2008-12-05:2009-01-10:RETAIL:qdr:Kazakhstan:F/K:WinXPx86:N/A
97:5QJ0****:ST31000340AS:9BX158-303:SD15:09115:2008-09-17:WUXISG:2008-11-20:2009-01-19:OEM:JRD393:USA:(no detect in bios):XP Pro:Corsair 650W
98:9QM6****:ST3500320AS:9BX154-303:SD15:09105:2008-09-10:KRATSG:2008-11-07:N/A:OEM:winicjusz:Poland:fine:Vista x64 Business:BeQuiet 450W
99:9QM6****:ST3500320AS:9BX154-303:SD15:09105:2008-09-10:KRATSG:2008-11-07:N/A:OEM:winicjusz:Poland:fine:Vista x64 Business:BeQuiet 450W
100:9QM3****:ST3500320AS:9BX154-303:SD15:08406:2008-04-10:KRATSG:2008-11-20:2009-01-22:RETAIL:ili:Israel:(no detect in bios):Vista64:620W
101:9QM69WY2:ST3500320AS:9BX154-303:SD15:09085:2008-08-27:KRATSG:2008-09-10:2009-01-18:OEM:geff44:France:(no bios detect):Ubuntu 8.10:480W Advance
102:9QM1****:ST3500320AS:9BX154-303:SD15:08357:2008-03-07:KRATSG:2008-N/A-N/A:2009-01-03:RETAIL:709394hk:HongKong:BSY:XP Pro:N/A
103:9QJ2****:ST31000340AS:9BX158-303:SD15:09097:2008-09-05:KRATSG:2008-12-05:2009-01-13:RETAIL:kornut:Russia:(no detect in bios):XP Pro:350W
104:9QM7****:ST3500320AS:9BX154-303:SD15:09136:2008-10-02:KRATSG:2008-11-27:N/A:OEM:an3k:Germany:still running fine:WinXP Pro:Enermax EMD525AWT
105:9QJ2****:ST31000340AS:9BX158-303:SD15:09101:2008-09-06:KRATSG:2008-12-3:2009-1-20:OEM:PANG:Sinapore:no detect in bios:xppro_sp2:N/A
106:6Qm0****:ST3500320AS:9BX154-303:SD15:09215:2008-11-26:SUZHSG:2009-01-26:2009-1-26:OEM:verdilith:china:(no detect in bios):xpHome_sp2:N/A
107:9QM2****:ST3500320AS:9BX154-303:SD15:08394:2008-04-01:KRATSG:2008-05-20:2008-08-05:N/A:cooper2009:Germany:(no detect in bios):XPHome:230W
108:9QJ0****:ST31000340AS:9BX158-303:SD15:08354:2008-03-04:KRATSG:N/A:2009-01-16:OEM:ione:Finland:(no detect in bios):N/A
109:3QK0****:ST3750330AS:9BX156-303:SD15:08222:2007-12-02:AMKSPR:2008-01-18:N/A:OEM:NearlyGod:Netherlands:fine:XPPro+VistaBiz:Antec500W
110:5QM0****:ST3500320AS:9BX154-303:SD15:08241:2007-12-15:WUXISG:2008-01-27:N/A:OEM:NearlyGod:Netherlands:fine:Server2003:Chieftec450W
111:9QM3****:ST3500320AS:9BX154-303:SD15:08411:2008-04-12:KRATSG:2008-07-15:2009-01-16:OEM:Verdilith:UK:(no detect in bios):Windows XP SP2:N/A
112:9QM6****:ST3500320AS:9BX154-303:SD15:09086:2008-08-28:KRAT8G:2008-09-25:2008-12-23:OEM:Dadou:France:(no detect in bios):winXP X86:Corsair 550W
113:9QM5****:ST3500320AS:9BX154-335:SD15:09055:2008-08-06:KRATSG:2008-10-01:2008-01-28:RETAIL/MICROCENTER:fcastro:USA:(no bios detect):XP:ThermalTakePurepower500W
114:9QJ1W***:ST31000340AS:9BX158-303:SD15:09076:2008-08-21:KRATSG:2008-08-28:2008-12-17:OEM:[pi]:(no detect in bios):Vista Ultimate x86:Corsair HX620
115:9QM1****:ST3500320AS:9BX154-303:SD15:08366:2008-05-05:KRATSG:2008-06-06:2009-01-10:N/A:secagate lorito:Spain:(no detect in bios):N/A:N/A
116:9QK0****:ST3750630AS:9BX146-621:HP24:08476:2008-05-29:TK:10-15-2008:01-29-2008:OEM:RainCaster:USA:(no detect in bios):Doesnt_matter:HP
117:9QM6****":ST3500320AS:98X154-335:SD15:09085:2008-08-27:KRATSG:2008-12-27:2009-01-22:RETAIL:jake36:USA:(no detect in bios):Vista:N/A
118:9TE0****:ST31000333AS:9FZ136-100:LC15:09146:2008-10-09:TK:2008-11-21:2008-12-19:OEM:MyData:Netherlands:no detect in bios:N/A:N/A
119:9QM1****:ST3500320AS:9BX154-303:SD15:08373:2008-03-17:KRATSG:2008-05-05:2009-01-22:N/A:Datenshi:Sweden:(no detect bios):XP pro x86:N/A

Edited by DerSnoezie, 03 February 2009 - 12:38 PM.



How to remove advertisement from MSFN

#2
Lippy

Lippy
  • Member
  • 9 posts
  • Joined 12-January 09
Here's another one, which I'm keeping cosy in my drawer for now.

48:9QJ2****:ST31000340AS:9BX158-303:SD15:09086 (28-08-08):KRATSG:(22-09-08):(26-12-08):OEM:Lippy:UK:BUSY (locks up at BIOS)

EDIT: Found purchase date.

Edited by Lippy, 12 January 2009 - 02:25 PM.


#3
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09
Countries currently reported to have been affected by the seagate 7200.11 "plague" marked in red (including a few countries of forum members which did report the problem, but haven't contributed their data to the fail & fine dataset yet):

Posted Image

Credits for providing the basic vector map go out to Lee Brimelow: http://theflashblog.com/?p=144

Edited by DerSnoezie, 31 January 2009 - 03:35 PM.


#4
fuzzby

fuzzby

    Newbie

  • Member
  • 10 posts
  • Joined 13-January 09
Excellent idea moving the forums off of Seagate and I was so happy to see the Inquirer article. Anyways would like to report that I had the exact same issue with my ST31000AS with SD15 from Thailand. Would not detect on boot. Using a repair kit I purchased online (not cheap!) I was able to connect to the drive through a special serial connection that I did not recognize in my 15+ years of PC experience. With the included software I was able to clear the BSY (busy) lock on the HDD and also the 0GB detect issue. Full functionality was restored and the data intact. The kit was expensive so if the data is not valuable then I recommend RMAing it in.
I've been hit with many requests from ppl online to unbrick their drives so if you want to mail it to me that's an option I'm providing. I'm located in Toronto, Canada. I'm in no way a professional recoverer nor am I looking to profiteer heavily from this. I lost 800GB from this Seagate defect and was pretty p***ed :realmad: I'd imagine I'm not alone.

Rule#1 - Always back up!
Rule#2 - Always back up! (This is a backup to Rule#1)

#5
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09
Thanks! Unfortunately seagate moderators do a darn good job preventing people from finding this thread. They blocked out all possibilties on their forum to link to this thread and alter or even delete our posts! We do have some small scale promotion going on at several forums, but for as yet we haven't got the resources to reach the bulk of neglected seagate customers.

Excellent idea moving the forums off of Seagate and I was so happy to see the Inquirer article.


Edited by DerSnoezie, 13 January 2009 - 12:02 PM.


#6
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09
Visualization of the seagate 7200.11 fail & fine dataset:

Posted Image

Posted Image

Edited by DerSnoezie, 27 January 2009 - 08:51 AM.


#7
Holux

Holux
  • Member
  • 1 posts
  • Joined 13-January 09
Here is another one:

Problem: 0 GB in BIOS & not detected. 2 months of life.
Country: Spain
S/N: 9QM613FN
ST3500320AS Barracuda 7200.11 500Gbytes
P/N: 9BX154-303
Firmware: SD15
Date Code: 09083
Site Code: KRATSG
Product of Thailand

#8
StephenB

StephenB
  • Member
  • 3 posts
  • Joined 13-January 09
Failed yesterday:

Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User: fail reason/fine
====================================================================================================
01:9QM6N***:STM3500320AS:9GT154-325:MX15:09101:KRATSG:120908:120109:OEM:StephenB:UK:NO DETECT IN BIOS

I have another working drive (date code 09265) with Firmware MX1A. Is this likely to go the same way?

#9
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

Failed yesterday:

Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User: fail reason/fine
====================================================================================================
01:9QM6N***:STM3500320AS:9GT154-325:MX15:09101:KRATSG:120908:120109:OEM:StephenB:UK:NO DETECT IN BIOS

I have another working drive (date code 09265) with Firmware MX1A. Is this likely to go the same way?


This case is a bit different, since these are both maxtor drives (according to the model entry), with one displaying exactly the same problem as we are reporting in seagate 7200.11 drives. But when comparing the firmware versions with that of seagate models the only difference apears to be a 2 character prefix, with your MX15 corresponding to the SD15 failures and MX1A being a later firmware update, which was officially launched by seagate to fix yet another problem (so called "freezing"). Up till now I haven't come across any cases of seagate drives with SD1A firmware failing due to the "no detect in bios/0GB disc size problem" so my best guess is that your second drive will be spared from those particular issues.

BTW According to the date code calulator your second drive was manufactured quite recently; on 31-12-2008, to be precise and the defective drive on 06-09-08.

Edited by DerSnoezie, 13 January 2009 - 04:42 PM.


#10
prim

prim
  • Member
  • 8 posts
  • Joined 08-January 09
Mine failed too, I'm not sure if failed at the end of November or begining of December, so let's say 1 Dec.

49:9QM5KJGA:ST3500320AS:9BX154-303:SD15:09062:KRATSG:04-09-08:01-12-08:OEM:prim:Spain:(no detect in bios)

#11
Karlston

Karlston

    Newbie

  • Member
  • 13 posts
  • Joined 13-January 09
As fate would have it, I lost this drive a few minutes after reading the story on The Inquirer site...

50:5QJ0JRE3:ST31000340AS:9BX158-303:SD15:08516:WUXISG:13-11-08:14-01-09:RETAIL:Karlston:Australia:(no detect in BIOS)

(dates above are dd-mm-yy)

#12
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

As fate would have it, I lost this drive a few minutes after reading the story on The Inquirer site...

50:5QJ0JRE3:ST31000340AS:9BX158-303:SD15:08516:WUXISG:13-11-08:14-01-09:RETAIL:Karlston:Australia:(no detect in BIOS)

(dates above are dd-mm-yy)


I am sorry for your loss.. Thanks for sharing your data though :)

BTW It's time to get some sleep. See you all in about 9 hours or so.

Edited by DerSnoezie, 13 January 2009 - 07:06 PM.


#13
hallwal

hallwal
  • Member
  • 2 posts
  • Joined 14-January 09
You can add mine to the list. :( I still haven't bothered reporting mine to Seagate because I'm sure they will take my drive before giving me a new one, and I really really want my data back!! Arghhh...

51:5QJ0****:ST31000340AS:9BX158-302:SD04:08185:WUXISG:(06-04-08):(21-06-08):RETAIL:hallwal:USA (0GB reported)

Edited by hallwal, 19 February 2009 - 08:39 AM.


#14
s1lencer

s1lencer
  • Member
  • 1 posts
  • Joined 13-January 09
9QM8BLTQ:ST3500320AS:9BX154-303:SD15:09167:KRATSG:DEC2008:(11-01-09):OEM:s1lencer:Malaysia:Fail(Freezes Bios)

2 weeks and it died...

#15
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09
For now you hold the unlucky record of having the oldest drive to brick out in the dataset.. Have you really hold on to the failed drive since June last year?!? wow..

You can add mine to the list. :( I still haven't bothered reporting mine to Seagate because I'm sure they will take my drive before giving me a new one, and I really really want my data back!! Arghhh...

51:5QJ03R2M:ST31000340AS:9BX158-302:SD04:08185:WUXISG:(06-04-08):(21-06-08):RETAIL:hallwal:USA (0GB reported)


Edited by DerSnoezie, 14 January 2009 - 05:52 PM.


#16
valdas

valdas
  • Member
  • 5 posts
  • Joined 04-January 09
Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User: fail reason/fine

55:9QK0WPSV:ST3750330AS:9BX156-303:SD15:09024:KRATSG:2008-11-28:2008-12-30:OEM:valdas:Lithuania:(no detect in BIOS)


Also has has text below specs STX-ST310000340AS (B) whatever it means. Maybe was ST310000340AS and was rebranded as ST3750330AS because of some problems when doing QA. Just my speculation...

Edited by valdas, 14 January 2009 - 07:20 AM.


#17
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

55:9QK0WPSV:ST3750330AS:9BX156-303:SD15:09024:KRATSG:2008-11-28:2008-12-30:OEM:valdas:Lithuania:(no detect in BIOS)


Lithuania! We will add your country to the map. Thanks for your info!

Edit: Lithuania has been marked on the "plague" map.

Edited by DerSnoezie, 14 January 2009 - 10:27 AM.


#18
jkc120

jkc120

    Newbie

  • Member
  • 12 posts
  • Joined 14-January 09
My parents bought me 2 of these drives for Christmas (purchased 12/13/2008, not sure of their manufacturing date). I'm in the US (Delaware).

Both are ok so far, but I also haven't cold booted the machine more than a handful of times.

Serial # prefixes are both "5QJ0", both are from China (WUXISG).

I'm really worried about this...the drives were purchased > 30 days ago, so I can't return them.

#19
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

My parents bought me 2 of these drives for Christmas (purchased 12/13/2008, not sure of their manufacturing date). I'm in the US (Delaware).

Both are ok so far, but I also haven't cold booted the machine more than a handful of times.

Serial # prefixes are both "5QJ0", both are from China (WUXISG).

I'm really worried about this...the drives were purchased > 30 days ago, so I can't return them.



Yeah, since this issue was picked up by the mainstream media yesterday we've been waiting for an official statement from seagate..

BTW If you add some more characteristics, we could list your drives in the dataset. Most of the data is printed on the sticker on top of your drive. The manufacturing date is based on a 5 digit code, starting with a 0. We use a simple tool to translate this code into the manufacturing date. The link to this file is also present in the main thread on msfn, but I can't remember exactly which page..

Edit: You can find the link to the date code calculator on page 9, post #176:

http://www.megaupload.com/?d=HS5ZEL4O

Edited by DerSnoezie, 15 January 2009 - 12:46 PM.


#20
jkc120

jkc120

    Newbie

  • Member
  • 12 posts
  • Joined 14-January 09
Thanks, will do. The drives are back in the case and I can't see the tops of them while they're in the chassis.

However...I took a couple of photos of the drives, so I'll get that info and add it to my post above.

Another question I have about the dataset. Would it be useful to see the OS the drive is running in (Windows (with specific version info), Linux (with specific kernel info), FreeBSD (with specific release info))?

The reason I ask is because I know, for example, FreeBSD doesn't support NCQ and perhaps that (or some other ATA command that one or the other OS doesn't support or has a buggy driver) is contributing to the wedging of the drive?

#21
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

Another question I have about the dataset. Would it be useful to see the OS the drive is running in (Windows (with specific version info), Linux (with specific kernel info), FreeBSD (with specific release info))?

The reason I ask is because I know, for example, FreeBSD doesn't support NCQ and perhaps that (or some other ATA command that one or the other OS doesn't support or has a buggy driver) is contributing to the wedging of the drive?


Yes, unfortunately the OS is missing from the list. We have some reports from mac users, but none from Linux or FreeBSD, so it would make a nice addition to the dataset. Thanks for the tip!

BTW You may have noticed that we have very few failure entries of the "5QJ0****" serial number. The same can be said for drives manufactured in China. So perhaps yours have a higher chance of survival. But then again our dataset only covers a small amount of the thousands of failed drives reported worldwide, so I wouldn't count on it. Especially when they have the infamous SD15 firmware.

Edited by DerSnoezie, 14 January 2009 - 06:45 PM.


#22
jkc120

jkc120

    Newbie

  • Member
  • 12 posts
  • Joined 14-January 09

BTW If you add some more characteristics, we could list your drives in the dataset. Most of the data is printed on the sticker on top of your drive. The manufacturing date is based on a 5 digit code, starting with a 0. We use a simple tool to translate this code into the manufacturing date. The link to this file is also present in the main thread on msfn, but I can't remember exactly which page..

Edit: You can find the link to the date code calculator on page 9, post #176.



Here's the info to add, I have 2 of the drives. They're identical in all the info except for the serial # of course:

5QJ0*:ST31000340AS:9BX158-303:SD15:09133(29-09-08):WUXISG:N/A:OEM:jkc120:USA:Ok_so_far
5QJ0*:ST31000340AS:9BX158-303:SD15:09133(29-09-08):WUXISG:N/A:OEM:jkc120:USA:Ok_so_far

Note: it was puchased on the 13th of December, 2008, but has only been in the system for 10-14 days or so, I forget exactly when I first fired it up.

OS on this is FreeBSD 7.1-RELEASE/amd64. :)

Edited by jkc120, 14 January 2009 - 06:40 PM.


#23
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

Here's the info to add, I have 2 of the drives. They're identical in all the info except for the serial # of course:

5QJ0*:ST31000340AS:9BX158-303:SD15:09133(29-09-08):WUXISG:N/A:OEM:jkc120:USA:Ok_so_far
5QJ0*:ST31000340AS:9BX158-303:SD15:09133(29-09-08):WUXISG:N/A:OEM:jkc120:USA:Ok_so_far

Note: it was puchased on the 13th of December, 2008, but has only been in the system for 10-14 days or so, I forget exactly when I first fired it up.

OS on this is FreeBSD 7.1-RELEASE/amd64. :)


Thanks! I'll upload your entries right away :) and set the purchase date of the drives to 01-01-09, I think that will cover it. Since you are running a special OS it might be nice to hear further feedback from you on the drives; if they do fail - which I certainly hope not - let us know.

#24
jkc120

jkc120

    Newbie

  • Member
  • 12 posts
  • Joined 14-January 09

BTW You may have noticed that we have very few failure entries of the "5QJ0****" serial number. The same can be said for drives manufactured in China. So perhaps yours have a higher chance of survival. But then again our dataset only covers a small amount of the thousands of failed drives reported worldwide, so I wouldn't count on it. Especially when they have the infamous SD15 firmware.


Yes, I'm hoping the 5QJ0* entries are just the typical failures and unrelated to the problems being reported. After all, drives can and DO fail. Maybe amid the slew of problems, the China/5QJ0* failure reports are just the more typical failures. Well, a guy can hope right? :unsure:

I will certainly report back if (and I really hope not) either drive fails for some reason. I'm going to keep the number of times the drive is fully powered down/up to a minimum, until I hear of a potential resolution or a recall or what.

#25
DerSnoezie

DerSnoezie

    Member

  • Member
  • PipPip
  • 151 posts
  • Joined 08-January 09

Yes, I'm hoping the 5QJ0* entries are just the typical failures and unrelated to the problems being reported. After all, drives can and DO fail. Maybe amid the slew of problems, the China/5QJ0* failure reports are just the more typical failures. Well, a guy can hope right? :unsure:

I will certainly report back if (and I really hope not) either drive fails for some reason. I'm going to keep the number of times the drive is fully powered down/up to a minimum, until I hear of a potential resolution or a recall or what.


We'll just have to wait & see. BTW it's time for some sleep now over here, I'll be back in about 10 hours..




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users



How to remove advertisement from MSFN