- Minor
Hello,
I'm running unRaid 6.7.2 Stable.
I've noticed a problem with the parity check scheduler not functioning properly.
Its currently set to run a check monthly. However, the parity check runs every Sunday morning and I get a report emailed. Its always been running every Sunday even though its set to monthly, so this is not a new problem. Just reporting it now.
eg: The parity check was supposed to run on Nov 1, as configured in scheduler, but didn't. Instead, it ran on Sunday, Nov 3 (and every Sunday), which is the built-in default.
n3supernas-diagnostics-20191106-2307.zip
cron file:
# Generated docker monitoring schedule: 10 0 1 * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php 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: 0 2 1 * * /usr/local/sbin/mdcmd check &> /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