Ichthus

Sorry for the cryptic title. Not meant to be clickbait, I just have no idea what is going on. First I started seeing errors from dockers and VMs. Then when I logged in via hostname it looked like a 90s basic HTML site. I was able to log in via the local IP and it looked better, but the log filesystem was full. I was able to reboot, then noticed a bunch of BTRFS errors, read only errors, and a bunch of other funny business. Not sure if a drive is failing, a filesystem is corrupt, or something else. Thanks in advance. unraid-diagnostics-20251010-2315.zip

I am getting the following error: Go to System and initialize a "Force SMART+DB" I've attached my debug file. Any help would be appreciated. disklocation-2025-09-27.log

Doh... my bad... I had the wrong file referenced. All is good now! Thanks again!

I have tested this in the new version and the thresholds seem to be following the global settings now. Thanks! However, I seem to also be having the same issue as others where the mover is still moving files that should be ignored. In light of my previous issues, I'm wondering if this isn't also an issue with the global settings not being applied. My mover ignore script includes: /mnt/buffer/data/usenet /mnt/buffer/data/torrent /mnt/buffer/./data/usenet /mnt/buffer/./data/torrent However I am still getting the following when running mover: Moving "/mnt/buffer/./data/usenet/complete/default/test_download_10GB.1.4/test_download_10GB.bin" to /mnt/user0/

Thanks for working on this fix. I'd love to help test it, but I'm not sure how to install the updated plugin from the link you provided. Again, sorry for my ignorance.

Thank you for the clarification. I believe I have a better grasp of this now. I agree that trying to perfectly balance "cache yes" and "cache prefer" shares might be an overly ambitious goal, given the countless possible scenarios. It’s probably more practical for users to handle this on a case-by-case basis, tailored to their specific needs. I’m currently managing this by keeping my "cache yes" and "cache prefer" in completely separate pools. Regarding the "cache yes" not working as expected (i.e., not picking up the global settings), it seems like this is a recognized issue. Please let me know if I’ve gotten anything wrong. Thanks again for the explanation and all your hard work!

When I add an override to the data share using the same settings as the global configuration, the functionality works as I’d expect. This leaves me wondering about the purpose of the global settings if they don’t automatically apply to cache yes shares without an override. I feel like I might be missing their intended role. I’m also unsure about the plugin’s intended use case if it’s not designed for this exact scenario. I’m not trying to be sarcastic—I genuinely don’t grasp the point. This is precisely how the old plugin functioned for me, so I’m struggling to see the difference. On a related note, my data share is a cache yes share that operates on a separate pool from everything else, so there’s no risk of it consuming space needed for a cache prefer share. Plus, my downloader is configured to pause if the mover falls behind and the pool gets too full.

There's an after mover script as well.

