Jim Paris wrote:
[]
Weird: /dev/sdc2 has both a 0.90 and 1.0 superblock. I guess that's
the problem. How would that have happened? mdadm --create over an
existing device without a --zero-superblock inbetween, I suppose?
I wonder why it was never a problem before. For the root, only
/dev/sda2 and /dev/sdb2 are necessary. Maybe 2.6.30 changed the disk
order, or the ordering of /proc/partitions, such that mdadm now
examines this bad disk before the array is fully assembled, whereas it
never needed to scan it before?
2.6.30 turned on "fastboot" option by default -- it's when
all disks/controllers gets scanned in parallel.
/mjt
--
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
