From: Bill Davidsen <davidsen@tmr.com>
To: Tobias Rehn <tr@crontex.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software Raid 5, multiple raid controller disk mixup problem
Date: Tue, 24 Jul 2007 15:18:52 -0400 [thread overview]
Message-ID: <46A6509C.6000302@tmr.com> (raw)
In-Reply-To: <469CED66.50109@crontex.de>
Tobias Rehn wrote:
> Hey Guys,
>
> I am currently having a strange problem. I have a system with 4
> onboard sata ports. The system also has four 4-port sata controllers
> plugged into it.
>
> The raid works fine but if i reboot the system, sometimes my harddisks
> are mixed up so that my system disk(normally sda) is sometimes sdb or
> sdc... My system disk is plugged to one of onboard sata ports.
>
> I already tried to bind the disks statically via udev to a certain
> device name, but no chance.
>
> Are there any other methods to stop this mixing of the drives? Or does
> anyone have the same problem?
I was really hoping one of the hardware guys would answer this. My only
thought is that you have a feature enabled which allows simultaneous
discovery, and that the 1st drive spun up is sda,, etc. If you could
save your dmesg from a good and bad boot, and make them available,
someone may see the problem, I can't guess beyond what I've said already.
If you are building the arrays using UUID in the config file, it should
matter what they are called, of course. Mine just list devices
PARTITIONS and then a bunch of arrays based on UUID. It makes for a huge
dmesg file, of course, filled meaningless babble about "found this" and
"that doesn't match." But it works every blessed time, which is more
important in the long run.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2007-07-24 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 16:25 Software Raid 5, multiple raid controller disk mixup problem Tobias Rehn
2007-07-24 19:18 ` Bill Davidsen [this message]
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=46A6509C.6000302@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=tr@crontex.de \
/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).