Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: linux-raid@vger.kernel.org
Subject: degraded raid5 at bootup
Date: Fri, 13 Aug 2004 12:49:18 -0700	[thread overview]
Message-ID: <411D1B3E.9050306@tupshin.com> (raw)

I have a 5 disk raid5 using autodetect partitions. If I have a clean 
array when I shut down, I always have a degraded array with one disk 
removed when I boot back up. Below I include the relevant dmesg output. 
hdi1 is always the problem. If I do a "mdadm -a /dev/md0 /dev/hdi1", 
then the array rebuilds without a problem, and runs clean until I reboot 
again. Any suggestions?

Kernel is 2.6.8-rc2-mm2, but I've tried it with a few other recent 
kernels (mm and not) and all have the same problem. Distro is Debian Sid.

-Tupshin

md: considering hdl1 ...
md:  adding hdl1 ...
md:  adding hdj1 ...
md: hdi1 has different UUID to hdl1
md:  adding hdh1 ...
md:  adding hde1 ...
md: created md0
md: bind<hde1>
md: bind<hdh1>
md: bind<hdj1>
md: bind<hdl1>
md: running: <hdl1><hdj1><hdh1><hde1>
raid5: device hdl1 operational as raid disk 4
raid5: device hdj1 operational as raid disk 3
raid5: device hdh1 operational as raid disk 1
raid5: device hde1 operational as raid disk 0
raid5: allocated 5242kB for md0
raid5: raid level 5 set md0 active with 4 out of 5 devices, algorithm 2
RAID5 conf printout:
 --- rd:5 wd:4 fd:1
 disk 0, o:1, dev:hde1
 disk 1, o:1, dev:hdh1
 disk 3, o:1, dev:hdj1
 disk 4, o:1, dev:hdl1
md: considering hdi1 ...
md:  adding hdi1 ...
md: md0 already running, cannot run hdi1
md: export_rdev(hdi1)
md: ... autorun DONE.


             reply	other threads:[~2004-08-13 19:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 19:49 Tupshin Harper [this message]
2004-08-13 20:19 ` degraded raid5 at bootup John Stoffel

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=411D1B3E.9050306@tupshin.com \
    --to=tupshin@tupshin.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