From: "Andrew Kinney" <andykinney@advantagecom.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 13:34:10 -0800 [thread overview]
Message-ID: <42319E52.19095.2CDA5B5A@localhost> (raw)
In-Reply-To: <87br9plyaf.fsf@tapsellferrier.co.uk>
On 11 Mar 2005 at 20:31, Nic Ferrier wrote:
> The machine I am having trouble with has been running MS Windows for 2
> years.
>
> I just put linux on it (with no other changes) and we get regular
> (twice daily) catastrophic crashes.
>
> Can this be a controller problem? I'm not a hardware expert but it
> doesn't sound like one to me.
It can be a controller problem, but it can also be a drive problem,
cable problem, firmware problem, or a backplane problem. We had a
similar instance that was resolved by replacing the drive with a
different brand, replacing the backplane, replacing the cabling,
replacing the ROMB, and getting the newest firmware. Now, drives
fail gracefully instead of taking the whole container offline. Who
knows what the actual cause was, but the problem is fixed and that's
what I was looking for.
Like Mark S. said, many causes, one symptom. That Dell trouble
ticket is going to be the best way to get it solved. Their Linux
guys have seen it all and can escalate it to an engineer if they
haven't. They're going to ask you for the diagnostic output of
afacli, so you'll want to get that installed if you haven't already.
They can also swap in new components for you.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
next prev parent reply other threads:[~2005-03-11 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 16:06 aacraid died on kernel 2.4.27 Salyzyn, Mark
2005-03-11 20:31 ` Nic Ferrier
2005-03-11 21:34 ` Andrew Kinney [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 20:54 Salyzyn, Mark
2005-03-10 21:01 Nic Ferrier
2005-03-11 6:04 ` 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=42319E52.19095.2CDA5B5A@localhost \
--to=andykinney@advantagecom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox