967841513 Parity Errors

[Falloutman]

Below is the history from my monthly parity checks. Ever since I replaced my Parity Drive with a 14tb, this is a monthly issue whenever the scan runs.  Where do I start?

 

 

Date	Duration	Speed	Status	Errors	Elapsed Time	Increments	Type
2021-02-03, 10:41:17	1 day, 12 hr, 13 min, 33 sec	107.4 MB/s	OK	967841513	Unknown	Unavailable	
2020-12-28, 09:46:17	1 min, 28 sec	Unavailable	Canceled	0	Unknown	Unavailable	
2020-12-26, 02:10:08	1 day, 6 hr, 33 min, 15 sec	127.3 MB/s	OK	967841513	Unknown	Unavailable	
2 day, 13 hr, 29 min, 28 sec	1	OK		Unknown	Unavailable	
2020-12-06, 02:16:18	2 day, 13 hr, 29 min, 28 sec	63.2 MB/s	OK	967841513	Unknown	Unavailable	
13 min, 34 sec	1	OK		Unknown	Unavailable	
2020-12-04, 12:12:47	13 min, 34 sec	17.2 GB/s	Canceled	8485997	Unknown	Unavailable	
2020-12-04, 12:02:37	25 sec	Unavailable	Canceled	383899	Unknown	Unavailable	
2020-12-03, 22:28:24	1 day, 22 hr, 19 min, 24 sec	84.0 MB/s	OK	0	1 day, 22 hr, 19 min, 24 sec	1	Correcting
2020-12-02, 17:35:19	2 day, 8 hr, 23 min, 52 sec	69.0 MB/s	OK	0	2 day, 8 hr, 23 min, 52 sec	1	Non-Correcting
2020-12-01, 10:11:24	20 hr, 22 min, 46 sec	54.5 MB/s	OK	0	20 hr, 22 min, 46 sec	1	Correcting
2020-11-01, 09:12:41	20 hr, 25 min, 18 sec	54.4 MB/s	OK	0	20 hr, 25 min, 18 sec	1	Non-Correcting
2020-10-01, 10:12:25	10 hr, 12 min, 24 sec	108.9 MB/s	OK	0	10 hr, 12 min, 24 sec	1	Correcting
11 hr, 18 min, 39 sec	1	OK		
2020-09-01, 11:18:40	11 hr, 18 min, 39 sec	98.3 MB/s	OK	11	
2020-08-14, 08:46:05	10 hr, 33 min, 28 sec	105.3 MB/s	OK	11	
2020-08-07, 21:51:01	10 hr, 59 min, 14 sec	101.1 MB/s	OK	11	
2020-08-04, 21:41:34	10 hr, 36 min, 58 sec	104.7 MB/s	OK	11	
2020-08-04, 00:40:40	11 hr, 46 min, 33 sec	94.4 MB/s	OK	19

 

tower-diagnostics-20210209-0938.zip

Edited February 9, 2021 by Falloutman
Adding diagnostics

[itimpi]

Not quite sure what question you are asking?   

 

If it is the very large value in the Errors column then this might be due to the part of the parity drive beyond the size of the previous one not being correctly zeroed by Unraid when the new one was added (there have been reports of this happening).   These errors would keep being reported until you run a correcting check after which the count should return to zero for subsequent runs.

 

If you use the History button on the Main tab that data will be better formatted   

 

The entries with the extra fields are ones where you have had the Parity Check Tuning plugin active and it has added to the entry with information it has gathered. 

[Falloutman]

2 minutes ago, itimpi said:

Not quite sure what question you are asking?   

 

If it is the very large value in the Errors column then this might be due to the part of the parity drive beyond the size of the previous one not being correctly zeroed by Unraid when the new one was added (there have been reports of this happening).   These errors would keep being reported until you run a correcting check after which the count should return to zero for subsequent runs.

 

If you use the History button on the Main tab that data will be better formatted   

 

The entries with the extra fields are ones where you have had the Parity Check Tuning plugin active and it has added to the entry with information it has gathered. 

More or less just trying to figure out why these errors would occur.  I have these errors corrected automatically while the Parity check is running but it keeps coming back.  Took a quick screenshot to help with the formatting.  

[itimpi]

Are you sure it is a correcting check?  Without the extra information added by the Parity Check Tuning plugin one cannot tell from the history.

 

It might be possible to tell if you attach your systems diagnostics zip file (obtained via Tools->Diagnostics) to your NEXT post covering a period where this has happened.