# tracking parity mismatches to a failing disk

- List: linux-raid
- 2 messages, 2 authors
- Page: https://ratatoskr.run/linux-raid/2012/05/6620005/t

## tracking parity mismatches to a failing disk

- From: Michael Peterson \<hidden\>
- Date: 2012-05-09 19:16:08 
- Message: https://ratatoskr.run/linux-raid/2012/05/6620005.md

```text
I'm trying to identify the source of a non-zero mismatch_cnt on a
six-disk RAID6 md array.  I think I've identified it as /dev/sdf since
that is the only device with a non-zero value in
/sys/block/md0/md/dev-sd*/errors.  Is that the right way to track parity
mismatches back to a disk?

OS is CentOS 5.8 -> mdadm 2.6.9

Thanks,
Michael
```

## Re: tracking parity mismatches to a failing disk

- From: NeilBrown \<hidden\>
- Date: 2012-06-04 04:17:04 
- Message: https://ratatoskr.run/linux-raid/2012/06/6620432.md

```text
On Wed, 09 May 2012 15:16:08 -0400 Michael Peterson
[ref] wrote:

> I'm trying to identify the source of a non-zero mismatch_cnt on a
> six-disk RAID6 md array.  I think I've identified it as /dev/sdf since
> that is the only device with a non-zero value in
> /sys/block/md0/md/dev-sd*/errors.  Is that the right way to track parity
> mismatches back to a disk?
> 
> OS is CentOS 5.8 -> mdadm 2.6.9

There is a program in the mdadm source distro called "raid6check" which can
possibly help you.

NeilBrown
```
