[DerSnoezie]

aspro, on Jan 17 2009, 01:14 AM, said:

Here is my data

9TE0****:ST31000333AS:9FZ136-100:LC15:09175:TK:Dez2008:08-01-09:RETAIL:aspro:Germany:no detect in bios:XP x64:Seasonic 380W

Well, this is a new 3 platter TB drive with a different firmware than SD15 so I dunno if it's related to the firmware problem of the 4 platter version but I hope so. Also my drive isn't acoustically working normal but is continuously attempting to spin up and then spinning down again.

Seagate has officially acknowledged the issue. Check out the links in the post above yours. And I'm pretty exhausted right now

This post has been edited by DerSnoezie: 16 January 2009 - 06:23 PM

[DataRecPro]

DerSnoezie, on Jan 16 2009, 03:38 PM, said:

DataRecPro, on Jan 16 2009, 10:20 PM, said:

Sorry if I misunderstood...do you mean a main thread here or at the place I linked? Could you direct me to this fix/thread?

DRP

The main thread I linked above in post #72. Please scroll up.

Ahh, I see. Thanks! So does anyone know what they did?

DRP

This post has been edited by DataRecPro: 16 January 2009 - 11:36 PM

[cluberti]

I believe Seagate owes everyone involved a big apology, free data recovery, and new (hopefully better... ) drives.

Good work everyone.

[DerSnoezie]

cluberti, on Jan 17 2009, 01:27 AM, said:

I believe Seagate owes everyone involved a big apology, free data recovery, and new (hopefully better... ) drives.

Good work everyone.

And we greatly appreciate that the MSFN forum provided a solid & objective platform for our efforts!

[puntoMX]

DerSnoezie, on Jan 16 2009, 07:11 PM, said:

And we greatly appreciate that the MSFN forum provided a solid & objective platform for our efforts!

That´s what we try to do here.

Goed werk, we zijn er blij mee!

[TerTop]

Here is my 500GB drive data working fine now for 9 months already.
I have jumpered the drive to SATA 1.5GB since day one. Not sure if it make any difference anyway.

9QM2****:ST35000320AS:9BX154-303:SD15:08381:KRATSG:2008-04-30:N/A:OEM:TerTop:MY:fine:WinXP_x86_x64:NMB 460W

Edit: But the cache size is zero?

Attached File(s)

•  untitled.jpg (108.91K)
  Number of downloads: 13

This post has been edited by TerTop: 16 January 2009 - 09:07 PM

[Karlston]

DerSnoezie, on Jan 17 2009, 10:22 AM, said:

Seagate has officially acknowledged the issue. Check out the links in the post above yours. And I'm pretty exhausted right now

Just wanted to say thanks for your efforts during this trying time. And also to MSFN forums.

Also, plugged my "not seen in BIOS" bricked 1 TB (entry 50 in the DB) into my Ubuntu Linux box and the drive was visible, but reported as 0 GB. I could put it in my older Windows box and if it's visible but 0GB then try what this earlier poster tried...

http://www.msfn.org/board/index.php?showto...st&p=827567

The question is, should I or shouldn't I try? The data is not vital, it'd just be nice to get the drive working again enough to drag a little data off it and do the firmware upgrade myself instead of the hassle of sending it off to Seagate. Any takers?

[mahk]

took a picture before sending it in after it was hanging in the bios (on two machines with different cables, PSU, SATA controllers etc.). lucky enough it was a plain vanilla installed xp on it, no data was yet moved to it.

Number:9QM88KAF:ST3500320AS:9BX154-303:SD15:09165:KRATSG:2008/12/15:2009/01/03:OEM:mahk:Germany:BIOS hung:XPPRO32/Linux2.6.xx:HEC300W

Attached File(s)

•  ST3500320AS.jpg (76.02K)
  Number of downloads: 18

This post has been edited by mahk: 17 January 2009 - 03:11 AM

[schoolisoutfan]

DerSnoezie, on Jan 16 2009, 03:38 PM, said:

schoolisoutfan, on Jan 16 2009, 09:34 PM, said:

