Changing the number of devices to 12 worked! Thanks! -Bryan On Wed, Mar 28, 2012 at 4:26 AM, NeilBrown <neilb@xxxxxxx> wrote: > On Wed, 28 Mar 2012 03:54:45 -0400 Bryan Bush <bbushvt@xxxxxxxxx> wrote: > >> On Wed, Mar 28, 2012 at 12:18 AM, NeilBrown <neilb@xxxxxxx> wrote: >> > On Tue, 27 Mar 2012 22:44:18 -0400 Bryan Bush <bbushvt@xxxxxxxxx> 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
