On 02/22/2011 01:36 PM, Simon McNair wrote: > Phil, > phew I didn't know that: > "mdadm: /dev/sdo has wrong uuid. > mdadm: /dev/sdn1 has wrong uuid." > > was just that the array UUID didn't match mdadm.conf, it would be nice if it said: > > "mdadm: /dev/sdo uuid does not match mdadm.conf. > mdadm: /dev/sdn1 uuid does not match mdadm.conf" > my mdadm.conf now reads > > DEVICE partitions > CREATE owner=root group=disk mode=0660 auto=yes > HOMEHOST <system> > MAILADDR root > # ARRAY /dev/md/0 level=raid5 metadata=1.1 num-devices=10 UUID=0a72e40f:aec6f80f:a7004457:1a84a7a8 name=pro�lox:0 > ARRAY /dev/md/0 metadata=1.1 UUID=12c2af00:10681e10:fb17e449:1404739c name=proxmox:0 You can strip it down to be effectively "auto", but I wouldn't remove it. Since you are using partitioned devices throughout your system, something like this: DEVICE /dev/sd*[0-9] AUTO all Or slightly more restrictive: DEVICE /dev/sd*[0-9] ARRAY /dev/md/0 UUID=12c2af00:10681e10:fb17e449:1404739c > I'm afraid to do another reboot incase something else goes wrong ;-). Just for my info, when I only have a single array there isn't much chance of it being assigned anything other than md0, so could I not just leave mdadm.conf empty ? LVM doesn't care what device name the physical volumes end up with. Please reboot when the system is quiet again to make sure your new mdadm.conf works. Or stop your array, and then do a "mdadm --assemble --scan", which is effectively the same. Phil -- 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
