After Update to 6.9.2 Parity-Check starts itself unperiodly without scheduler set

[Pasadena]

Hi,

I updated my Unraid to 6.9.2. Since that time I saw that Parity-check was running. I have a lot of data, so it takes 2-3 days each time. When it is finished, maybe one day is ok, but then it starts again without reason?

 

The scheduler is off, because I want to start parity check manuel.

I switch off trhe server every day in the evening and start it in morning again. (Not during the parity check, in thisd case I wait until finish!)
any ideas, what I can do?

corntab -l contains:
47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null
#
# Run daily cron jobs at 4:40 every day:
40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null
#
# Run weekly cron jobs at 4:30 on the first day of the week:
30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null
#
# Run monthly cron jobs at 4:20 on the first day of the month:
20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null

cat /etc/cron.d/root contains:

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:
0 */1 * * * /usr/local/sbin/mover &> /dev/null

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

Any Ideas?

Edited May 10, 2021 by Pasadena

[itimpi]

Sounds like you are getting unclean shutdowns.     Have you tried stopping the array before shutdown?   There have been reports that there might be problems with the timeouts for shutting down Docker containers and VMs not being honoured leading to unclean shutdowns, and stopping the array first before doing a shutdown would avoid this happening.

[Pasadena]

I found the solution!

Better I must say: I think, I found the solution.

Under "Disc Settings" in the Settings menu the "Shutdown Time-Out" was set to 60 seconds. Maybe this was to less?

I set ist to 120 seconds now. After the parity-check was finished (maybe tomorrow evening or the day after tomorrow...) I will check it again.

 

 

[itimpi]

2 hours ago, Pasadena said:

I found the solution!

Better I must say: I think, I found the solution.

Under "Disc Settings" in the Settings menu the "Shutdown Time-Out" was set to 60 seconds. Maybe this was to less?

I set ist to 120 seconds now. After the parity-check was finished (maybe tomorrow evening or the day after tomorrow...) I will check it again.

 

 

There are also timeouts for VMs and docker containers if you use those?