From: Otto Solares <solca@guug.org>
To: Phil Brutsche <phil@brutsche.us>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aacraid, seagate and adaptec issues [Was: Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline]
Date: Wed, 10 Nov 2004 15:08:24 -0600 [thread overview]
Message-ID: <20041110210824.GD8047@guug.org> (raw)
In-Reply-To: <41927B0F.6000902@brutsche.us>
On Wed, Nov 10, 2004 at 02:33:19PM -0600, Phil Brutsche wrote:
> Otto Solares wrote:
>
> > A seagate time-out issue with exactly my disks:
> >
> > http://www.seagate.com/support/disc/u320_firmware.html
>
> [...]
>
> > Does anybody have this seagate firmware updates?
>
> I have a pair of RAID5s with these Seagate drives; I have flashed the
> firmware on the affected drives to the latest 0006 rev (they are 15k RPM
> drives).
I have Dell servers with the following disks:
SPEED BRAND MODEL REV
10K SEAGATE ST3146807 DS09
15K SEAGATE ST373453 DX10
Clearly they are affected by the _time_out_ issue.
They are in RAID1 configurations. I couldn't obtain the
firmware from Dell nor Seagate, how do you obtain the
firmware updates?
-otto
next prev parent reply other threads:[~2004-11-10 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 7:53 Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline Andrew Morton
2004-10-28 18:21 ` Phil Brutsche
2004-11-09 20:22 ` Ryan Anderson
2004-11-09 21:32 ` Otto Solares
2004-11-09 23:49 ` Andrew Kinney
2004-11-10 17:43 ` aacraid, seagate and adaptec issues [Was: Re: Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline] Otto Solares
2004-11-10 20:33 ` Phil Brutsche
2004-11-10 21:08 ` Otto Solares [this message]
2004-11-23 21:41 ` Fw: [Bugme-new] [Bug 3651] New: dell poweredge 4600 aacraid PERC 3/Di Container goes offline Ryan Anderson
2004-11-23 22:58 ` Otto Solares
2004-11-24 1:00 ` Andrew Kinney
2004-11-24 18:35 ` Ryan Anderson
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=20041110210824.GD8047@guug.org \
--to=solca@guug.org \
--cc=linux-scsi@vger.kernel.org \
--cc=phil@brutsche.us \
/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).