Neil Brown wrote: > > Weird... > > What version of mdadm? > > Can you show us "mdadm --examine" of a couple of devices? > > Any kernel logs while this is happening? > I just got the LATEST off of your website, whatever the number was. I got the array running, i noticed that in the dmesg from booting it said something about "kicking non-fresh drive sdxyz" so I did a --assemble --scan --force and then re-added the final drive which got the array back to syncing. I would have prefered not to resync but whatever. The strange thing is how they came to be non-fresh, these were the drives that had changed controller. They were always there and I never did anything to the array apart from trying to assemble it. If I try to assemble an array and it can only find part of the devices, do those devices that are found have their superblocks updated before the assemble is rejected? If that's the case and I try again, the missing drives will be "non-fresh" even though nothing was ever done. That's the only cause I can imagine... cheers, /Patrik - 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