I've been following this thread for a while now but can't seem to make sense of my issue. Here are the settings for my shares: appdata: Cache <- Array backups: Backup <- Array data: Buffer -> Array domains: Cache <- Array isos: Cache -> Array system: Cache <- Array Cache and Backup are both pools. If I understand how this is intended to function correctly, there should be really no difference between this and the normal move function for cache prefer shares (appdata, backups, domains, system). For cache yes shares (data and isos), I do not have anything overridden so I would have expected that the global settings of 50%/25% would have been used but it doesn't appear that they are. Am I missing something? 08:34:36.859 ***************************************************** Mover Tuning Plugin version 2025.03.11 **************************************************** 08:34:36.863 ----------------------------------------------------------------- Global settings --------------------------------------------------------------- 08:34:36.865 Using global (cache) moving threshold: 50 % 08:34:36.867 Using global (cache) freeing threshold: 25 % 08:34:36.871 Age: Automatic (smart caching) 08:34:36.872 After script: /mnt/user/appdata/scripts/moverafter.sh 08:34:36.874 Before script: /mnt/user/appdata/scripts/moverbefore.sh 08:34:36.881 Enable Turbo: yes 08:34:36.884 Skip file list: /mnt/user/appdata/scripts/moverignore.sh 08:34:36.894 Test Mode: yes 08:34:36.896 Notify: errorsOnly 08:34:36.899 Debug Logging: no 08:34:36.900 Validate Filenames: yes 08:34:36.907 Launching before script: /mnt/user/appdata/scripts/moverbefore.sh 08:34:38.136 Before script finished 08:34:38.140 ***************************************************************** FILTERING FILES *************************************************************** 08:34:38.144 ----------------------------------------------------------- Processing [appdata] share ---------------------------------------------------------- 08:34:38.157 Primary storage: cache - size: 932GiB - used: 74 % (679GiB) 08:34:38.158 Secondary storage: user0 08:34:38.176 Share Information: Name: appdata - Path: /mnt/*/appdata 08:34:38.179 Moving threshold: 0% (0B) ; Filling up threshold: 95% (885GiB) 08:34:38.180 Mover action: user0->cache (cache:prefer). Pool is below priming threshold percentage: 74% < 95%. 08:34:38.181 => Will smart move newest files from user0 to cache until threshold. 08:36:01.100 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-18T083436.list for appdata 08:36:01.104 ----------------------------------------------------------- Processing [backups] share ---------------------------------------------------------- 08:36:01.117 Primary storage: backup - size: 466GiB - used: 53 % (245GiB) 08:36:01.118 Secondary storage: user0 08:36:01.121 Share Information: Name: backups - Path: /mnt/*/backups 08:36:01.124 Moving threshold: 0% (0B) ; Filling up threshold: 95% (443GiB) 08:36:01.124 Mover action: user0->backup (cache:prefer). Pool is below priming threshold percentage: 53% < 95%. 08:36:01.125 => Will smart move newest files from user0 to backup until threshold. 08:36:01.179 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-18T083436.list for backups 08:36:01.183 ------------------------------------------------------------- Processing [data] share ----------------------------------------------------------- 08:36:01.196 Primary storage: buffer - size: 1.9TiB - used: 1 % (513MiB) 08:36:01.196 Secondary storage: user0 08:36:01.200 Share Information: Name: data - Path: /mnt/buffer/data 08:36:01.202 Moving threshold: 0% (0B) ; Freeing threshold: 95% (1.8TiB) 08:36:01.203 Mover action: buffer->user0 (cache:yes). Pool is above moving threshold percentage: 1% >= 0%. 08:36:01.204 => Will smart move old files from buffer to user0. Nothing will be moved from user0 to buffer 08:36:01.206 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-18T083436.list for data 08:36:01.210 ----------------------------------------------------------- Processing [domains] share ---------------------------------------------------------- 08:36:01.222 Primary storage: cache - size: 932GiB - used: 74 % (679GiB) 08:36:01.223 Secondary storage: user0 08:36:01.226 Share Information: Name: domains - Path: /mnt/*/domains 08:36:01.229 Moving threshold: 0% (0B) ; Filling up threshold: 95% (885GiB) 08:36:01.230 Mover action: user0->cache (cache:prefer). Pool is below priming threshold percentage: 74% < 95%. 08:36:01.230 => Will smart move newest files from user0 to cache until threshold. 08:36:01.233 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-18T083436.list for domains 08:36:01.237 ------------------------------------------------------------- Processing [isos] share ----------------------------------------------------------- 08:36:01.249 Primary storage: cache - size: 932GiB - used: 74 % (679GiB) 08:36:01.250 Secondary storage: user0 08:36:01.254 /mnt/cache/isos does not exist. Is the share still used? Consider removing /boot/config/shares/isos.cfg if not. 08:36:01.255 => Skipping 08:36:01.259 ------------------------------------------------------------ Processing [system] share ---------------------------------------------------------- 08:36:01.270 Primary storage: cache - size: 932GiB - used: 74 % (679GiB) 08:36:01.271 Secondary storage: user0 08:36:01.275 Share Information: Name: system - Path: /mnt/*/system 08:36:01.277 Moving threshold: 0% (0B) ; Filling up threshold: 95% (885GiB) 08:36:01.278 Mover action: user0->cache (cache:prefer). Pool is below priming threshold percentage: 74% < 95%. 08:36:01.278 => Will smart move newest files from user0 to cache until threshold. 08:36:01.281 Updated Filtered filelist: /tmp/ca.mover.tuning/Filtered_files_2025-03-18T083436.list for system 08:36:01.697 ************************************************************ ANALYSING MOVING ACTIONS *********************************************************** 08:36:01.776 Deciding the action (move/sync/keep) for each file. There are 572799 files, it can take a while... 08:42:57.035 No new files will be moved/synced from primary to secondary 08:42:57.036 No new files will be moved/synced from secondary to primary 08:42:57.037 Launching after script: /mnt/user/appdata/scripts/moverafter.sh 08:42:57.116 After script finished with result: OK 08:42:57.117 Cleaning lock and stop files 08:42:57.121 ****************************************************************** WE ARE DONE ! ****************************************************************

