Cressio

I see. I was hoping the mover would always just move to the correct disk based on its current share regardless of its originating share. Sounds like that Caution section explains why that isn't possible (although I don't fully understand it... but that's neither here nor there) Thanks for the help. I managed to update and adjust the script to get it working all within the same share. That error *should* probably be updated and clarified if possible though so maybe I'll try to report that suggestion.

Yeah that was my thesis as well. Looks like they’re actually moving now. I imagine/hope this is worthy of a bug report and not intended behavior?

/mnt/user/media/processed/Music/Flux Pavilion/Cannonball/01 - Cannonball.mp3 /mnt/server/media/processed/Music/Flux Pavilion/Cannonball/01 - Cannonball.mp3

Done

Little bump on this after I've added logs. I hope I have something misconfigured, that'd be an easy fix, but I can't really see where I do. The Mover logic flow should basically be: Share files are supposed to be stored on array -> files exists on share that isn't on array -> files gets moved to array, right? The file(s) definitely don't exist on array, I checked each disk 1 by 1 and the Unraid GUI also reflects their actual location (not on array, and definitely not "exist"-ing on array). The share they're on (media) moves to the array properly in every other scenario. This is the only time I've ever had a problem with Mover and it's also the only time I've had files get downloaded and moved from appdata -> my main media share, so it makes me suspect Unraid has become confused in some way.

alright I'll try to get that done. I think I just crashed the web page trying to generate the log because it's so large... as far as I can tell the only relevant mover information is the "file exists" part so maybe I'll regenerate a log without mover logging and post that for general system information. But otherwise there's gonna be roughly 10 thousand lines (number of tracks I have downloaded right now) of the same thing edit: yeah the page ran out of memory trying to download the existing log lol

To try and keep it succinct, I'm trying to using Lidarr combined with a script that integrates Deemix (https://github.com/RandomNinjaAtk/arr-scripts), and the default configuration of the script makes it to where it downloads in the appdata folder (I tried to change this, but the behavior got weird so I was planning to just keep it this way for now). Lidarr then atomic moves the music files into my designated music directory (which isn't a child folder of appdata). Unraid then seems to get confused and won't move these files because they "exist" already. Well... they don't exist where I want them. My appdata is set to use my NVMe cache, while my music directory is set to be on my array, but Unraid won't move them. I've checked the disks and files individually and they are indeed not on the array but instead on the cache disk and permanently filling up my cache. Any idea how to fix this? This is the Github issue I posted for the script that has more details and screenshots attached. It's probably not a script issue but I just went there first to see what he had to say. As far as I can tell, all my Unraid settings are correct so I'm pretty confused. Maybe I have something configured wrong though. Container PUID/PGID is 99/100. Maybe it needs to be root 0/0? Doesn't seem it like though since it theoretically is the literal root operating system that's struggling to move these files regardless who owns what. But idk considering the non root-owned files like the extra .lrc and .jpg are moving successfully maybe it has something to do with it. I just don't see why it would. SOLUTION: files that are created on a share, and then moved to a share with different disk/mover settings, will break mover. Unraid/Linux doesn't support this, you need to handle them on the same share. Unraid's error message is incorrect and misleading.

Hey, is this still working? Doesn't seem to for me... although I sort of have no idea what I'm doing. Am I supposed to just install the container and have it function? Web GUI throws a "site can't be reached" error for me. Tried a few different ports, including 5540 like the guy mentioned above even though I'm not really sure what he was saying. I'm just tryna use this to validate if my Redis is working at all or doing anything for a Nextcloud container

I *think* this worked for me. I'm a noob and have very little understanding of all of this so don't take my word for too much, it could've been dumb luck, but I had basically everything working except being able to access the Unraid GUI via subnet (I don't wanna use Tailscale IPs or device names, I want everything standardized so I can use 1 IP everywhere). Did this, and now it works. So, thanks!

Hey, sorry if this has been answered already but I couldn't find an answer; does removing this plugin uninstall the drivers if I ever wanted at some point to use a GPU in a VM? If not, how could I go about doing that?