From: Ryan Anderson <ryan@autoweb.net>
To: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aacraid died on kernel 2.4.27
Date: Fri, 11 Mar 2005 01:04:56 -0500 [thread overview]
Message-ID: <20050311060456.GK20923@ryan2> (raw)
In-Reply-To: <87sm33kyf5.fsf@tapsellferrier.co.uk>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Thu, Mar 10, 2005 at 09:01:50PM +0000, Nic Ferrier wrote:
> I've been trying, without success, to get the aacraid driver to work
> reliably on a Dell 2650 Poweredge.
I've had problems there, too. With kernel 2.6.8.
I just had another failure, and I got some better logs.
Can you install the "afacli" utility (Dell-branded version of aacli),
and run
diag show history /old
from afacli?
If you can't seem to get the OLD history to show (compare diag show
history /current with diag shot history /old), try diag dump text - you
may find some useful messages there.
The other, standard, suggestion is to go through and open a ticket with
Dell, and do all the hardware diagnostics to try and see if the error
can be traced to hardware problems or not.
Good luck, I hope you find a fix faster than I have (still trying,
unfortunately)
--
Ryan Anderson
AutoWeb Communications, Inc.
email: ryan@autoweb.net
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-11 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 21:01 aacraid died on kernel 2.4.27 Nic Ferrier
2005-03-11 6:04 ` Ryan Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 16:06 Salyzyn, Mark
2005-03-11 20:31 ` Nic Ferrier
2005-03-11 21:34 ` Andrew Kinney
2005-03-11 20:54 Salyzyn, Mark
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=20050311060456.GK20923@ryan2 \
--to=ryan@autoweb.net \
--cc=linux-scsi@vger.kernel.org \
--cc=nferrier@tapsellferrier.co.uk \
/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.