On 09/22/2013 11:34 PM, Dave Gomboc wrote: >> If you'll generate the following for each member, we'll see what we can do: >> >> dd if=/dev/sdX1 bs=512 skip=2048 count=16 2>/dev/null |hexdump -C >> dd if=/dev/sdX1 bs=512 skip=3072 count=16 2>/dev/null |hexdump -C Ok. I can't determine how the superblocks ended up the way they did, but the first two chunks appear to follow the proper patterns. I think you're best bet is to disconnect two of the drives, leaving one that identifies as "0" and one that identifies as "3". Then use "mdadm -Af /dev/mdX /dev/sdY1 /dev/sdZ1" The "-f" will force the assembly without regard to the event counts. Then you can take a backup. Finally you can add devices as "new" ones to rebuild back to full redundancy. (Fix your timeouts before attempting the latter.) 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
