On Wednesday July 10, danci@agenda.si wrote: > OK, it's all attached. One file contains results of mdadm --examine, the > other is what I get on the screen with mdadm --assemble (w/wo --run)... Hmmm. Yes --force isn't doing all that it should do. I'll have to look into that. You should be able to use create successfully. If the original order was b2,c2,a2, which is what the --examine suggests, and you want to not use b2, then mdadm --create /dev/md1 -l5 -c32 -n3 missing /dev/sdc2 /dev/sda2 should work. It will not start a rebuild so you can mount it read-only and if something was wrong, you can "mdadm --stop" and try again with a different arrangement of drives. If b2 and c2 are really the most recent, as it appears, then you might want to use those: mdadm --create /dev/md1 -l5 -c32 -n3 /dev/sdb2 /dev/sdc2 missing Again, this wont do a resync and as long as you don't touch the bad block on b2, you should be able to access data. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
