Kiyan Azarbar wrote:
> hdd2's event counter: 0000000b
> hdc2's event counter: 00000001
> hdb2's event counter: 0000000b
> md: superblock update time inconsistency -- using the most recent one
> freshest: hdd2
> md: kicking non-fresh hdc2 from array!
This is indicative of a RAID5 array that was not shut down properly. In
most cases, this should automatically recover by using the kicked, non-fresh
drive for reconstruction. However, it won't automatically do that if the
system goes down while it's trying to reconstruct the parity drive.
raidhotadd /dev/md1 /dev/hdc2
should get you reconstructing/working again.
Tom
