DerSnoezie

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, who are reading this topic: After multiple complaints that the 7200.11 fail & fine dataset was clogging up this main thread, I've decided to open a new topic on msfn dedicated to collecting the life history data of your seagate barracuda 7200.11 SD15 (and other firmware versions) drives. Please register to the msfn forum and add your data to the list at the following topic (also located at msfn hardware hangout): http://www.msfn.org/board/index.php?showtopic=128514

Initial credits for the idea of this list go out to poolcarpet: http://www.msfn.org/board/index.php?s=&amp...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/board/index.php?showto...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

I do not know. Feel free to do so since most of the tech stuff is out of my league.

You are referring to this guy: http://www.tomshardware.co.uk/forum/248044...tect-bios-fixed He has spend big bucks on a software hardware complex, which was already known to fix the problem.

Thanks. Most of the information is there, but I'm not sure about last 5 digits of your firmware code, which are oddly resembling a date code. And from your text description the failure date was 11-01-09. Final question for you: was it a retail or OEM drive? You'll probably find the OEM statement printed on the sticker on top of your drive. And for future posters: please present your data in this format: Number in list:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User ==================================================================================================== ========== example= 40:9QM66SGE:ST3500320AS:9BX154-303:SD15:09082:KRATSG:1Dec2008:11Jan2009:OEM:SeaGAYBarracuTARD:Canada:(no detect in bios)

Okay, at the moment fatlips' research is bogged down, since his crapped out guinea pig drive experiences much more problems than expected, and he is waiting on the delivery of a friends' drive with similar problems to continue his investigation. When you flip through the thread you'll see he has started some kind of a tutorial, including photographs how to hook your drive up to the adapter and the com port. Pichi appears to be the member achieving the most progress on the hardware front, but his post usually lack an introduction and largely require a high tech level of the reader in order to interpret. So with only two members actively posting their findings toward a homemade solution, things are relatively slow on that front. We would greatly appreciate more help from people with a high tech level! For as far as I know swapping the pcb won't work because every pcb has been manufactured in a way that it only recognises the specific harddrive it was assemblied with. If you swap the pcb I think your data will not be destroyed. Shorting out the contacts goes beyond my knowledge and I would advise against it due to the collaterol damage you might induce. Currently the thread needs serious streamlining, but these things take time, many members live in various timezones and communication is generally slow. This thread is maintained on a pure informal basis and sure is getting a bit messy, but I hope that soon we'll succeed in streamlining the attention this thread receiving. So I suggested you to PM fatlip and/or pichi, since from them you have the largest chance to receive a technically sound awnser for your questions. The other purposes of this thread are to draw attention to the problem and collect data. so what's the point of this forum ? I don't want to be here and be insulted for not buying into conspiracy theories...I want to try to find a solution. That mean's I have one 7200.11 that is bsy dead; and I have a few others that are still running with stuff on and one that I can sacrifice to try to restore the dead one. Has anyone tried anything ? pcb swap ? why wouldn't a pcb swap not work ? would I destroy the data on the dead unit if I try a pcb swap ? what about shorting out the sata contacts (unpowered)- similar to clearing a cmos would that work ? is there risk ? that's what I think we need- not another dumping ground for madcap garbage and idiocy

Think of all the data these viewers could contribute to the dataset.. We are going to need some serious streamlining. If in a couple of hours no action is taken, I think I'll simply start a new seperate thread in the hardware hangout on this forum, dedicated to the failure/fine list.

Hmm.. all listed 7200.11 models coincidentally appear to have that 0,34% annualized failure rate.. 0,34% of how many drives in total would that be?

BTW despite some of the strong discussions over here, I definetely would not want to be a moderator at the official seagate forum right now. That place is showing signs of a complete meltdown XD

It is typical mass production tactics to simply pump out patches for every bug - and if the patch works then forget about it - and never find out which underlying factors led to the start of the problem. In this way the industry standard will never improve. I'm sorry if you were offended by one of the other members, but I need to have some sleep eventually and can't stop people from venting some of their more heated opinions. If you are referring to technical questions please try to contact fatlip or pichi, this is complicated, specialistic stuff and there aren't that many hardware engineers hanging around this forum.

