From: Felix Miata <mrmazda@ij.net>
To: linux-ide@vger.kernel.org
Subject: Re: Faulty seagate drives, are going to be blacklisted?
Date: Mon, 26 Jan 2009 14:04:32 -0500 [thread overview]
Message-ID: <497E0940.3020409@ij.net> (raw)
In-Reply-To: <49753D09.8060503@shaw.ca>
On 2009/01/19 20:55 (GMT-0600) Robert Hancock composed:
> 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.
I just got off the phone with Seagate tech because I could not find out
whether the SD22 firmware in my ST3320613AS was an affected version. He said
that it was and recommended I upgrade.
The "Drive Detect software" that
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207957
directs to use to discover the firmware revision requires windoz. Anyone know
if it works under Wine? Instead I used a bootable Seatools CD that came in a
retail Seagate HD package.
--
"Train a child in the way he should go, and when he
is old he will not turn from it." Proverbs 22:6 NIV
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
next prev parent reply other threads:[~2009-01-26 19:15 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
2009-01-20 15:26 ` Diego Calleja
2009-01-21 0:30 ` Robert Hancock
2009-01-26 19:04 ` Felix Miata [this message]
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=497E0940.3020409@ij.net \
--to=mrmazda@ij.net \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.