From: NeilBrown <neilb@suse.de>
To: Bryan Bush <bbushvt@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 grow failed
Date: Wed, 28 Mar 2012 19:26:01 +1100 [thread overview]
Message-ID: <20120328192601.3db82133@notabene.brown> (raw)
In-Reply-To: <CAJ72viMxgfjhQiqJYVnjBQGfCq7jtegfvUY0nRdj46XDedeSjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2487 bytes --]
On Wed, 28 Mar 2012 03:54:45 -0400 Bryan Bush <bbushvt@gmail.com> wrote:
> On Wed, Mar 28, 2012 at 12:18 AM, NeilBrown <neilb@suse.de> wrote:
> > On Tue, 27 Mar 2012 22:44:18 -0400 Bryan Bush <bbushvt@gmail.com> wrote:
> >
> >> I hope this is the right place to ask this question. I have at 8
> >> drive RAID 6 array that I wanted to grow to 13 drives (adding 5 more).
> >> I issued the mdadm command and checked /proc/mdstat and all looked
> >> well. However at some point in time a disk failed and that hung my
> >> system. Upon reboot the array is inactive and I can't get it to
> >> reassemble.
>
> > Hmmm... what do you have in /etc/mdadm.conf??
>
> root@diamond:~# cat /etc/mdadm/mdadm.conf
> # mdadm.conf
> #
> # Please refer to mdadm.conf(5) for information about this file.
> #
>
> # by default, scan all partitions (/proc/partitions) for MD superblocks.
> # alternatively, specify devices to scan, using wildcards if desired.
> DEVICE partitions
>
> # auto-create devices with Debian standard permissions
> CREATE owner=root group=disk mode=0660 auto=yes
>
> # automatically tag new arrays as belonging to the local system
> HOMEHOST <system>
>
> # instruct the monitoring daemon where to send mail alerts
> MAILADDR root
>
> # definitions of existing MD arrays
>
> # This file was auto-generated on Fri, 14 Jan 2011 22:22:14 -0500
> # by mkconf $Id$
>
> ARRAY /dev/md1 level=raid6 num-devices=8 metadata=01.02 name=1
> UUID=fa32e2c5:e7bda20b:32af7c90:c7ee61eb
I think this array now has 13 devices, not 8. You might want to fix that.
If you do, it might all magically start working.
(also get rid of the metadata= or make it metadata=1.2)
Or just get rid of the num-devices= bit.
> ARRAY /dev/md0 level=raid5 num-devices=4 metadata=00.90
> UUID=989c3b8b:bd60d243:683690d9:73a11dfa
>
> root@diamond:~#
>
> >
> > Though if the names have changed at all it would be safer to do
> >
> > mdadm -Asf /dev/md1 -u fa32e2c5:e7bda20b:32af7c90:c7ee61eb
> >
>
> root@diamond:~# mdadm -Asf /dev/md1 -u fa32e2c5:e7bda20b:32af7c90:c7ee61eb
> mdadm: metadata format 01.02 unknown, ignored.
> mdadm: metadata format 00.90 unknown, ignored.
> mdadm: no devices found for /dev/md1
Odd. I the above change to mdadm.conf doesn't help, try rerunning this
command with --verbose and report the result.
NeilBrown
> root@diamond:~#
>
> Didn't seem to help.
> Any other ideas?
> Thanks
> -Bryan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-03-28 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 2:44 RAID6 grow failed Bryan Bush
2012-03-28 3:22 ` Mathias Burén
2012-03-28 4:18 ` NeilBrown
2012-03-28 7:54 ` Bryan Bush
2012-03-28 8:26 ` NeilBrown [this message]
2012-03-28 10:35 ` Bryan Bush
2012-03-31 19:38 ` Bryan Bush
2012-03-31 22:00 ` NeilBrown
2012-03-31 23:24 ` Bryan Bush
2012-04-01 7:05 ` Bryan Bush
2012-04-01 23:54 ` NeilBrown
2012-04-02 0:02 ` Bryan Bush
2012-04-02 0:26 ` NeilBrown
2012-04-02 0:44 ` Bryan Bush
2012-04-02 2:12 ` NeilBrown
2012-04-02 2:59 ` Bryan Bush
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=20120328192601.3db82133@notabene.brown \
--to=neilb@suse.de \
--cc=bbushvt@gmail.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