Description
While I was reading up on parity checks I believe this part needs some work:
By default, if an error is found during a Parity-check the parity disk will be updated (written) with the computed data and the Sync Errors counter will be incremented. If you wish to run purely a check without writing correction, uncheck the checkbox that says Write corrections to parity before starting the check. In this mode, parity errors will be notated but not actually fixed during the check operation.
It's a very technical way to explain something to the average user and it does not really explain why one should run a parity check, the dangers of doing so and if a parity check is necessary at all.
The information seems to imply that a parity check can fix problems. Using words like "correction" and "fixed" is a bit of a misnomer/confusing if all the parity check really does is to update the parity disk to whatever the array disk has.
The information should include some warning to the user that running a parity check could potentially be destructive if the array disk contains an error - because the error will be written to the parity. From this point on there is really no way back.
At least a common myth and popular belief seems to be that running a parity check will correct corrupted files on the array.
I have seen again and again that people run parity checks frequently because they think it is good practice in general.