summaryrefslogtreecommitdiffstats
path: root/health/guides/mdstat/mdstat_mismatch_cnt.md
blob: 7a156e38f71f02981b6e6cc0779e0d3a79d54fd0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
### Understand the alert

This alert presents the number of unsynchronized blocks for the RAID array in crisis. Receiving this alert indicates a high number of unsynchronized blocks for the RAID array.  This might indicate that data on the array is corrupted.

This alert is raised to warning when the metric exceeds 1024 unsynchronized blocks.

### Troubleshoot the alert

There is no standard approach to troubleshooting this alert because the reasons can be various. 

For example, one of the reasons might be a swap on the array, which is relatively harmless. However, this alert can also be triggered by hardware issues which can lead to many problems and inconsistencies between the disks. 

### Useful resources

[Serverfault | Reasons for high mismatch_cnt on a RAID1/10 array](https://serverfault.com/questions/885565/what-are-raid-1-10-mismatch-cnt-0-causes-except-for-swap-file/885574#885574)