From: Peter Smith <peter.smith@utsouthwestern.edu>
To: linux-ide@vger.kernel.org
Subject: Re: Promise SATA oops
Date: Tue, 27 Dec 2005 17:51:16 -0600 [thread overview]
Message-ID: <43B1D374.5070307@utsouthwestern.edu> (raw)
In-Reply-To: <20051220201719.GC15466@vitelus.com>
Aaron Lehmann wrote:
>Argh, died again!! It had been stable for over 12 days. Same error
>message, and the root md is degraded and dirty just like last time.
>This is a very severe state with high risk of data loss. When things
>went sour, terminals and most applications still kept working, but
>anything that touched the filesystem froze up. I had a shell open in a
>chroot on a ramdisk, but dmesg just hung for a few minutes and then
>exited with a "Bus error". I had no other way of examining the kernel
>log since the machine runs X.
>
>This was running 2.6.15-rc4. Crashes seem to happen less frequently
>with it than with 2.6.14.x, but when they happen they leave the RAID
>in a severe state. I also don't think 2.6.14.2 said anything about
>disabling the IRQ.
>
>I'm very desperate now. About every week I experience a crash that
>damages my RAID array to the point where it can't boot, as if the
>instability wasn't bad enough. Do I need to buy a hardware RAID card?
>
>
>
I personally wouldn't recommend a hardware RAID card.. Are you still
experiencing difficulties? Have you *tried* an i386 build? Can you work
on getting more data out of the Ooops'es--this would involve setting up
a serial console connection to another box and receiving dumps that way,
there are How-tos out there on this setup.. Another possibility is the
Kernel Crash Dump project [1]... Btw, I have (fairly simple) setup here
at my office, using Fedora Core 3, 2.6.12-1.1381_FC3smp kernel, dual
P3-500mz, 512MB ram, two Promise Sata2-150 TX4s, and five Seagate 200GB
drives.. I haven't had any problems with it since it was installed.
Granted the hardware and software are a bit behind the curve, it has
been sailling along quietly and steadily, so it is possible.
Peter
[1] http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11google.com
next prev parent reply other threads:[~2005-12-27 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 4:58 Promise SATA oops Aaron Lehmann
2005-12-02 5:29 ` Jeff Garzik
2005-12-02 19:51 ` Aaron Lehmann
2005-12-03 10:09 ` Erik Slagter
2005-12-20 20:17 ` Aaron Lehmann
2005-12-27 23:51 ` Peter Smith [this message]
2006-02-21 4:21 ` Aaron Lehmann
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=43B1D374.5070307@utsouthwestern.edu \
--to=peter.smith@utsouthwestern.edu \
--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 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).