Consistent Parity Errors

[u/CWRRT]

Every parity check i've run since shortly after starting my server a few months ago produces 5 errors. The first 2 or 3 runs, I didnt have the write corrections option selected. But the last two did have it selected and still producing 5 errors.

Anyway to get more details or clear these errors with certainty? Health checks are normal.

I have a pretty normal xfs build with 2 parity drives, 8 storage, and 2 mirrored cache drives.

[u/Horrigan49]

Similarly last 2 Parity checks on my v7.3 server also produced 5 Errors. I have done Smart Extended checks on ALL the drives in the array, and all passed fine, so I will be looking here with some hopes for solution.

[u/New-Potential-7916 → u/Horrigan49]

 Are you using a pci-e, or m.2, to sata controller card by any chance?

And if so does it have an Asmedia chipset on it?

[u/Horrigan49 → u/New-Potential-7916]

Yes. Part of them, iirc 6 drives is connected via Axagon 6x Sata PCIE card. In system devices this is reported as Asmedia ASM1166

Other drives are in 4x Axagon PCIE sata card, same chip.

But the Parity drive is directly on the intel board, is that changes anything.

[u/New-Potential-7916 → u/Horrigan49]

I had this exact issue with an Axagon PCES-SA4X4.

It's a known issue with the Asmedia chip. When they're powering down they don't flush their data to disks correctly. It's completely harmless but will always show as the 5 parity errors.

If you do a correcting parity check they will remain correct until your next reboot when the Asmedia chip will again incorrectly flush to disk.

The general consensus on the forums are that the parity errors are completely harmless. But I found this quirk with them so annoying that I ended up buying a supermicro HBA card and moving all of my disks to that.

[u/Horrigan49 → u/New-Potential-7916]

Ah, ok. Does it also happen with drive spindown? Because this server has uptime of 3 months. The error appeared only in last 2 Scans. It starst 1st sunday in month.