On Wed, Jan 27, 2010 at 7:41 PM, Luca Berra <bluca@xxxxxxxxxx> wrote: > On Wed, Jan 27, 2010 at 06:32:57PM +0000, Kristleifur Dađason wrote: >> >> # mdadm.conf >> # >> >> # by default, scan all partitions (/proc/partitions) for MD superblocks. >> # alternatively, specify devices to scan, using wildcards if desired. >> DEVICE partitions /dev/md/d0 /dev/md/d1 >> >> # auto-create devices with Debian standard permissions >> # CREATE owner=root group=disk mode=0660 auto=mdp >> >> # automatically tag new arrays as belonging to the local system >> HOMEHOST <system> >> >> # definitions of existing MD arrays >> >> ARRAY /dev/md/d0 metadata=1.1 name=mamma:d0 >> UUID=7f98e926:206a8ebe:59fc8d7b:4644a883 level=raid6 num-devices=6 # >> container=6f98a7a8:d7b50181:587c27d1:59d6d137 >> >> ARRAY /dev/md/d1 metadata=1.1 name=mamma:d1 >> UUID=da547022:042a6f68:d5fe251e:5e89f263 level=raid6 num-devices=6 # >> container=6f98a7a8:d7b50181:587c27d1:59d6d137 >> >> ARRAY /dev/md/tank metadata=1.1 name=mamma:tank >> UUID=6f98a7a8:d7b50181:587c27d1:59d6d137 level=raid0 num-devices=2 >> devices=/dev/md/d0,/dev/md/d1 >> > > this kind of setup should be working without any issue on recent mdadm > try removing > DEVICE partitions /dev/md/d0 /dev/md/d1 > and the "devices=/dev/md/d0,/dev/md/d1" from mdadm.conf > and let it discover things on boot by itself > > L. > Many thanks for the reply! However, that's how the mdadm.conf looked like until today - adding the DEVICE and devices stuff is something I put in to get things to autoassemble themselves fully, as I thought 'man mdadm.conf' indicated it. Still, I'll certianly try - with and without - and double-checking that my initramfs is OK. Any further input most well appreciated. -- Kristleifur -- 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
