Bryce wrote: [] > mdadm -C -l5 -n5 -c128 /dev/md0 /dev/sdf1 /dev/sde1 /dev/sdg1 /dev/sdc1 /dev/sdd1 ... > IF you don't have the configuration printout, then you're left with > exhaustive brute force searching of the combinations You're missing a very important point -- --assume-clean option. For experiments like this (trying to figure out the order of disks), you'd better ensure the data on disks isn't being changed while you try different combinations. But on each build, md always destroys one drive by re-calculating parity. You have to stop it from doing so - to not trash your data. Another option is to use one missing drive always, i.e., mdadm -C -l5 -n5 -c128 /dev/md0 /dev/sdf1 missing /dev/sdg1 /dev/sdc1 /dev/sdd1 so that the array will be degraded and no way to resync anything - this also prevents md from trashing data. /mjt - 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
