I forgot to mention that it didn't work ...I am including my mdadm.conf also for reference. All my partitions and devices are visible in /proc/partitions. One change after the initramfs....now I don't have any arrays show up in proc/mdstat but the assemble, scan gets them all perfectly...its just not happening automatically at boot time like it used to. 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 GATEWAY # instruct the monitoring daemon where to send mail alerts MAILADDR root # definitions of existing MD arrays ARRAY /dev/md_d127 LEVEL=raid5 NUM-DEVICES=4 METADATA=1.2 UUID=42c56ea0:2484f566:387adc6c:b3f6a014 DEVICES=/dev/sdb,/dev/sdd5,/dev/sdc5,/dev/sda1 NAME=GATEWAY:raid5_280G ARRAY /dev/md_d126 LEVEL=raid5 num-devices=3 METADATA=1.2 UUID=54b83ff7:55316d90:d497a0cb:5a3309fe DEVICES=/dev/sdc6,/dev/sdd6,/dev/sda2 NAME=GATEWAY:raid5_186G ARRAY /dev/md_d125 LEVEL=raid5 NUM-DEVICES=2 METADATA=1.2 UUID=e501ec78:3e45999f:4ecca49e:d48db221 DEVICES=/dev/sdc7,/dev/sdd7 NAME=GATEWAY:raid5_178G 2009/8/23 Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>: > I ran update-initramfs -u to update (which should work for ubuntu > jaunty)...should it be needed, since my root partition is not on raid? > I didn't need to do it so far with any other cluster change? > > 2009/8/23 Robin Hill <robin@xxxxxxxxxxxxxxx>: >> On Sun Aug 23, 2009 at 07:19:44PM +0530, Anshuman Aggarwal wrote: >> >>> Although its not a show stopper, would really appreciate some help on this. >>> >>> My raid arrays don't start up automatically like they used to after I >>> grew them to include the 4th disk (yes, I DID modify the mdadm.conf so >>> I'm not sure what's not working here) >>> Kernel: 2.6.30.4; mdadm 3.0 (are there any other libraries whose >>> version I should be checking also, since I manually upgraded Ubuntu >>> Jaunty to mdadm 3.0) >>> >> <-snip-> >>> >>> This array starts fine when I do the following: >>> >>> mdadm -S /dev/md_d1* >>> mdadm -A -s >>> >>> So, if the scan works without any changes in the mdadm, then why >>> doesn't it work at boot time? >>> >> Have you updated the initrd so the new mdadm.conf is available at boot? >> >> Cheers, >> Robin >> -- >> ___ >> ( ' } | Robin Hill <robin@xxxxxxxxxxxxxxx> | >> / / ) | Little Jim says .... | >> // !! | "He fallen in de water !!" | >> > -- 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
