verdilith

No problem, just thought the more in your dataset the better

DerSnoezie - I'm not sure that you've added my first fail (above), just the second one I posted - #106 on your list.

Just taken delivery of drive #3, so here's another one for you: 6Qm0****:ST3500320AS:9BX154-303:SD15:09215:SUZHSG:2009-01-26:2009-1-26:OEM:verdilith:china:DOA:xpHome_sp2 this one won't even get as far as letting me check it in BIOS. What a mess. edit: the company I bought my drives from are offering me a full refund. Western Digital, here I come!

Number:9QM3****:ST3500320AS:9BX154-303:SD15:08411:KRATSG:2008/07/15:2009/01/16:OEM:Verdilith:UK:fail :Windows XP SP2: This is actually my second drive - the first was DOA, I returned it and got the one above. Unfortunately, I didn't make a note of what the f/w or anything was, assuming it was just "one of those things". It was a 500GB ST3500320AS though, and like the second one, wasn't being detected in the BIOS.

I have a 500GB ST3500320AS drive, 7200.11, SD15 firmware. Without any warning, it died two days ago. I could hear it working, but it wasn't even being detected in the BIOS. A lot of internet searching about this has led me here, so I could add my experience. The first ST3500320AS drive I got was DOA. I had the replacement 6 months before it died on me on Friday. The company I got it from (I'm based in the UK) said they would send me a replacement. They said that they only considered "other options" when at least three drives had died. I feel like I am working with a time bomb. When I read that Seagate had some kind of firmware fix for this, it eased the annoyance and frustration a bit, but trying to contact them to ask about the firmware patch was a nightmare. I have got to the point where I am expecting a replacement HDD, but am leery about using it - in fact, I *want* it to die on me so I can get something completely different.