At the present rate of data input (<10 entries/day) updating the list is only a minor inconvenience to me. Probably this rate wil increase somewhat when more and more people find out about this thread, but I guess interest in the problem will also fade with time, so I don't expect the maintenance of the dataset to become a major hassle. However, setting up a new location for the data set could prove to be so, depending on what is the preferred option.

Although the list is not helpful in restoring acces to the defective drive, I 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 think this is feasible, just look at how many people are viewing this thread right now: 200+! 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? 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. If you would like to start a new thread or whatever for the list and the rants I am certainly interested, but unfortunately I lack the skills and time to set up a dedicated website. So if something needs to be done about the clogging of this thread, find someone who's able and willing to sort things out. Abuse of the drive information in the list can certainly happen but can be prevented. For instance if people PM their data to me I could provide a stripped down "on screen" version of the list & charts. I agree. What about to open a blog on the issue? While users here work to find a technical solution, we can make a page (or a post) with the dead list and people will be able to add their hd info by comments. Also, a website entirely focused on the issue may receive more media attention. If anyone is interested in this, feel free to PM me.

Well.. it's time for some sleep over here. I hope my remaining barracudas will last through the night..

Thanks harwin! I hope you didn't lose any valuable data..

Those are some serious findings you have there.. Errors in the P list :S

Thanks dragtop

Nice alias you have there The list is certainly growing.. and entries from so many different countries too.. But ofcourse we should all believe seagate and think this are only isolated incidents. Yeah right! We don't think so!

Thanks for your kind words of hope and the data entry ofcourse Regarding your technical questions I think it is best to send a PM to fatlip, which is one of the most knowledgeable forum members in that particular field.

