From: Robert Hancock <hancockr@shaw.ca>
To: Diego Calleja <diegocg@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?
Date: Mon, 19 Jan 2009 20:55:05 -0600 [thread overview]
Message-ID: <49753D09.8060503@shaw.ca> (raw)
In-Reply-To: <20090120002923.065f24ca@diego-desktop>
Diego Calleja wrote:
> Tech sites are reporting everywhere a massive flaw in seagate drives that
> can lock up the drive and make it unusable (the bios doesn't detect it, you
> can't read the data). Haven't read anything about it here on the lists.
> Seagate has ack'ed the problem:
> http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931
>
> So, apparently there're a lot of drives on the market (including mine)
> that can die any day. Are those drives going to be blacklisted? It's
> still not clear if the firmware update is safe (some affected but
> working drives are dying after the firmware update), so some people
> like me is still waiting (and hoping that the drive doesn't die) for
> more stable firmware updates...
>
> Here is the list of drives+firmware affected, according to the support site
> as of now. Some models are still being diagnosed.
There are a few drives which are currently marked to disable NCQ and
warn the user that the firmware that should be upgraded:
ST31500341AS
ST31000333AS
ST3640623AS
ST3640323AS
ST3320813AS
ST3320613AS
all for firmware versions SD15 through SD19.
>
>
> Seagate Barracuda 7200.11 (http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207951)
>
> Models Affected:
> ST3500320AS
> ST3640330AS
> ST3750330AS
> ST31000340AS
> Firmware Affected
> SD15, SD16, SD17, SD18, SD19, AD14
> Recommended Firmware Update
> SD1A
>
> Seagate Barracuda 7200.11, page 2 (http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207957)
> Models Affected:
> ST31500341AS
> ST31000333AS
> ST3640323AS
> ST3640623AS
> ST3320613AS
> ST3320813AS
> ST3160813AS
> Firmware Affected
> Still Unknow
> Recommended Firmware Update
> Still Unknow
>
>
> Seagate Barracuda ES.2 (http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207963)
> Models Affected:
> ST3250310NS
> ST3500320NS
> ST3750330NS
> ST31000340NS
> Firmware Affected
> Still Unknow
> Recommended Firmware Update
> Still Unknow
>
> DiamondMax 22 (http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207969)
> Models Affected:
> STM3500320AS
> STM3750330AS
> STM31000340AS
> Firmware Affected
> MX15 (or higher)
> Recommended Firmware Update
> MX1A
>
> DiamondMax 22 (http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207975)
> Models Affected:
> STM31000334AS
> STM3320614AS
> STM3160813AS
> Firmware Affected
> Still Unknow
> Recommended Firmware Update
> Still Unknow
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-01-20 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 23:29 Faulty seagate drives, are going to be blacklisted? Diego Calleja
2009-01-20 0:22 ` David Rees
2009-01-20 2:55 ` Robert Hancock [this message]
2009-01-20 15:26 ` Diego Calleja
2009-01-21 0:30 ` Robert Hancock
2009-01-26 19:04 ` Felix Miata
2009-01-26 19:54 ` Mark Lord
2009-01-26 20:57 ` Gene Heskett
2009-01-26 21:34 ` Felix Miata
2009-01-26 23:56 ` Mark Lord
2009-01-20 3:32 ` Valdis.Kletnieks
2009-01-20 15:30 ` Diego Calleja
2009-01-20 17:24 ` Valdis.Kletnieks
2009-01-20 18:18 ` Diego Calleja
2009-01-21 10:27 ` Patrick Horn
2009-01-25 1:12 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49753D09.8060503@shaw.ca \
--to=hancockr@shaw.ca \
--cc=diegocg@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).