linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Causey <ken@ineffable.com>
To: linux-raid@vger.kernel.org
Subject: Can't add missing member back in???
Date: 26 Jun 2002 12:10:57 -0500	[thread overview]
Message-ID: <1025111457.596.13.camel@temp> (raw)

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?

Anyway, here's my setup, let me know what else you need to know:

/boot	/dev/md0 	RAID1	(/dev/sda1 /dev/sdb1 /dev/sdc1)
swap	/dev/md1	RAID1	(/dev/sda2 /dev/sdb2 /dev/sdc2)
/	/dev/md2	RAID5	(/dev/sda3 /dev/sdb3 /dev/sdc3)
/home	/dev/md3	RAID5	(/dev/sda5 /dev/sdb5 /dev/sdc5)
/var	/dev/md4	RAID5	(/dev/sda6 /dev/sdb6 /dev/sdc6)

The drive that is currently "failed" is /dev/sdb.  Again, the system
boots up happily with sdb disconnected.  But has fits if it is
reconnected and all 3 drives are connected.

All help is appreciated,

Ken Causey




             reply	other threads:[~2002-06-26 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 17:10 Ken Causey [this message]
2002-06-26 18:09 ` Can't add missing member back in??? Neil Brown
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=1025111457.596.13.camel@temp \
    --to=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).