Parity errors

version:

version: 5.0-beta6a

I've run a no correct parity check three times and get a parity error at the very first of the run.  I only get the one, but curious as to how to tell if I should correct parity or not.

syslog:

upon boot up I see:

May 18 08:11:22 Tower kernel: REISERFS (device md5): checking transaction log (md5) (Routine)

May 18 08:11:22 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal (Routine)

May 18 08:11:22 Tower kernel: REISERFS (device md1): using ordered data mode (Routine)

May 18 08:11:22 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal (Routine)

May 18 08:11:22 Tower kernel: REISERFS (device md2): using ordered data mode (Routine)

May 18 08:11:22 Tower kernel: md: parity incorrect: 128 (Errors)

May 18 08:11:22 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal (Routine)

May 18 08:11:22 Tower kernel: REISERFS (device md3): using ordered data mode (Routine)

When I manually run check I see:

May 18 16:08:10 Tower kernel: mdcmd (48): check NOCORRECT (unRAID engine)

May 18 16:08:10 Tower kernel: md: recovery thread woken up ... (unRAID engine)

May 18 16:08:10 Tower kernel: md: recovery thread checking parity... (unRAID engine)

May 18 16:08:11 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. (unRAID engine)

May 18 16:08:22 Tower kernel: md: parity incorrect: 128 (Errors)

May 18 16:19:02 Tower kernel: mdcmd (50): check NOCORRECT (unRAID engine)

May 18 16:19:02 Tower kernel: md: recovery thread woken up ... (unRAID engine)

May 18 16:19:02 Tower kernel: md: recovery thread checking parity... (unRAID engine)

May 18 16:19:02 Tower kernel: md: using 1152k window, over a total of 976762552 blocks. (unRAID engine)

May 18 16:19:02 Tower kernel: md: parity incorrect: 128 (Errors)

Suggestions?

thanks,

dave