On Donnerstag 19 Februar 2009, Arnau Bria wrote: > Hi all, > > after a reboot (my machine was up for more than 6 months) I saw my raid > with only one of two devices used, and I had to read the second > partioition: > > #mdadm --manage /dev/md1 --add /dev/hda1 > mdadm: re-added /dev/hda1 > > # cat /proc/mdstat > Personalities : [raid1] [multipath] [faulty] > md1 : active raid1 hda1[2] hdc1[1] > 29302464 blocks [2/1] [_U] > [>....................] recovery = 2.8% (846976/29302464) > finish=19.9min speed=23731K/sec > > > Looking at dmes I saw this message: > > > raid1: raid set md2 active with 1 out of 2 mirrors > md: considering hdc1 ... > md: adding hdc1 ... > md: adding hda1 ... > md: created md1 > md: bind<hda1> > md: bind<hdc1> > md: running: <hdc1><hda1> > md: kicking non-fresh hda1 from array! > md: unbind<hda1> > md: export_rdev(hda1) > raid1: raid set md1 active with 1 out of 2 mirrors > md: ... autorun DONE. > > so, seems that hda1 was out of sync... is this the meaning? > How could it happen? cause mdadm did not send any email about my raid > status....
maybe your last shutdown was not really clean - and the disk had not enough time to flush its cache completly. Possible explaination: hd with big cache, ext3, a bit too fast to turn off at shutdown.
