bug in UI and parity check

Adding some more details:

-non correcting check works correctly after first array start (with auto-start enable or disable)

-the firs parity check after stopping and re-starting the array is always correct, even if you uncheck the "write corrections" box, if you cancel and run another one (without stopping the array) it works correctly.

Urgent?

Missed that, changing to minor which seems the most appropriate.

On 8/14/2020 at 12:33 PM, bonienl said:

Urgent?

Initially, I labeled it minor. But then I read the label descriptions, and this bug does indeed lead to data loss, with a real life example.  And in any case, writing to the disks when it is not supposed to write anything, that's not something minor. 

Edited August 15, 2020 by Pourko
typo

And how is it that when I do a read-only parity check and it finds errors, the UI still shows "Parity is valid"?