Jarlehm

# Generated btrfs balance cache schedule: 0 7 15 * * /usr/local/emhttp/plugins/dynamix/scripts/btrfs_balance start /mnt/cache -dusage=50 &> /dev/null # Generated docker monitoring schedule: 10 0 * * * /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: 0 7 1 * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 30 5 * 1,4,7,10 2 [[ $(date +%e) -le 7 ]] && /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated TRIM schedule: 0 8 * * 1 /usr/local/emhttp/plugins/dynamix/scripts/ssd_trim cron|logger &> /dev/null # Generated array status check schedule: 20 0,12 * * * /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 # Appdata.Backup cron settings 10 08 * * 1 php /usr/local/emhttp/plugins/appdata.backup/scripts/backup.php > /dev/null 2>&1 # Generated cron settings for docker autoupdates 0 6 * * 1 /usr/local/emhttp/plugins/ca.update.applications/scripts/updateDocker.php >/dev/null 2>&1 # Generated cron settings for plugin autoupdates 0 6 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # CRON for CA background scanning of applications 17 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 # Generated file integrity check schedule: 0 8 15 * * bash /boot/config/plugins/dynamix.file.integrity/integrity-check.sh &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null # Purge recycle bin at 5:00 AM on the first day of the week: 0 5 * * 0 /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin cron &> /dev/null # Refresh Recycle Bin trash sizes every five minutes: */5 * * * * /usr/local/emhttp/plugins/recycle.bin/scripts/get_trashsizes &> /dev/null "Normal" mover should just run once a month.

So, I've notices for a while that all of my drives spin up every night at 4:40am. Not the end of the world, but I'm a concert photographer and often still working then and find it kinda annoying. I've been trying to figure out what may cause it for a while (turning off dockers, going through settings, etc.), but been unable to pinpoint it. I've used the "File Activity" plugin to see if that could reveal something, but nothing is really going on at that moment. Just now I installed the "Dynamix Schedules" plugin, and think I may be on to something. Under "Fixed Schedules" I see a daily schedule at 4:40am with the scheduled tasks "exportrotate, fix.common.problems.sh, logrotate" running. I thought "Fix Common Problems" was the culprit, but that was already set to "Skip tests on spun down disks". I can't quite figure out what the other two tasks are, but given the timing, I assume something is going on there. I'm not 100% sure, but I feel like this started to occur after I installed the "Unraid Patch" a few weeks ago. Currently running 6.12.13, by the way.

I wouldn't claim to be sure of any thing😅 If there is some way for me to mess it up, it is definitely possible, but as far as I can recall, I haven't changed anything about how it runs except the schedule. The previous parity check also had some errors (around 600), so I guess something isn't right. The memtest is still running without any errors, by the way.

Memtest has been running for almost 17 hours now (9 passes). No errors thus far. Is that long enough? Since the RAM doesn't appear to be the issue, what would be the next suspect to check out?

Ah... I was minutes from pulling the trigger on new RAM, there. My motherboard doesn't support it. Guess that's an upgrade I should invest in down the line. Thanks itimpi! I'll run the memtest now and see how it goes.

Thanks JorgeB, I'll look into that. Haven't heard of ECC RAM before, but from what I can gather, it's probably better to change the RAM I already have to ECC regardless?

Hi all! For the last couple of parity checks I've been getting errors. I'm suspecting two older 8tb drives in the system, but I can't figure out which drive (if any?) is giving the errors. My box has been running fine for about 18 months. I was going to expand the storage anyway with a new 16tb drive, currently waiting for at the post office, but it might be better to replace one of the old drives with the new one? torchwood-diagnostics-20221002-1242.zip