From: Neil Brown <neilb@cse.unsw.edu.au>
To: Ken Causey <ken@ineffable.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can't add missing member back in???
Date: Thu, 27 Jun 2002 04:09:27 +1000 (EST) [thread overview]
Message-ID: <15642.855.558011.545081@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Ken Causey on June 26
On June 26, ken@ineffable.com wrote:
> Hi,
>
> Interesting problem. I'm setting up an all software RAID system and
> after a few fits and starts have reached some success. I started to do
> some testing and have run into a problem. What I was doing is I was one
> by one unplugging one of the SCSI drives and then powering up the system
> to make sure it would power up properly. The first time I did this
> everything worked great. I plugged the drive back up and used
> raidhotadd to recover and got everything to UUU. I then powered off and
> unplugged another drive, system boots up great with only two drives.
> Now its time to plug the drive back in and rebuild the array to be ready
> to unplug the last of the three drives for a thorough test. Only, now I
> can ONLY boot up if I DO NOT have the missing drive plugged in. This is
> really weird. If I have all three devices attached then it claims that
> 2/3 of the devices that make up md2 (my root) are unavailable and well
> then we are screwed. WTF?
Let me guess... you are using "raidstart" to start the arrays?
If so, that is your problem. It is broken.
Either change the partition type to use auto-detect, or use
mdadm:
http://www.cse.unsw.edu.au/~neilb/source/mdadm/
If you aren't using raidstart, tell me and I try harder.
NeilBrown
next prev parent reply other threads:[~2002-06-26 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 17:10 Can't add missing member back in??? Ken Causey
2002-06-26 18:09 ` Neil Brown [this message]
2002-06-26 18:14 ` Ken Causey
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=15642.855.558011.545081@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=ken@ineffable.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).