On May 31, 2016, at 2:19 PM, Phil Turmel <philip@xxxxxxxxxx> wrote: > On 05/30/2016 10:43 PM, Peckins, Steven E wrote: >> >> The component devices in the array are supposed to be multipath devices (dm-multipath), but for some reason, when the server was restarted, md grabbed both dm-* components and raw devices. I *think* that this is what caused the problem. > > Quite possible. You probably need a DEVICES clause in your mdadm.conf > to exclude the raw devices from the arrays. I had a typo in the DEVICE glob for the system disks (/dev/sd[ab]* instead of /dev/sd[ab][12]). >> I'm seeking advice on how to proceed at this point. If more information is required, please ask. > > Hmmm. The partial success on mdadm --force suggests trying that again. > Possible with --force twice on the command line. > > Forced assembly is precisely what you need -- don't despair and attempt > anything else. Repeating the command was not successful; it is still reporting "/dev/md10 assembled from 5 drives and 1 spare - not enough to start the array." Four drives are listed as “possibly out of date." I assume those are the four that are not being incorporated. Output from --assemble --force 1x and 2x: http://pastebin.com/k1dT2zYC --steve-- 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
