hanzo

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!

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. 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

Just incase others have a similar issue. This worked for me: Delete /boot/config/network.cfg Reboot This will reset the network configuration of the server and obtain an IP via DHCP. Reapply your network configuration.

Hello, For some strange reason, I am getting very slow uploads from MacOS Transmit via SFTP to my UNRAID 6.12.8 server. The system used to upload at a decent speed but not anymore. I've tried disabling the Docker service but the uploads remain slow.

I have a shell script which I would like to run as a daemon/service. I had a look at the User Scripts plugin and whilst it can run the script. I cannot stop/restart the script. #!/bin/bash cd /root/myapp if pgrep -x "/root/myapp/./app" > /dev/null then echo "Already running" else echo "Not running. Starting..." /root/myapp/./app fi Is it possible to do something like this in UNRAID? # service myapp start # service myapp stop # service myapp restart # service myapp start # systemctl start myapp # systemctl stop myapp # systemctl restart myapp # systemctl status myapp Thanks.