On Tue, August 25, 2009 9:08 am, Info@xxxxxxxxxxxxxxx wrote: > > The sync has finally finished, but something's wrong with the first > partition set; Only sda1 is a member of md0. In dmesg I find: > [ 4.756365] md: kicking non-fresh sdb1 from array! > > Huh? If it's not fresh, why doesn't it sync it? What should I do about > this? How did it happen on a new array? You'll need to provide a lot more information, starting with kernel log at all relevant times (and don't use 'grep', just cut out of contiguous section of the log including a few lines before and after anything that might be relevant). And "mdadm -E" of any relevant device. "Kicking non-free sdb1 from arrays" is a message that you get when assembling an array if the metadata on sdb1 is older than the others. This can happen if it was evicted from the array due to failure or if the array was assembled without sdb1 for some reason. There are probably other scenarios. That is why I need to see recent history, including anything from the last time the array was active. NeilBrown -- 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
