On one of my LimeTech systems a parity check "non correrctional" is currently running. The system was rebootet right before starting the parity check. There was no activity before starting the parity check.

 

If you look at the read values shown in the screen shot, they start from 4.9 million and end on 11.8 million reads. Parity check is currently on 36%.

 

I thought that the read values should be equal - more or less.

 

Is there something wrong with my system?

 

Thanks in advance.

 

P.S.: System is unRAID 5.0.6

This came up in another thread recently. I won't go looking for it, but long story short is that it is normal. If the error column is all zeroes your good.

On one of my LimeTech systems a parity check "non correrctional" is currently running. The system was rebootet right before starting the parity check. There was no activity before starting the parity check.

 

 

unless you cleared the counters right before the parity check, the values will be out of sync.

 

The mere act of mounting files systems causes reads of various values to be in the counters.

Then there is the housekeeping that occurs for any journal or superblock updates.

All devices did report two-digit values when I did start the parity check. Counters where under 100.

 

Parity check is over now - reporting 0 errors.

 

The difference of reads on the 3TB drives (same type) is between 6.9 million reads and 16.2 million reads. This is something I do not understand and that makes me nervous.

 

What is counted? Simply unRAIDs read requests - that does not explain the huge difference? Or the number of tries that where neccessary to fetch a value because of somehow bad disks?

 

 

This might be a factor of drives on different controllers and buffering.

On my HP Microserver all values are the same at the end of the parity check. All drives are on one controller and all models are the same.

This might be a factor of drives on different controllers and buffering.

On my HP Microserver all values are the same at the end of the parity check. All drives are on one controller and all models are the same.

I have certainly seen the values vary with different disk models on the same controller, or alternatively with the same disk model on different controllers.  It also seems it can vary with firmware version number I believe.