I followed the instructions here (https://docs.unraid.net/legacy/FAQ/check-disk-filesystems/) and got the output below. Should I run a filesystem check on a BTRFS pool? UUID: ae50ab32-ea0b-48e4-9409-dc332166df09 Scrub started: Mon Mar 17 10:47:52 2025 Status: finished Duration: 0:04:41 Total to scrub: 1.39TiB Rate: 5.07GiB/s Error summary: no errors found

Hadn't seen that—thanks for pointing that out. Forgive my ignorance but how do I go about fixing this?

Thanks. Should I be concerned about rebooting remotely? I'm only hesitant because it failed to boot up after previous freeze ups but that very well may have had to do with hard rebooting while in a frozen state. I won't be back home for another week so I don't want to reboot if it won't boot back up.

Since upgrading to Unraid 7.0.0, my server keeps freezing, requiring hard reboots. After rebooting, the machine often fails to detect the flash drive until I switch USB ports, making me hesitant to reboot remotely. While traveling, it froze again but recovered after a few hours, allowing me to gather data. The Mover Tuning feature seems problematic since the update, but could there be other issues? Should I be concerned about rebooting? plugin: installing: memorystorage.plg Executing hook script: pre_plugin_checks plugin: downloading: memorystorage.plg ... done Executing hook script: pre_plugin_checks This script may take a few minutes to run, especially if you are manually mounting a remote share outside of /mnt/disks or /mnt/remotes /usr/bin/du --exclude=/mnt/user --exclude=/mnt/user0 --exclude=/mnt/disks --exclude=/proc --exclude=/sys --exclude=/var/lib/docker --exclude=/boot --exclude=/mnt -h -d2 / 2>/dev/null | grep -v 0$' ' 1.7M /.cache/mesa_shader_cache_db 1.7M /.cache 20K /tmp/tailscale 243M /tmp/.mount_firefopFevU6 4.0K /tmp/unraidcheck 132K /tmp/user.scripts 18M /tmp/fix.common.problems 27G /tmp/ca.mover.tuning 4.0K /tmp/ca_notices 36M /tmp/CA_logs 60K /tmp/gui.search 16K /tmp/unassigned.devices 4.0K /tmp/file.activity 4.0K /tmp/disklocation 14M /tmp/community.applications 160K /tmp/appdata.backup 424K /tmp/notifications 1.1M /tmp/plugins 4.0K /tmp/emhttp 27G /tmp 596M /usr/bin 28M /usr/lib 815M /usr/lib64 90M /usr/libexec 463M /usr/local 53M /usr/sbin 362M /usr/share 7.3M /usr/src 1.1M /usr/man 20K /usr/info 300K /usr/include 972K /usr/doc 2.4G /usr 24M /sbin 80K /run/libvirt 2.1M /run/docker 4.0K /run/avahi-daemon 8.0K /run/elogind 4.0K /run/dbus 4.0K /run/hook-state 628K /run/udev 16K /run/blkid 2.9M /run 12K /lib64/pkgconfig 1.8M /lib64/elogind 4.4M /lib64/security 47M /lib64 25K /lib/dhcpcd 192M /lib/firmware 18K /lib/modprobe.d 29M /lib/modules 512 /lib/systemd 8.5M /lib/udev 234M /lib 4.0K /etc/rsyslog.d 1.1M /etc/libvirt 340K /etc/libvirt- 8.0K /etc/fonts 12K /etc/gtk-3.0 40K /etc/zfs 8.0K /etc/OpenCL 4.0K /etc/pkcs11 152K /etc/lvm 8.0K /etc/libnl 8.0K /etc/ssmtp 20K /etc/samba 8.0K /etc/php.d 24K /etc/php-fpm.d 40K /etc/nginx 2.7M /etc/file 24K /etc/avahi 44K /etc/apcupsd 12K /etc/sysstat 44K /etc/security 260K /etc/ssl 568K /etc/ssh 4.0K /etc/nvme 48K /etc/mcelog 100K /etc/mc 60K /etc/logrotate.d 4.0K /etc/sensors.d 9.3M /etc/udev 28K /etc/modprobe.d 112K /etc/pam.d 12K /etc/elogind 4.0K /etc/cron.monthly 4.0K /etc/cron.hourly 20K /etc/cron.daily 4.0K /etc/cron.d 8.0K /etc/cron.weekly 8.0K /etc/dbus-1 4.0K /etc/sasl2 176K /etc/bash_completion.d 80K /etc/default 8.0K /etc/acpi 64K /etc/profile.d 116K /etc/X11 18M /etc 12M /bin 143M /var/sa 544M /var/local 4.0K /var/kerberos 16K /var/state 4.8M /var/cache 16K /var/named 16K /var/tmp 16K /var/spool 4.0K /var/lock 7.9M /var/log 4.6M /var/lib 703M /var 1.8M /root/.cache 4.0K /root/.mozilla 4.0K /root/.dbus 2.1M /root/.pm2 4.0K /root/.config 3.9M /root 30G / 0 /mnt/rootshare 0 /mnt/addons 0 /mnt Finished. NOTE: If there is any subdirectory from /mnt appearing in this list, then that means that you have (most likely) a docker app which is directly referencing a non-existant disk or cache pool script: memorystorage.plg executed Executing hook script: post_plugin_checks unraid-diagnostics-20250317-0513.zip