On Tuesday November 28, patrik@xxxxxxxxxxx wrote: > Hi, > > I just got a new SATA controller and moved some of my drives around, so > the device numbers of course got all messed up. I expected mdadm to be > able to handle that, which it did when I moved one device. However, when > I moved the next 3, things got weird. Here's the output from mdadm > --assemble --scan -v: > > ... <removed unmatching devices> --snip-- > mdadm: /dev/md5 assembled from 7 drives - not enough to start the array. > > The added drives are the correct ones, but how it adds 10 drives but > then thinks that it's only assembled 7 mystifies me. Is this a bug? Weird... What version of mdadm? Can you show us "mdadm --examine" of a couple of devices? Any kernel logs while this is happening? NeilBrown - 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
