Dear team,

 

the last Parity-Check discovered several errors, so I started an Parity-Check with ticked correct errors.

It is running smooth, nearly finished an did not correct any errors yet. However, I now realized that the Parity-Check is running only on one disk, the other is spun down. Capacity of the array is also bigger than show in the Parity-Check information.

Is there something wrong?

 

 

Edited September 6, 20214 yr by matty2k

It's normal since the other disk is smaller, parity check for that one ended at the 8TB mark.

 

2 minutes ago, matty2k said:

Capacity of the array is also bigger than show in the Parity-Check information.

Total size refers to parity size.

After finishing the Parity-Check with ticked "write corrections to disk" I am wondering why 0 corrections have been corrected since the Parity-Check before found >500 errors?

The last test finished with 0 errors ... confused .. 

That suggests the previous one was also correct.

19 minutes ago, matty2k said:

After finishing the Parity-Check with ticked "write corrections to disk" I am wondering why 0 corrections have been corrected since the Parity-Check before found >500 errors?

The last test finished with 0 errors ... confused .. 

The check includes "corrections" in its error count   Once you have any genuine parity errors you should expect the next correcting check to report them as errors but then fix them.

 

Tip:  If you have the Parity Check Tuning plugin installed then one of its not so obvious features is to enhance the parity history to indicate what type 

of check was run for each entry.

 

OK. Thank`s. Will try that too.

BR