I have a parity check scheduled every 3 months.  It started normal and finished without any errors but to find out the next day that parity check is running again.  I didn't manually start the second one, nor the system rebooted. Could it be a bug or something else?

See attached diagnostic file

nas-unraid-bkp-diagnostics-20211102-0920.zip

Edited November 5, 20214 yr by johnwhicker

So both of unraids performed the same way which is strange. I have a schedule setup for every 3 months.  The November one kicked normally and as per my initial post the second unraid started a second parity check out of nowhere.  As I was monitoring the first unraid to finish the scheduled parity check and I noticed after it finished, the schedule show to start another scheduled parity check in 2 hours.  That's very strange. So something messed up with the schedule?  I disabled and redone the schedule again and hope this won't happen again?

 

Anyone seen this strange parity schedule behavior?

Was end of daylight savings time involved?

2 hours ago, trurl said:

Was end of daylight savings time involved?

Thank you Sir.  How do I check that please?  It could I guess

Did daylight saving time end in your location?

 

 

Yes indeed, that could be it.  It ended first Sunday of Nov for CST

1 hour ago, johnwhicker said:

It ended first Sunday of Nov for CST

First Sunday of Nov hasn't happened yet, Sunday was Oct 31. In US we don't fall back until this coming Sunday Nov 7, 2AM.

1 hour ago, trurl said:

First Sunday of Nov hasn't happened yet, Sunday was Oct 31. In US we don't fall back until this coming Sunday Nov 7, 2AM.

 

Doooh So what was it then?  The strangest thing and it happened on both of my unraids which have same schedule.

What do you get from the command line with this?

cat /etc/cron.d/root

 

3 hours ago, trurl said:

What do you get from the command line with this?

cat /etc/cron.d/root

 

 

I got this?   

 

,_     _
 |\\_,-~/
 / _  _ |    ,--.
(  @  @ )   / ,-'
 \  _T_/-._( (
 /         `. \
|         _  \ |
 \ \ ,  /      |
  || |-_\__   /
 ((_/`(____,-'

 

Kidding

 

 

root@NAS-UNRAID:~# cat /etc/cron.d/root

# 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 0 * 2,6,10 * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null || :

 

# Generated array status check schedule:

20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

 

# Generated Unraid OS update check schedule:

11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null

 

# Generated cron settings for docker autoupdates

0 11 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1

# Generated cron settings for plugin autoupdates

0 2 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1

 

# CRON for CA background scanning of applications

33 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1

 

# Generated file integrity check schedule:

0 0 * * 0 bash /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null

 

# Generated ssd trim schedule:

0 0 * * * /sbin/fstrim -a -v | logger &> /dev/null

 

# Generated system data collection schedule:

*/1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

 

And same on my second unraid box:

 

oot@NAS-UNRAID-BKP:~# cat /etc/cron.d/root

# Generated system monitoring schedule:

*/1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

# Generated mover schedule:

30 3 * * * /usr/local/sbin/mover &> /dev/null

 

# Generated parity check schedule:

0 0 * 2,6,10 * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null || :

 

# Generated array status check schedule:

20 0 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null

 

# Generated Unraid OS update check schedule:

11 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null

 

# Generated cron settings for docker autoupdates

0 11 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1

# Generated cron settings for plugin autoupdates

0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1

 

# CRON for CA background scanning of applications

35 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1

 

# Generated file integrity check schedule:

0 0 * * 0 bash /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null

 

# Generated ssd trim schedule:

0 0 * * * /sbin/fstrim -a -v | logger &> /dev/null

 

# Generated system data collection schedule:

*/1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

Edited November 5, 20214 yr by johnwhicker

post a screenshot of your settings, scheduler, parity check section.

Attached Sir

 

 

Edited November 5, 20214 yr by johnwhicker

10 hours ago, johnwhicker said:

# Generated parity check schedule:

0 0 * 2,6,10 *

 

Is that a custom entry? (I see it is) When did you set this up? Seems like it would have been running every day in Oct.

 

http://corntab.com/?c=0_0_*_2,6,10_*

 

Quote

At 00 minutes past 0:00 on every day in Feb, Jun, and Oct

 

2 minutes ago, trurl said:

 

Is that a custom entry?

 

http://corntab.com/?c=0_0_*_2,6,10_*

 

 

Correct, is custom and is every 3 months or so.

1 minute ago, johnwhicker said:

Correct, is custom and is every 3 months or so.

Not what that entry says   it means run it every day during the 3 selected months.    You need to constrain it to a specified day within those 3 months.

2 minutes ago, johnwhicker said:

Correct, is custom and is every 3 months or so.

As noted, it is every day on 3 specific months

Hmm, SNAP.   I think it was like this the entire time and it worked ok. I will change it right now   Thanks much