My understanding is that if the parity-check completes with zero errors, the system will kick off the next parity-check at the next configured Schedule in the Settings.

 

My server has run parity-checks three times in a row (with a few seconds pause) and each parity-check resulted with zero errors. The system has not rebooted and the array has not stopped or started.

 

All drives are green with zero errors.

Quote

 

6 March 2024 at 1:06:01 pm AEDT

Event: Unraid Parity-Check

Subject: Notice [TOWER] - Parity-Check finished (0 errors) Description: Duration: 7 hours, 32 minutes, 57 seconds. Average speed: 110.4 MB/s Importance: normal 6

 

March 2024 at 1:07:01 pm AEDT

Event: Unraid Parity-Check

Subject: Notice [TOWER] - Parity-Check started

Description: Size: 3 TB Importance: warning

 

 

I cannot explain. Do I let UNRAID keep doing it's thing until this stops?

 

UPDATE:  SMART short self tests on all drives completed without errors.

 

 

Attached are the diagnostics.

 

Thanks.

tower-diagnostics-20240306-1459.zip

Edited March 6, 20242 yr by hanzo

Are you sure you have the schedule set correctly?   Perhaps a screenshot of the scheduling page might help as the syslog in the diagnostics suggests it could be wrong.

 

Also the output of the following command will allow us to check the schedule:

cat /etc/cron.d/root

 

 

Thank you for the suggestions. 

Please find attached the screenshots from the Scheduler. 

Also below is the output from cron:

 

root@Tower:~# cat /etc/cron.d/root
# Generated docker monitoring schedule:
10 0 * * 1 /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate check &> /dev/null

# Generated system monitoring schedule:
*/1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

# Generated mover schedule:
40 3 * * * /usr/local/sbin/mover &> /dev/null

# Generated parity check schedule:
* * * * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null
# Generated plugins version check schedule:
10 0 * * 1 /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null

# Generated array status check schedule:
20 0 * * 1 /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

# Generated Unraid OS update check schedule:
11 0 1 * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null


# CRON for CA background scanning of applications
30 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1

# Generated schedules for parity.check.tuning
15 0 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null
30 7 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null
*/17 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null

 

From the cron job I noticed one of the jobs show run all the time:

 

# Generated parity check schedule:
* * * * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null

 

Would it this be this?

UPDATE: I changed the Parity Check to Disable, re-checked /etc/cron.d/root, the entry disappeared.  I re-enabled Parity Check to Monthly and it looks correct now.

 

# Generated parity check schedule:
0 0 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null

 

I'll wait till the current Parity Check completes to confirm if this worked.

 

Thank you for pointing me in the right direction on where to look!

 

Edited March 6, 20242 yr by hanzo
Updated info

2 hours ago, hanzo said:

 

# Generated parity check schedule:
* * * * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null

 

Would it this be this?

Yes - that means start a scheduled parity check every minute of every day!    Not sure how it got like that.