Koozali.org: home of the SME Server
Obsolete Releases => SME Server 8.x => Topic started by: azche24 on October 22, 2012, 10:17:17 AM
-
Hi all,
for documentation purposes i'd like to describe my solution for an annoying error message. Every week at 4:22 am my SME 8.0 dropped the following error-mail:
A RebuildFinished event has been detected on md device /dev/md1.
Device mismatches found: 128 is now an active member of md device /dev/md1.
The RAID1 seemed to be okay. Messages continued after changing disks. First hint was in Charlie Brady's post at bugzilla http://bugs.contribs.org/show_bug.cgi?id=6160#c7 (http://bugs.contribs.org/show_bug.cgi?id=6160#c7): The system drops an error-message, if drive mismatch count is not 0 for any reason. You just have to reset the drive mismatch count, if the raid is healty. This seems to be quite common on RAID1 systems.
The solution is described here http://www.fractalizer.ru/frpost_350/warning-mismatch_cnt-is-not-0-on-devmd0/#codesyntax_5 (http://www.fractalizer.ru/frpost_350/warning-mismatch_cnt-is-not-0-on-devmd0/#codesyntax_5); you reset the drive mismatch counter and check it with these commands (md1 was my mismatched boot-array):
cat /sys/block/md1/md/mismatch_cnt
echo repair >/sys/block/md1/md/sync_action
echo check >/sys/block/md1/md/sync_action
watch cat /proc/mdstat
After that issue
cat /sys/block/md1/md/mismatch_cnt
and it says "0". You're done.
-
IMHO this should be posted in bugzilla and, if verified, in the wiki
-
Bug ist closed (nobug). Of course i can post it in the wiki - where?