9QM62***:STM3500320AS:9BX154-303:SD15:09083:KRATSG:121108:160109:OEM:Schoolisoutfan:Germany:NO DETECT IN BIOS

Hi, thanks! Could you also add some info on your OS and power supply please?

Hi,

I am using Vista Business 64Bit an have a 430W Antec Earthwatts power supply.

[coltrane69]

Count me in, my STS31000340AS failed yesterday after only 5 months of light use.

9QJ1P***:ST31000340AS:9BX158-303:SD15:09075:KRATSG:08/20/08:01/15/09:OEM:Coltrane69:U.S.:No Detect In Bios

This post has been edited by coltrane69: 17 January 2009 - 04:00 AM

[bigjimmcbob]

Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of User:fail reason/fine:OS:PSU
5QM2****:ST3500320AS:9BX154-303:SD15:09105:WUXISG:10/21/08:NOT YET:OEM:bigjimmcbob:CANADA:file:DSN-323(Linux based):N/A

Been using this drive in my DSN-323 acts as a nightly backup server. No issues yet.
Not sure how the Dlink DSN-323 is designed (Bios etc) or how it detects drives and what SATA commands it uses/supports.

[chrisbkr]

Mine failed on jan 15th. I went online to get review to buy another and found the news. Bought Western Digital inseated of another on of these. Never again will I buy another Seagate when they fail to be forthcoming about these issues.

90j13858:ST31000340AS:9BX158:SD15:08527:KRATSG:Aug08:1/15/09:OEM:chrisbkr:USA:FAILURE-BIOS NO-Detect:WinVista:650W pwr suply

[cdturri]

