On Saturday September 2, josh@xxxxxxxxxxx wrote: > > Attempting to build a new raid5 md array across 4 hard drives. At the > exact moment that the drive finishes rebuilding, the superblock checksum > changes to an invalid value. During the rebuild, mdadm -E for the 4 > drives shows: > > Checksum : 70c0863a - correct > Checksum : 70c0864c - correct > Checksum : 70c0865e - correct > Checksum : 70c08670 - correct > > The instant it finishes: > > Checksum : 70c0bc47 - expected 70c0bc27 > Checksum : 70c0bc59 - expected 70c0bc39 > Checksum : 70c0bc6b - expected 70c0bc4b > Checksum : 70c0bc7d - expected 70c0bc5d > > Kernel is 2.6.17.11. Very odd. It this repeatable? Does the checksum stay wrong? i.e. if you run 'mdadm -E' again, a few seconds later, does it still report the wrong number? If you stop the array and run 'mdadm -E' on the drives, what values do they have now. NeilBrown -- VGER BF report: U 0.5 - 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