Minor edit; the firmware version of rainshower (#12) should be SD25: Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User:reason of failing / still running fine ==================================================================================================== 01:9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet:Malaysia 02:9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule:United Kingdom 03:9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie:Netherlands (no detect in bios) 04:9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:dskbrk 05:9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:ToKuRo:Chile (no detect in bios) 06:9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:jeroen__online:Netherlands 07:9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:quattro150:Malaysia 08:9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:Nichev 09:9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:PrOdiGy1:UK 10:9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:AVINNC:USA 11:9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage:UK 12:9QM6354J:ST3500820AS:9BX134-505:SD25:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:rainshower:Germany 13:9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:fabio.cillo:Italy 14:9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia 15:9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:Taiketo 16:5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:Styleman 17:9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:roadstarter:Philippines 18:9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:labraticmp3:USA 19:9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:eli2k 20:9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:poim76 21:9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:caba212:Spain 22:9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:GrayGhost:USA 23:9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09: timha 24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:viniciusferrao:Brazil 25:9QM60864:ST3500320AS:9BX154-303:SD15:09076:KRATSG:31 October 2008:Dec 2008:RiderZen:Australia (BSY) 26:9QJ0W41R:ST31000340AS:9BX158-335:SD15:08457 (16/May/2008):KRATSG:Jul2008:20Dec2008:Macprk:USA 27:9QM5V5HQ:ST3500320AS:9BX154-303:SD15:09071:KRATSG:(04/Nov/08):(09/Jan/09):BigSilverHotdog:USA 28:9QM2C4LT:ST3500320AS:9BX154-303:SD15:08382(??):KRATSG:Aug2008:1Jan2009:Keddar:USA 29:5QM1EYCG:ST3500320AS:9BX154-303:SD15:08383:WUXISG:jUL2008:02Jan2009:waly2k1:Argentina (no detect in bios). 30:9QM5RCNT:ST3500320AS:9BX154-303:SD15:09063:KRATSG:JUL2008:25DEC2008:criverock:Italy (no detect in bios). 31:9QM*****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:Oct2008:20Dec2008:sarahcoco:France 32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104 (10/Oct/2008):KRATSG:3Jan2009:artpav:Canada 33:9QM*****:ST3500320AS:9BX154-303:SD15:08371 (15/Mar/2008):KRATSG:7May2008:29Dec2008:KillerB :Korea (no detect in bios) 34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:WUXISG:CHINA:August2008:Dec24th08:Fuzzy_3D:Canada 35:9QJ0GLEX:ST31000340AS:9BX158-303:SD15:08356 (06/March/2008):KRATSG:March2008:Jun2008:TheName:Croatia 36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:KRATSG:JUL2008:05JAN2009:OEM:BARAKASPEED:THIALAND 37:9QM1****:ST3500320AS:9BX154-303:SD15:08364:KRATSG:May2008:12Dec2008:OEM:taa:Russia (no detect in bios) 38:9QM6****:ST3500320AS:9BX154-303:SD15:09096:KRATSG:Sep2008:07Jan2009:OEM:kiave:Poland:(no detect in bios)

Thanks for your input

Oh, okay So we can keep the dataset over here? Maybe that's the best thing to do; at this thread it will probably receive the highest exposure.

Yes, you are right! Things are getting too messy.. People looking for the findings of fatlip, pichi and others will easily get lost. If the topic starter and the main posters agree I'll start a new topic for the seagate barracuda 7200.11 fail or fine dataset.

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, who are reading this topic: Please register to this 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. Most of the data can be collected from the sticker on the top of your harddrive (please keep in mind that you preferably do this when the computer is powered down, be safe). 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! Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User:reason of failing / still running fine ==================================================================================================== ========== 01:9QM7VZBP:ST3500320AS:9BX154-303:SD15:09146 (09/Oct/2008):KRATSG:Oct2008:24Dec2008:poolcarpet:Malaysia 02:9QM6X90B:ST3500320AS:9BX154-303:SD15:09115 (17/Sep/2008):KRATSG:Oct2008:28Dec2008:DaftMule:United Kingdom 03:9QM6W2JE:ST3500320AS: - :SD15: - : - :5Dec2008:19Dec2008:DerSnoezie:Netherlands (no detect in bios) 04:9QM4G4PK:ST3500320AS:9BX154-303:SD15:08503 (16/Jun/2008):KRATSG:Aug2008:Nov2008:dskbrk 05:9QM3RWHJ:ST3500320AS:9BX154-568:SD81:08464 (20/May/2008):KRATSG:Aug2008:23Dec2008:ToKuRo:Chile (no detect in bios) 06:9QM7KSQJ:ST3500320AS:9BX154-501:SD15:09134 (30/Sep/2008):KRATSG:28Oct2008:07Jan2009:jeroen__online:Netherlands 07:9QM2MFS6:ST3500320AS:9BX154-303:SD15:08406 (10/Apr/2008):KRATSG:12Apr2008:23Dec2008:quattro150:Malaysia 08:9QJ0XJ01:ST31000340AS:9BX158-303:SD15:08496 (12/Jun/2008):KRATSG:Aug/Sep2008:8Jan2009:Nichev 09:9QM717SF:ST3500320AS:9BX154-303:SD15:09114 (16/Sep/2008):KRATSG:13Oct2008:14Dec2008:PrOdiGy1:UK 10:9QJ1LESR:ST31000340AS:9BX158-303:SD15:09063 (11/Ago/2008):KRATSG:Nov2008:27Dec2008:AVINNC:USA 11:9QJ1AGEV:ST31000340AS:9BX158-303:SD15:08515 (2/Jul/2008):KRATSG:Aug2008:4Jan2009:Ruddrage:UK 12:9QM6354J:ST3500820AS:9BX134-505:SD25:09084 (26/Ago/2008):KRATSG:July2008:20Dec2008:rainshower:Germany 13:9QM33FL8:STM3500320AS:9GT154-325:MX15:08396 (03/Abr/2008):KRTASG:Sep2008:30Dec2008:fabio.cillo:Italy 14:9QM*****:ST3500320AS:9BX154-303:SD15:08367 (14/Mar/2008):KRATSG:Dec2007:Dec2008:Death_Angel:Malaysia 15:9QK*****:ST3750630AS:9BX146-621:HP24:08511 (21/Jun/2008):TK:Oct2008:7Jan2009:Taiketo 16:5QJ*****:ST1000340AS:9BX158-303:SD15:09121 (20/Sep/2008):WUXISG:October2008:28Dec2008:Styleman 17:9QM8DRHL:ST3500320AS:9BX154-303:SD15: - (13/Oct/2008):KRATSG:06Dec2008:24Dec2008:roadstarter:Philippines 18:9QM6****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:15Oct2008:29Dec2008:labraticmp3:USA 19:9QM6****:ST3500320AS: - : SD15 - : - : Oct2008:2Jan2008:eli2k 20:9QM5****:ST3500320AS:9BX154-303:SD15:09063 (11/Ago/2008):KRATSG:6Nov2008:27Nov2008:poim76 21:9QM2CHR4:ST3500320AS:9BX154-303:SD15:08382 (23/Mar/2008):KRATSG:August-08:Nov-Dec-08:caba212:Spain 22:9QJ15ZBN:ST31000340AS:9BX158-303:SD15:08496 (05/Jun/2008):KRATSG:July2008:26Dec2008:GrayGhost:USA 23:9QM27S5F:ST3500320AS:9BX154-303:SD15:08381:DEC 08:JAN 09: timha 24:9QJ0****:ST31000340AS:9BX158-303:SD15:08495:KRATSG:Oct2008:02Jan2009:viniciusferrao:Brazil 25:9QM60864:ST3500320AS:9BX154-303:SD15:09076:KRATSG:31 October 2008:Dec 2008:RiderZen:Australia (BSY) 26:9QJ0W41R:ST31000340AS:9BX158-335:SD15:08457 (16/May/2008):KRATSG:Jul2008:20Dec2008:Macprk:USA 27:9QM5V5HQ:ST3500320AS:9BX154-303:SD15:09071:KRATSG:(04/Nov/08):(09/Jan/09):BigSilverHotdog:USA 28:9QM2C4LT:ST3500320AS:9BX154-303:SD15:08382(??):KRATSG:Aug2008:1Jan2009:Keddar:USA 29:5QM1EYCG:ST3500320AS:9BX154-303:SD15:08383:WUXISG:jUL2008:02Jan2009:waly2k1:Argentina (no detect in bios). 30:9QM5RCNT:ST3500320AS:9BX154-303:SD15:09063:KRATSG:JUL2008:25DEC2008:criverock:Italy (no detect in bios). 31:9QM*****:ST3500320AS:9BX154-303:SD15:09076 (21Aug2008):KRATSG:Oct2008:20Dec2008:sarahcoco:France 32:9QJ*****:ST31000340AS:9BX158-303:SD15:09104 (10/Oct/2008):KRATSG:3Jan2009:artpav:Canada 33:9QM*****:ST3500320AS:9BX154-303:SD15:08371 (15/Mar/2008):KRATSG:7May2008:29Dec2008:KillerB :Korea (no detect in bios) 34:5QJ0****:ST31000340AS:9BX158-303:SD15:09045:WUXISG:CHINA:August2008:Dec24th08:Fuzzy_3D:Canada 35:9QJ0GLEX:ST31000340AS:9BX158-303:SD15:08356 (06/March/2008):KRATSG:March2008:Jun2008:TheName:Croatia 36:9QM2****:ST3500320AS:9BX154-303:SD15:08381:KRATSG:JUL2008:05JAN2009:OEM:BARAKASPEED:THIALAND

Thanks rainshower:) I've changed your entry to the correct firmware version in my spreadsheet. The title of the chart also required an important addition: "of failed", since the dateset only contains failed drives. Actually we would need to have a testgroup of about 1000-10000 random customers (from various countries) who bought a 7200.11 drive in the time frame from 01-09-07 to present and see what happens to the failure rate of the drives compared to the date of production. There are also plenty reports of 7200.11 drives who work just fine, but then I would want to know when and where they were manufactured and how long they have been running. A member of the Dutch tweakers forum (_I ochen) suggested that although the main thing that most failing drives now have in common is their SD15 firmware, somewhere during 2008 something might have changed in the production line of the 7200.11 drives (switch of factory, other components), which could be related to the introduction of new platters together with the 1,5TB drive. I believe he might be on to something! Link: http://gathering.tweakers.net/forum/list_m...es/1329882/last Only data of failed drives:

http://www.tomshardware.co.uk/forum/248044...tect-bios-fixed Goodnight