October 22, 2025Oct 22 Using Unraid 7.1.4. Essentially what the title has said. I have two shares, Downloads and Media, that have files on the cache. The shares are set up to move the files from the cache to the array. The Mover is scheduled to move the files when the server is idle at 04:00 every day. However, it has not been doing that. Even when I manually invoke the Mover, nothing happens. It just starts and stops. I am not using the Mover Tuning plug-in, just the default in-built Mover on Unraid. The diagnostics show no errors that I'm familiar with.Oct 22 03:20:26 SERVER move: mover: started Oct 22 03:20:26 SERVER move: mover: finished Oct 22 03:23:39 SERVER emhttpd: Starting services... Oct 22 03:23:40 SERVER emhttpd: shcmd (390): /etc/rc.d/rc.samba reload Oct 22 03:23:40 SERVER emhttpd: shcmd (394): /etc/rc.d/rc.avahidaemon reload Oct 22 03:23:40 SERVER avahi-daemon[3138]: Got SIGHUP, reloading. Oct 22 03:23:41 SERVER unassigned.devices: Updating share settings... Oct 22 03:23:41 SERVER unassigned.devices: Share settings updated. Oct 22 03:23:53 SERVER emhttpd: shcmd (399): /usr/local/sbin/mover start |& logger -t move & Oct 22 03:23:53 SERVER move: mover: started Oct 22 03:23:53 SERVER move: mover: finished Oct 22 03:32:32 SERVER emhttpd: Starting services... Oct 22 03:32:32 SERVER emhttpd: shcmd (402): /etc/rc.d/rc.samba reload Oct 22 03:32:33 SERVER emhttpd: shcmd (406): /etc/rc.d/rc.avahidaemon reload Oct 22 03:32:33 SERVER avahi-daemon[3138]: Got SIGHUP, reloading. Oct 22 03:32:33 SERVER unassigned.devices: Updating share settings... Oct 22 03:32:33 SERVER unassigned.devices: Share settings updated. Oct 22 03:32:41 SERVER emhttpd: shcmd (411): /usr/local/sbin/mover start |& logger -t move & Oct 22 03:32:41 SERVER move: mover: started Oct 22 03:32:41 SERVER move: mover: finished Oct 22 03:33:56 SERVER emhttpd: Starting services... Oct 22 03:33:57 SERVER emhttpd: shcmd (414): /etc/rc.d/rc.samba reload Oct 22 03:33:57 SERVER emhttpd: shcmd (418): /etc/rc.d/rc.avahidaemon reload Oct 22 03:33:57 SERVER avahi-daemon[3138]: Got SIGHUP, reloading. Oct 22 03:33:57 SERVER unassigned.devices: Updating share settings... Oct 22 03:33:57 SERVER unassigned.devices: Share settings updated. Oct 22 03:35:29 SERVER emhttpd: Starting services... Oct 22 03:35:29 SERVER emhttpd: shcmd (425): /etc/rc.d/rc.samba reload Oct 22 03:35:30 SERVER emhttpd: shcmd (429): /etc/rc.d/rc.avahidaemon reload Oct 22 03:35:30 SERVER avahi-daemon[3138]: Got SIGHUP, reloading. Oct 22 03:35:30 SERVER unassigned.devices: Updating share settings... Oct 22 03:35:30 SERVER unassigned.devices: Share settings updated. Oct 22 03:36:06 SERVER emhttpd: Starting services... Oct 22 03:36:06 SERVER emhttpd: shcmd (436): /etc/rc.d/rc.samba reload Oct 22 03:36:07 SERVER emhttpd: shcmd (440): /etc/rc.d/rc.avahidaemon reload Oct 22 03:36:07 SERVER avahi-daemon[3138]: Got SIGHUP, reloading. Oct 22 03:36:07 SERVER unassigned.devices: Updating share settings... Oct 22 03:36:07 SERVER unassigned.devices: Share settings updated. Oct 22 03:37:03 SERVER kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint. Oct 22 03:37:10 SERVER emhttpd: shcmd (445): /usr/local/sbin/mover start |& logger -t move & Oct 22 03:37:10 SERVER move: mover: started Oct 22 03:37:10 SERVER move: mover: finished I tried changing a few settings and running it manually a few times, but to no avail. I have noted that the mover will still move files from other shares on the server, but just not these two shares for whatever reason. It was working before so I'm not sure what has changed. Any help would be much appreciated. Edited October 23, 2025Oct 23 by N¿¿B Added more information, included Unraid version. Diagnostics have been removed.
October 22, 2025Oct 22 Author I'm sorry. I thought I added them. I've attached the diagnostics. Edited October 23, 2025Oct 23 by N¿¿B Diagnostics removed.
October 22, 2025Oct 22 Community Expert Solution You might want to check that the capitalisation of the .cfg files for each share on the flash drive in the config/shares folder matches that of the actual share folders on the drives.
October 22, 2025Oct 22 Author That seems to have fixed my issue. Thank you! Just out of curiosity, how did you figure that out? I feel like I scoured the internet and forums and I never saw anything mentioning capitalization in the flash drive, of all places, affecting the Mover. How did you know that was the issue?
October 23, 2025Oct 23 Community Expert 9 hours ago, N¿¿B said:That seems to have fixed my issue. Thank you! Just out of curiosity, how did you figure that out?It has actually come up a number of times. I think at one time the case did not matter but it does nowadays. The flash drive is FAT32 so cannot actually store .cfg files that have the same spelling but different capitalization.9 hours ago, N¿¿B said:feel like I scoured the internet and forums and I never saw anything mentioning capitalization in the flash drive, of all places, affecting the Mover. How did you know that was the issue?If you look in the diagnostics in the /shares/shareDisks.txt file you will see an anonymised list of potential shares. If you see ones that has both an uppercase and a lower case first letter, the same last letter and the same name length then this might be the issue.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.