All of lore.kernel.org
 help / color / mirror / Atom feed
From: Orion Poplawski <orion@cora.nwra.com>
To: linux-raid@vger.kernel.org
Subject: raid5 missing drive at boot question
Date: Thu, 22 Sep 2005 16:28:50 -0600	[thread overview]
Message-ID: <dgvb75$hp5$1@sea.gmane.org> (raw)

I created a new 8 disk raid5 set with no spares.  Now, when I boot I end 
up with:


md3 : active raid5 sdp1[7] sdo1[6] sdn1[5] sdm1[4] sdl1[3] sdk1[2] sdi1[0]
       3418687552 blocks level 5, 64k chunk, algorithm 2 [8/7] [U_UUUUUU]

which I believe is a "degraded" array.  I then have to do:

mdadm -M -a /dev/md3 /dev/sdj1

to add in the missing disk.  I had to do this after it was created as well.

Why does this happen?  What am I not understanding?

Boot messages:

md: Autodetecting RAID arrays.
md: autorun ...
md: considering sdp1 ...
md:  adding sdp1 ...
md:  adding sdo1 ...
md:  adding sdn1 ...
md:  adding sdm1 ...
md:  adding sdl1 ...
md:  adding sdk1 ...
md:  adding sdi1 ...
md: created md3
md: bind<sdi1>
md: bind<sdk1>
md: bind<sdl1>
md: bind<sdm1>
md: bind<sdn1>
md: bind<sdo1>
md: bind<sdp1>
md: running: <sdp1><sdo1><sdn1><sdm1><sdl1><sdk1><sdi1>
raid5: device sdp1 operational as raid disk 7
raid5: device sdo1 operational as raid disk 6
raid5: device sdn1 operational as raid disk 5
raid5: device sdm1 operational as raid disk 4
raid5: device sdl1 operational as raid disk 3
raid5: device sdk1 operational as raid disk 2
raid5: device sdi1 operational as raid disk 0
raid5: allocated 8376kB for md3
raid5: raid level 5 set md3 active with 7 out of 8 devices, algorithm 2
RAID5 conf printout:
  --- rd:8 wd:7 fd:1
  disk 0, o:1, dev:sdi1
  disk 2, o:1, dev:sdk1
  disk 3, o:1, dev:sdl1
  disk 4, o:1, dev:sdm1
  disk 5, o:1, dev:sdn1
  disk 6, o:1, dev:sdo1
  disk 7, o:1, dev:sdp1


             reply	other threads:[~2005-09-22 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 22:28 Orion Poplawski [this message]
2005-09-23  9:02 ` raid5 missing drive at boot question Neil Brown
2005-09-23 14:51   ` Orion Poplawski

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='dgvb75$hp5$1@sea.gmane.org' \
    --to=orion@cora.nwra.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.