[6.9.2] Parity checking scheduling not working

You should provide a copy of your diagnostics so we can get a better idea of what happened.   It would also be a good idea to provide a copy of /etc/cron.d/root so we can see how the schedule has been set.

 

BTW:  It is normally recommended that scheduled checks are set to be non-correcting.   

@itimpi

I have attached the diagnostics - nightowl-diagnostics-20220101-1422.zip

 

this is the content of cron:

# Generated parity check schedule:
30 2 1 12 * /usr/local/sbin/mdcmd check  &> /dev/null || :

@itimpi

it is safe this to modify this file directly - /etc/cron.d/root?

Jan  1 08:22:21 NightOwl emhttpd: unclean shutdown detected

 

That cron setting is correct that's listed

 

Dec 1st @ 2:30 am

 

Since it's correct, and it's running at random times, it would appear that your system is randomly rebooting. (Confirmed by your diagnostics)  Maybe the system event log in the BIOS would shed some light on what's going on.

Changed Status to Closed

26 minutes ago, Squid said:

Jan  1 08:22:21 NightOwl emhttpd: unclean shutdown detected

 

That cron setting is correct that's listed

 

Dec 1st @ 2:30 am

 

Since it's correct, and it's running at random times, it would appear that your system is randomly rebooting. (Confirmed by your diagnostics)  Maybe the system event log in the BIOS would shed some light on what's going on.

 I didn't shutdown my machine. Its running 24x7. That's the reason  the parity check was triggered?

Yes

42 minutes ago, Squid said:

Yes

@Squid

I know the reason. Just now we have  experience a brownout; it happens only a few seconds. Just now parity checking is running. During that time around 08:22:21AM , I didn't know we have a power outage and I was sleeping. Thanks to all. I need to protect my server with UPS since occasionally brownout occurs in my place.

Edited January 1, 2022 by altyne