totalhavoc

Do you have compression with multicore enabled? I found this to cause issues and had to set it to enabled/normal.

So I'm not much of a coder but I know enough to get AI to help. The problem is you are feeding stat with $6 but $6 has a $ in it that needs to be escaped out. This is the code that AI provided instead of FINDSTR="$FINDSTR cmd=\"stat -c%X \\\"\"\$6\"\\\"\"; # Replace $ with \$ escaped_6="${6//$/\\\$}" # Use the new escaped variable in your command FINDSTR="$FINDSTR cmd=\"stat -c%X \\\"\"$escaped_6\"\\\"\"; Edit: looks like AI sucks as usual. I modified the age_mover file and add that code but it is still not escaping the $.

I just changed it from rsync for both to move/rsync and running a test to see what happens. edit: the file is not hard linked and I run the qbit mover script to stop torrents. Edit2: It did not move the files. I think this is because it is failing to stat the file when it builds it's list. I am running another move with lower % thresholds incase it didn't move them because of that. But seems to me if you are building the list based on date from the stat command and your stat fails, that file will never be in the list to move.

I've already done all of that. I have disabled "Validate input filenames to prevent attacks" which I thought was causing it but the files are still causing error when it tries to rsync them. Give me a few to dig in the logs and I will post the error when it hits the files. Mar 4 00:16:04 Unraid move: stat: cannot statx '/mnt/cache/data/torrents/music/Ice Cube - Greatest Hits [FLAC]/04 00 Dollar Bill Ya'\''ll.flac': No such file or directory and Mar 4 01:47:01 Unraid move: Rsync cmd: rsync --archive --xattrs --relative --hard-links --remove-source-files, Move file: "/mnt/cache/./data/torrents/music/Ice Cube - Greatest Hits [320](320)/04 $100 Dollar > Mar 4 01:47:01 Unraid move: Mar 4 01:47:01 Unraid move: rsync: [sender] link_stat "/mnt/cache/data/torrents/music/Ice Cube - Greatest Hits [320](320)/04 00 Dollar Bill Ya'll.mp3" failed: No such file or directory (2) Mar 4 01:47:01 Unraid move: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1338) [sender=3.4.1]

I'm running version 2026.02.27 on 7.2.3 and I noticed that files with a "$" in the file name are not being moved. Anything I can do so these files move besides scheduling a full flush with the old mover?

built in mover is disabled as suggested with new versions. It's configured to run via "Mover Tuning schedule:" cron kicked off age_mover every time even with parity check running. Check is done now but I do have a drive to install in a few days which will cause another check. I'll post logs then.

Mover still seems to run when parity check is running. I have a check running and ca mover is still kicking off and running. version 25.12.13 on 7.2.2. Going to just temporarily disable ca mover but may be something to look into. EDIT: I do have it set to not allow mover when parity check is running

I've been having an issue with NFS mounts not automounting anymore. I'm on 7.1.3 and for the life of me I cannot figure it out. I have tried multiple different delay settings to see if stuff was just taking time to start up but nothing helps. I can mount the shares manually once they are not grayed out. Diagnostics attached. ud_diagnostics-20250614-213426.zip EDIT: I found the issue. The automount script is dependent on being able to ping the default gateway. My firewall by default blocks ICMP. Once I found that in the code I allowed ping from my unraid box and the automount script is able to proceed.

It's fixed. The synology unit has multiple nics with only 1 active. There was a static IP assigned to one of the inactive nics. Removed the static ip from the inactive nic and everything is working now

both: rpc mount export: RPC: Unable to receive; errno = No route to host I've disabled the firewall at the synology and I can ping from unraid box to each synology unit. I only mount 1 of them but I have 2 others I've been trying to test with to see what the issue is. Edit: it has been working fine for months prior to todays update. Other NFS clients are mounting the same synology unit fine.

I just updated to the latest version of the plugin and the showmount requirement is preventing my Synology based nfs shares from being mounted on Unraid. Showmount -e synology_ip results in an rpc error. Still researching a fix/workaround. ud_diagnostics attached