- Minor
A Parity Check, with enabled "corrections" will start as a "Non-Correcting Parity-Check":
Jan 2 00:00:07 Unraid-1 kernel: mdcmd (62): check NOCORRECT
Jan 2 00:00:07 Unraid-1 kernel:
Jan 2 00:00:07 Unraid-1 kernel: md: recovery thread: check P ...
[...]
Jan 2 00:00:14 Unraid-1 Plugin Auto Update: Community Applications Plugin Auto Update finished
Jan 2 00:00:17 Unraid-1 Parity Check Tuning: Scheduled Non-Correcting Parity-Check finished (0 errors)
Jan 2 00:00:17 Unraid-1 Parity Check Tuning: Elapsed Time 10 sec, Runtime 10 sec, Increments 1, Average Speed 1.0 TB/s
Jan 2 00:00:17 Unraid-1 Parity Check Tuning: Send notification: Scheduled Non-Correcting Parity-Check finished (0 errors): Elapsed Time 10 sec, Runtime 10 sec, Increments 1, Average Speed 1.0 TB/s (type=normal link=/Settings/Scheduler)
[...]
Jan 2 00:17:35 Unraid-1 Parity Check Tuning: Manual Non-Correcting Parity-Check: Manually resumed
[...]
Jan 2 01:41:34 Unraid-1 kernel: md: recovery thread: P incorrect, sector=2353004440
Jan 2 01:41:34 Unraid-1 kernel: md: recovery thread: P incorrect, sector=2353004472
idk why the parity checks stopps after 10 seconds and starts again by the plugin, but in log you can see, that the inital start was a "non-correction" one.