Barracuda XT, Barracuda, Barracuda Green, DiamondMax and other desktop SATA and IDE drives

[nomoreSg]

Its very interesting - they say something about the data recovery:

Q: How will Seagate help me if I lost data on this drive?
A. There is no data loss in this situation. The data still resides on the drive but it is inaccessible to
the end user. If you are unable to access your data due to this issue, Seagate will provide free
data recovery services. Seagate will work with you to expedite a remedy to minimize any
disruption to you or your business.

[JefUK]

I have also been getting IO errors with ST3500320AS. It causes one or more of my RAID10 drives to go offine and then goes through several hours while the array rebuilds. This has only happened since I updated to SD1A. At first I thought I had fixed the problem by udating to the latest chipset set drivers, but sadly this is not the case.

Clearly this is a firmware problem beacuse so many people have reported it. Has anyone had any response from Seagate yet about a solution?

Message Edited by JefUK on 02-05-2009 06:37 AM

[ModProbe]

---

JefUK wrote:

I have also been getting IO errors with ST3500320AS. It causes one or more of my RAID10 drives to go offine and then goes through several hours while the array rebuilds. This has only happened since I updated to SD1A. At first I thought I had fixed the problem by udating to the latest chipset set drivers, but sadly this is not the case.

Clearly this is a firmware problem beacuse so many people have reported it. Has anyone had any response from Seagate yet about a solution?

Message Edited by JefUK on 02-05-2009 06:37 AM

---

Already 3 in this topic... Good for us.

[Eckelmann]

I have one of that drive

ST31000333AS

S/N: 9TE151B3

FW: LC15 (what's that?)

The serial checker says: AFFECTED

The download offers only SD1B, but that firmware is the wrong one!!

Early webpages from seagate said CC and LC firmware are not affected.

Now, they are saying CC firmware is not affected.

The man on the support hotline said today, LC is a "server firmware" (???) and he doesn't know if it's affected.

So what now? Everyone is confused...

[jellokitty92]

IO errors are problems for all kinds of drives

Pardon me for breaking up everyone's conspiracy theories, but I've got a few of these .11s lying around and I'd like to know if anyone has any solid proof that the SN checker thingy yields incorrect results 

Or is it just that youre just convinced that your drive is effected and so obviously the SN checker is wrong?  Help me out here

[donidonidoni]

---

jellokitty92 wrote:

Pardon me for breaking up everyone's conspiracy theories, but I've got a few of these .11s lying around and I'd like to know if anyone has any solid proof that the SN checker thingy yields incorrect results 

Or is it just that youre just convinced that your drive is effected and so obviously the SN checker is wrong?  Help me out here

---

Please read through the thread and you'll see we have already taken a step back and discussed this. There is no proof of anything. All we know is many folks with similar widespread problems have drives reported UNAFFECTED. Whether that is because of incorrect criteria in the sn checker or because Seagate was only looking for one type of firmware problemwhen there are really several is unclear. The only thing that is clear is there are several widespread firmware problemsthat have yet to be addressed by Seagate.

[donidonidoni]

---

Eckelmann wrote:

I have one of that drive

ST31000333AS

S/N: 9TE151B3

FW: LC15 (what's that?)

The serial checker says: AFFECTED

The download offers only SD1B, but that firmware is the wrong one!!

Early webpages from seagate said CC and LC firmware are not affected.

Now, they are saying CC firmware is not affected.

The man on the support hotline said today, LC is a "server firmware" (???) and he doesn't know if it's affected.

So what now? Everyone is confused...

---

Wow, that IS confusing. Can support escalate you to someone who knows more? They have to be able to give you a definitive answer one way or the other. Even if they have to ask engineering. No?

[Eric-MicroAge]

All I can say is this has become extremely confusing.  I've seen so many different versions of firmware tossed around these last couple of weeks it has made my head spin.

My company has sold hundreds of the affected .11 drives (mostly ST3500320AS), and before we inform our clients and begin to update the firmware on all of these machines, we need to know if the currently available firmware actually fixes the problem or if Seagate is still offering firmware which does not resolve the cache issue.

In addition to this, when we attempted to update several ST31000333AS drives, but the update says the drive is the wrong type for the firmware update.  It was downloaded this morning, and will not update the drives, which are running firmware SD15.

Now, I have been on hold with Seagate technical support for about 2 hours (I actually feel sorry for the techs), but I cannot sit at my desk for the remained of the work day hoping to get a live person on the phone.  Tech Support email is a waste of keyboard clicks.

Message Edited by Eric-MicroAge on 02-05-2009 09:00 AM

[Sark]

---

JefUK wrote:

I have also been getting IO errors with ST3500320AS. It causes one or more of my RAID10 drives to go offine and then goes through several hours while the array rebuilds. This has only happened since I updated to SD1A. At first I thought I had fixed the problem by udating to the latest chipset set drivers, but sadly this is not the case.

Clearly this is a firmware problem beacuse so many people have reported it. Has anyone had any response from Seagate yet about a solution?

Message Edited by JefUK on 02-05-2009 06:37 AM

---

having the same issues with my raid10 and four ST3500320AS. yes i did contact seagate support and they told me to reformat the drives and rebuild the raid volume from scratch. which i did but it did not solve the problem at all. tried the latest chipset drivers (intel x48) as well, does not make a difference. 

right now i cant use the four ST3500320AS at all because i cannot have the raid volume rebuilding itself almost constantly and i was forced to replace them with four hard drives of another manufacturer that work just fine, just like the ST3500320AS ones did before i updated to firmware SD1A.

it is downright unacceptable to have four almost new seagate harddrives that used to work with the apparently faulty firmware SD15 and dont work properly since the update to SD1A anymore. i also asked seagate support if it is possible to downgrade to SD15 (it isnt) or if there is a new firmware in the making that addresses this issue (no answer).

Message Edited by Sark on 02-05-2009 09:21 AM

[jellokitty92]

doniX3

If theyre reported UNEFFECTED, then doesn't that mean that theyre not effected? 

that's why I asked the question - if the tool says it's good to go, then it's good to go, right?

Hard drives fail for all sorts of reasons, you know.  My guess is that these other failures on these uneffected drives are failures due to other reasons and that there's this conspiracy bandwagon jumping here.  Just a thought