From: Molle Bestefich <molle.bestefich@gmail.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Re: Drive fails & raid6 array is not self rebuild .
Date: Thu, 8 Sep 2005 21:34:09 +0200 [thread overview]
Message-ID: <62b0912f0509081234326cc15a@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509081247060.29776@filesrv1.baby-dragons.com>
Mr. James W. Laferriere wrote:
> Is there a documented procedure to follow during
> creation or after that will get a raid6 array to self
> rebuild ?
MD will rebuild your array automatically, given that it has a spare disk to use.
> raid5: Disk failure on sde, disabling device. Operation continuing on 35 devices
Seems like a raid5, not raid6..
> [UU_UUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU]
No need to do any rebuilding on the remaining devices, since the data
on them are fine.
You've lost redundancy however, so you should add a new disk to the array ASAP.
With 35 disks, I'd recommend that you at least use raid6 in place of raid5..
next prev parent reply other threads:[~2005-09-08 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 11:38 my first raid disaster on reboot :o( update Ken Walker
2005-09-08 18:54 ` Drive fails & raid6 array is not self rebuild Mr. James W. Laferriere
2005-09-08 19:34 ` Molle Bestefich [this message]
2005-09-08 21:09 ` Neil Brown
2005-09-08 21:39 ` Mr. James W. Laferriere
2005-09-09 0:50 ` Neil Brown
2005-09-09 2:05 ` Mr. James W. Laferriere
2005-09-09 2:15 ` Mr. James W. Laferriere
2005-09-09 7:40 ` Neil Brown
2005-09-09 11:37 ` David M. Strang
2005-09-09 13:52 ` Mr. James W. Laferriere
2005-09-09 13:59 ` David M. Strang
2005-09-09 19:59 ` Mr. James W. Laferriere
2005-09-09 20:07 ` Mr. James W. Laferriere
2005-09-09 20:58 ` OT: lilo overwriting partition info ? Mr. James W. Laferriere
2005-09-09 21:49 ` Drive fails & raid6 array is not self rebuild Neil Brown
2005-09-10 0:54 ` Mr. James W. Laferriere
2005-09-10 21:58 ` Neil Brown
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=62b0912f0509081234326cc15a@mail.gmail.com \
--to=molle.bestefich@gmail.com \
--cc=babydr@baby-dragons.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.