For those wanting to scream at someone I suggest you go to the Contact Us page in Seagate.com (http://www.seagate.c...out/contact_us/) and click on Media. There are a couple of people you could email:

COMMUNITY RELATIONS
elena.sexton@seagate.com
ian.o'leary@seagate.com
lotus.tan@seagate.com

Consumer Solutions Division / Seagate and Maxtor Retail / Storage Solutions
nathan.papadopulos@seagate.com
siobhan.m.lyons@seagate.com

Desktop and Notebook Storage
michael.hall@seagate.com

I already emailed all them. Make them hear your pain, let's make their mail inboxes get full with our complaints.

If they don't want to hear about it so be it. One email per drive dead should be a reasonable punishment!!!

[bertm]

failed this morning in nederland
bought in september
9qm6146s st3500320as 9bx154-303 sd15 09075 kratsg 5000c5000daf4d71
booting takes 10 times longer. no detect in bios.
luckaly only torrents and games where lost.
2 other barracudas are still good. 1 of them is now 1 year old.
the hd that failed was making noise alot with parking or something during windows sessions.

This post has been edited by bertm: 18 January 2009 - 06:29 AM

[Jackie78]

chrisbkr, on Jan 18 2009, 12:00 AM, said:

Mine failed on jan 15th. I went online to get review to buy another and found the news. Bought Western Digital inseated of another on of these. Never again will I buy another Seagate when they fail to be forthcoming about these issues.

90j13858:ST31000340AS:9BX158:SD15:08527:KRATSG:Aug08:1/15/09:OEM:chrisbkr:USA:FAILURE-BIOS NO-Detect:WinVista:650W pwr suply

Strange thing is: when I enter your serial number in seagates online checker, they say your drivbe is not affected. Wo how much can you trust that tool?
http://support.seaga...om/sncheck.html

Let's share our results here: http://www.msfn.org/...howtopic=128793

[wirefall]

Thanks a lot for this thread, my 500GB failed a few days ago, showing OGB. Bought last Oktober. Here we go:

Number:Serial N°:Model:Part N°:Firmware:DateCode:SiteCode:PurchaseDate:FailedDate:OEM/RETAIL:UserName:Country of the User: fail reason/fine

XX:9QM68R5A:ST3500320AS:9BX134-505:SD25:09085:KRATSG:2008-10-01:2008-01-03:RETAIL:wirefall:Germany:showing 0GB: Win XP Home:500 W pwr supply

I`ve used it via RAID 1, so no data loss *knock on wood*

Now I'm thinking about sending it to seagate for a cahange, but what about my data? What about the possibility of misusing by the people at seagate ...

[donnerzusel]

Hi folks,

I just registered because I have one of those Seagate Drives.

xx:5QJ1****:ST31000340AS:9BX158-303:AD14:09127:WUXISG:2008-10-15:2008-01-18:OEM:donnerzusel:Germany:Failed AFTER Firmware Upgrade recommended by Seagate:Linux 2.6.28:Enermax PRO82+ 425W

Strange thing:
I had a chat yesterday with one of those Seagate guys. At that time, I had Firmware SD15 running and the drive was running fine.
He affirmed that my drive (see above) is affected by the firmware issue. He gave me a link to a firmware update and a certificate number to access that page. I asked him if it is safe to "upgrade" the firmware from version SD15 to AD14 because I've read some posts of bricked hard drives. He assured me that the upgrade is necessary and safe to do.

So I created the bootable CD, powered down the computer, disconnected everything except a CD drive and the Seagate HDD and started the upgrade. Everything went fine, I powered down the computer as requested, waited for some minutes and powered it on again.

Well, and with the new firmware the BIOS reports an error while trying to access the Seagate HDD. I tried this hard disk in several other machines, it doesn't work anymore.

Edit:
Strangely, the BIOS still reports the full capacity of the drive, but refuses to boot if the drive is connected and reports "HARD DISK ERROR". If I put the power cable into the drive just after the POST, the computer boots happily from my first HDD (the faulty Seagate drive is just for data). The Seagate drive is unaccessible from Windows (it contains only ext3-partitions, but it is not shown in the Hardware tabs or the Drive Management) as well as from Linux. Linux is able to see and identify the drive and capacity, it reports the new firmware version (AD14) but hangs if I try to access the sectors on it.

If I boot from the Seagate Firmware-Upgrade CD (using the same trick as above: replug the power after POST), the Flash-Tool recognizes the Hard Drive and is able to flash the AD14 firmware again. But it is unaccessible as well.
So maybe I'm doing something wrong here or Seagate has some issues with the "new" firmware.

Oh, and the online tool at the Seagate page where you put in the Serial number, tells me that my drive is affected.
Of course, I backed up the data before flashing, so I don't suffer from data loss.
/Edit

Long story short:
-ST31000340AS with Firmware SD15 (working)
-Seagate support acknowledged that the drive is affected
-Seagate support suggests firmware upgrade to AD14
-upgraded firmware, drive bricked.

Thank you, Seagate.

This post has been edited by donnerzusel: 18 January 2009 - 07:33 AM

[ciobi]

Karyudo, on Jan 15 2009, 12:29 AM, said:

Made my own blist from the data: http://app.blist.com/#/blist/karyudo/Seaga...-Drive-Failures

Perhaps it would be interesting to add a column with the "affected" status as reported by http://support.seaga...om/sncheck.html , to get an idea about how good this S/N check actually is. It seems that there are drives that are found by it as "not affected" but have failed with the symptoms that started this discussion. (See also: http://www.msfn.org/board/index.php?showto...st&p=828094 )

My drive:
5QM3****:ST3500320AS:9BX154-303:SD15:09142:?:WUXISG:2009-01-06:N/A:OEM:ciobi:Romania:fine:Linux

(My drive was working OK, but I took it out to avoid bricking it; I'll put it back when this mess gets sorted out.)

[aalexandre]

failed today
bought in november (Russia, Moscow)

1:5QJ0QHZ7:ST31000340AS:9BX158-303:SD15:09056:2008-10-09:WUXISG:2008-11-01:2009-01-18:N/A:aalexandre:Russia:(no detect in bios):winXP

Noted that before death I fulled totally full disk - luckaly these were only torrents

2 other barracudas are still good (s/n start 9QJ0 ...) and online serial checker says they are not affected. They were bought in june-july

[sellig]

Failed today ; from france

9QM3****:STM3500320AS:9GT154-325:MX15:08401:KRATSG:2008-10-30:2009-01-18:RETAIL:sellig:FRANCE:(not detected in bios):XP pro

Loose family videos