From: Matthew Mitchell <matthew@geodev.com>
To: Corey McGuire <coreyfro@coreyfro.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 causing lockups
Date: Thu, 26 Jun 2003 08:32:15 -0500 [thread overview]
Message-ID: <3EFAF5DF.70104@geodev.com> (raw)
In-Reply-To: <200306252054340612.008AB828@ilneval.coreyfro.com>
Going along with some suggestions of other respondents, be very
suspicious of your power cables. I had a hell of a time getting a
stable raid running because of dodgy power cables. More accurately, the
5v or 12v lines in some of the little plugs were kind of loose, and they
would lose contact. So get in there with a pair of teeny pliers or
tweezers and crimp those babies on tight.
As an aside, has anyone ever experimented with any type of conductive
compound when putting these things together? IMO the cheesiest part of
the setup is the crappy PC-style power connector, and I wondered about
various solutions from compound to soldering on a PCB for a more
reliable means of powering drives.
Best of luck to you.
Corey McGuire wrote:
> Well, two of my drives did have an older bios, but the upgrade changed nothing.
>
> I noticed that even unmounted, as long as I didn't raidstop the device, the system still crashes.
>
> I tried setting down my bios as much as possible, and I am looking to do the same with the kernel, 2.4.21. I'll try the magic sysrq key, but I can't find my nulmodem cable to save my life, so I'll have to barrow one from work.
>
> My server marches on, but without /dev/md2... I'll try just letting it sit, /dev/md2 intact, over night, but for now, I need it up, even if it is only for fits and spurts.
>
> Thanks everyone, keep the ideas rolling in.
--
Matthew Mitchell
Systems Programmer/Administrator matthew@geodev.com
Geophysical Development Corporation phone 713 782 1234
1 Riverway Suite 2100, Houston, TX 77056 fax 713 782 1829
next prev parent reply other threads:[~2003-06-26 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 3:54 RAID5 causing lockups Corey McGuire
2003-06-26 11:46 ` Mike Black
2003-06-26 13:32 ` Matthew Mitchell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 17:34 Corey McGuire
2003-06-27 5:02 ` Corey McGuire
2003-06-27 5:32 ` Mike Dresser
2003-06-27 5:47 ` Corey McGuire
2003-06-25 19:16 Corey McGuire
2003-06-25 19:28 ` Mike Dresser
2003-06-25 19:41 ` Corey McGuire
2003-06-25 19:56 ` Mike Dresser
2003-06-25 20:51 ` Corey McGuire
2003-06-25 20:36 ` Matt Simonsen
2003-06-25 20:56 ` Corey McGuire
[not found] ` <1056575536.24919.101.camel@mattswrk>
2003-06-25 21:16 ` Corey McGuire
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=3EFAF5DF.70104@geodev.com \
--to=matthew@geodev.com \
--cc=coreyfro@coreyfro.com \
--cc=linux-raid@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).