October 1, 201114 yr The last two months I've gotten 10 parity errors almost immediately (15s) after the check starts. Everything else seems to run just fine. Just curious if there is some underlying problem or something I need to do: Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18248 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18256 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18264 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18360 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18368 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 19680 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 19688 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 34768 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 36216 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 36416 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18248 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18256 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18264 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18360 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18368 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 19680 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 19688 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 34768 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 36216 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 36416 (Errors)
October 2, 201114 yr The last two months I've gotten 10 parity errors almost immediately (15s) after the check starts. Everything else seems to run just fine. Just curious if there is some underlying problem or something I need to do: Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18248 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18256 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18264 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18360 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 18368 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 19680 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 19688 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 34768 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 36216 (Errors) Sep 1 00:00:15 YASS kernel: md: parity incorrect: 36416 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18248 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18256 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18264 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18360 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 18368 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 19680 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 19688 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 34768 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 36216 (Errors) Oct 1 00:00:15 YASS kernel: md: parity incorrect: 36416 (Errors) Run memtest at least overnight, if not for 24 hours
October 2, 201114 yr Have you run a correcting parity check? It looks like you are just seeing the results of the monthly scheduled non-correcting parity check. Until you tell it to correct the errors, they will always stay there. The fact that the errors appear to have stayed the same from one month to the next probably means everything is ok. Manually force a correcting parity run, then do a non-correcting run and see if the errors are still there.
Archived
This topic is now archived and is closed to further replies.