Faceman

always best to pass through a USB controller rather than an individual device if you have the ability. that will give you full hot-plug and generally just work a lot better than trying to pass a device through separately.

you sure you are pointing to /download or is it going to /downloadS with an S... Your SAB setup has the extra S...

I also use multiple cache pools and custom mappings in sabnzbd and have it set that way to download to one disk but unpack to another disk (which is also the media cache for recent plex/jellyfin additions) It works just fine for me so I suspect you have a typo or mis-mapped directory in there. Do you have a screenshot of the Sabnzbd settings, in the 'Folders' page there are the internal directories for incomplete and complete, you need to ensure they are mapped to your new /download/complete and /download/incomplete correctly.

They did say in a community update a while back that they were looking into other ways to do it as an option, but as far as I can see it's still the best method for managing the licence without potentially opening the doors to piracy, and it works with the way unraid's array/pool structure works. Maybe unlinking the licence from the USB, while still using as the boot device, but that opens a can of worms requiring more invasive licence verification methods. I wouldn't want to use up any space on the storage disks for unraid's boot for various reasons (wouldn’t it have to be duplicated on every disk to cover for a disk failure?), and it wouldn’t even be possible on some users setups with purely ZFS or BTRFS based systems, as it would require a bootloader to mount the pool, and plenty of people use HBA's with the bios removed, so no disks available at boot time.

I have compose running and it mostly works fine with Folders, apart from the spacing being a little weird after a compose entry.

finally had a chance to reboot into 7.0.0 stable after running the betas and RCs since they were public. All working smoothly, all plugins working, docker (including compose) working, no errors in logs, ZFS pools imported without issue as expected, no issues with the main array, Mover tuning plug-in (Reynalds 2024.09.05.0222) works, all good. impatiently awaiting the jump to Linux Kernel 6.12 and OpenZFS 2.3.0 though....

override settings on the share settings page perhaps? and maybe go in and find that filtered list file and have a look at it, then delete it. it shouldn't be doing any filter/ignore stuff with that setting set to no. Otherwise, i'd say to try removing the plugin and re-installing because something is a bit off there.

You don't have test mode turned on do you?

Set the move based on age setting to true. it doesn’t know what files to move and what to keep without that setting enabled. yes I think that should be worded better in a future update. and also enable advanced settings and check that you dont have a move-all threshold set. youc an also check that you havent got any mover tuning overrides set on a per share basis, in each shares settings you can add optional separate thresholds and settings to have some shares empty completely and some keep files.

What version of the plugin do you have? that looks like it might be the old version if it cant find the mover script

This version hasn't had a bugfix for a few months, Dev is back and will be working on it again soon. the empty folders aren't going to cause any issues, and they should be able to be cleaned up once the script is fixed.

If you are using a docker image file you can leave it on the default, overlay2 is for people having issues with docker in a Folder on zfs.

welcome back. ZFS on unraid has been improving quickly and more of those functions will end up in the UI. Advanced ZFS users have been running with the separate ZFS plugins or doing that in the terminal for years now, and most of those plugins still work perfectly for people that need them, but we know it will end up part of Unraid stock soon enough. I always found Truenas to be clunky and convoluted compared to UnRaid, I have seen it slowly getting better and I do run it for testing and experimentation on my proxmox box but since I use Unraids main feature of mixed disks with easy expansion for my bulk storage pool I'd never use it as my main OS. even with ZFS Expansion now mostly working, expanding large arrays with multiple VDEVs is still a pain and more expensive to grow than unraid. I think having a medium size ZFS pool sitting on top of the slow but cheap to scale unraid array is the optimal NAS solution for the vast majority of users, and the Mover Tuning plugin is what makes that work... I'm looking forward to the file exclude feature working fully again, it seems broken for some people at the moment and we need that to work to get @alturismo's new media caching plugin working with mover tuning seamlessly as it would need to write to an exclude file or have some other dedicated allocation method to not interfere or have them fight each other.

updated to RC2 over the weekend and still no issues to report.

yea it's a common pitfall, almost every reddit post about mover tuning issues was due to people running the old version without realizing it.

I'll do some deep diving when I update from Beta4 to the RC then.

it says the mover is running, so whats in the logs? perhaps it's jammed on something and it's filling up faster than it is clearing. Also, try turning on file move based on age, set to auto. that could kick it into action. to stop the frozen mover use "mover stop" in the terminal, then click move now to start it again.

I guess if the mover tuning ignore list feature works you could probably have your script update the file with the currently cached media list and tuning would skip them until your plugin removes them from that list.

I see you are considering taking on or forking Mover Tuning, would be good to see that polished up a bit. I personally haven't had any issues but I see a few people struggling with it.

I'd suspect the update to RC1 replaces the plugin mover script with the old mover again and you should be able to get it working again after re-installing the plugin unless unraid has changed something significant, but with RC1 being more of less the same as Beta4 it shouldnt be too much of an issue. when installing mover tuning it renames the stock mover to "mover.old" and puts its own in for the scheduler to execute.

I was specifically referring to the number rendering issue on the configuration page in that post, it looks correct but the only difference between that drop down and the others is some extra tabbing and line breaks in the .page code, which I assumed wouldn't change how it is interpreted, but some peoples browsers are getting tripped up by it. suspect line is HERE. The symlink for the mover script issue has never affected me, I've been on beta since the first public version and mover tuning fixed it a few days after release by adding the correct symlink to the plugin script. i'm currently on 7.0.0beta4

I can see the line in the code that is definitely causing it, but I don't know why that one is behaving differently to the age drop-down that works.. PHP is not my thing, my web dev experience started and ended with HTML4. Unless its sensitive to the line break and tabbing in the .page file and that's somehow breaking it out of the <select> tags its in? That's the only difference, and I didn't think any of that mattered for html, but I guess .page files for unraid are handled a little differently? we might have to wait for a proper dev to get back onto this project. @Reynald has been away (he was moving house, then had some hardware failures etc) I cant get my systems to render it wrong though, it all works fine on every machine and browser I have.

Symlinks should not be necessary with the current version of the plug-in, that was fixed quite a while ago.

You should only put HDDs in the main array, SSDs should go in separate pools (standard cache setup as you mention), no you wont be able to have the SSD parity protected without adding at least one more matching SSD, or setting up the CA Appdata backup plugin for your containers which will backup that data to the array on a schedule, there are also ways to backup VMs in a similar manner. Just keep in mind that if you want a parity protected array you will have to sacrifice the 14TB and only be able to use the 2x 4Tb and 2x500gb drives for data until you add more disks.

does it do it in every browser you try? perhaps there is an issue with the theme you are using, or some browser plugin (an ad blocker trying to block scripts for example?)