Terebi

Appears to be a bug in the dashboard responsive code that if you empty a column of all gadgets, you cannot drag and drop back into anymore. Doing a dashboard reset via the "blue wrench" works, but probably should make sure empty columns get a drag and drop target added.

Any chance you could add CPU in as well? Would probably need different temperature ranges. My thought is that the CPU and Disk calcs are done independently, and then whichever one wants the higher fan speed wins.

Note that I am not maintaining my script above anymore, as the new version of mover tuning now supports "age moving" similar to what my script above did.

Drive replaced, so far painless so fingers crossed!

Hrm, my "only overnight" commentis wrong, it just happened again. This is visible in the log :

For several days now, when I log into Unraid, the docker tile is missing in the dashboard, and on the docker tab it says "Docker Service failed to start" with no dockers listed. BUT the dockers are in fact running perfectly fine. For the ones that I remember the port numbers for, I can go to their web guis just fine. Rebooting causes an unclean shutdown, and a parity check on boot, but all of the dockers come up cleanly. This only happens overnight. I dunno if its an accumulation/leak thing, or if something is scheduling overnight that triggers it. I have just enabled the log server, so I will post additional logs tomorrow. though its possible the interesting stuff is in the attached diagnostics. tower-diagnostics-20250410-0829.zip

I can, but why is that a validation rule, when $ is a completely valid char in linux filenames?

Looks like $ in filenames may be causing issues? I see some posts a few pages back with a similar issue, where the response was $ is not valid in filenames. But $ are valid for filenames both based on spec and obviously, since those files exist and were put there by other unraid processes/containers Apr 2 11:33:15 Tower move: Error: Invalid characters in filename: 'Beast Games (2024) - S01E01 - 1,000 People Fight For $5,000,000 [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv' Apr 2 11:33:15 Tower move: Error: Invalid filename path: 'data/media/tv/Beast Games (2024) {tvdb-447806}/Season 1/Beast Games (2024) - S01E01 - 1,000 People Fight For $5,000,000 [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv' Apr 2 11:33:15 Tower move: Error: Invalid characters in filename: 'Beast Games (2024) - S01E10 - $10,000,000 Coin Flip [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv' Apr 2 11:33:15 Tower move: Error: Invalid filename path: 'data/media/tv/Beast Games (2024) {tvdb-447806}/Season 1/Beast Games (2024) - S01E10 - $10,000,000 Coin Flip [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv' Apr 2 11:33:15 Tower move: Error: Invalid characters in filename: 'Beast Games (2024) - S01E08 - Betray Your Friend For $1,000,000 [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv' Apr 2 11:33:15 Tower move: Error: Invalid filename path: 'data/media/tv/Beast Games (2024) {tvdb-447806}/Season 1/Beast Games (2024) - S01E08 - Betray Your Friend For $1,000,000 [Release Sources (Streaming Service) - Notifiarr_6_0 WEBDL-720p][EAC3 2.0][h264]-FLUX.mkv'

I just installed the plugin and also see them (although I may have had a prior version installed long ago that could be influencing things)

Is it possible to set parity timing to be a sliding window? Like I want every 90 days, but if I have an unsafe shutdown that causes an unscheduled parity check, that should move the next scheduled check back 90 days.

I think these settings could still use some additional tweaks : 1) I think free down and prime up should be split. Maybe I want to free down to 80%, but fill up to 70%? 2) The second setting is limited by the first setting. Especially in the "prime" scenario, this doesn't make sense. If my current usage is 20%, and I have prime to 70%, that means that "only move" is also at least 70%. 20% < 70%, so mover won't run, and it won't "prime" ? 3) (Bonus question) : If I have old files on cache, and new files on array, will it swap them?

This has always been "backwards" in my mind, but I swear there was a direct instruction earlier that this was the correct behavior to use the age-cache. But I will try flipping it.

Since upgrading to the newest version of this plugin, with Masterwishx in the maintainer list, it does not appear to be working as I expect. When the cache is below the fill percent, I expect it to "prime" the cache. When it is above the fill percent, I expect it to empty. Neither appears to be happening as I expect anymore. I have the threshholds set at 75%, and actual cache usage is at 82%, but it is not moving anything to array. Full mover log below, but what I consider to be the "important bits" is here. I have no idea where the 0 and 99% are coming from. I do not have "per-share" settings set. Per the "auto age" instructions in the older version of the plugin, I have the share set to move cache<-array which is "backwards" but was apparently the way it is coded? Mar 7 13:33:22 Tower move: ------------------------------------------------------------- Processing [data] share ----------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: user0 Mar 7 13:33:22 Tower move: Share Information: Name: data - Path: /mnt/*/data Mar 7 13:33:22 Tower move: Moving threshold: 99% (923GiB) ; Freeing threshold: 0% (0B) Mar 7 13:33:22 Tower move: Mover action: user0->cache (cache:prefer). Pool is above freeing threshold percentage and below priming threshold percentage: 0% < 82% < 99%. Mar 7 13:33:22 Tower move: => Skipping Mar 7 13:33:17 Tower move: ***************************************************************** FILTERING FILES *************************************************************** Mar 7 13:33:17 Tower move: ----------------------------------------------------------- Processing [appdata] share ---------------------------------------------------------- Mar 7 13:33:17 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:17 Tower move: Secondary storage: none Mar 7 13:33:17 Tower move: Share Information: Name: appdata - Path: /mnt/cache/appdata Mar 7 13:33:17 Tower move: Mover action: no action, only cache used (cache:only). Mar 7 13:33:17 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Mar 7 13:33:17 Tower move: Calculating share usage... (can take a moment) Mar 7 13:33:22 Tower move: cache/appdata used: 27GiB Mar 7 13:33:22 Tower move: ------------------------------------------------------------- Processing [data] share ----------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: user0 Mar 7 13:33:22 Tower move: Share Information: Name: data - Path: /mnt/*/data Mar 7 13:33:22 Tower move: Moving threshold: 99% (923GiB) ; Freeing threshold: 0% (0B) Mar 7 13:33:22 Tower move: Mover action: user0->cache (cache:prefer). Pool is above freeing threshold percentage and below priming threshold percentage: 0% < 82% < 99%. Mar 7 13:33:22 Tower move: => Skipping Mar 7 13:33:22 Tower move: ----------------------------------------------------------- Processing [domains] share ---------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: none Mar 7 13:33:22 Tower move: Share Information: Name: domains - Path: /mnt/cache/domains Mar 7 13:33:22 Tower move: Mover action: no action, only cache used (cache:only). Mar 7 13:33:22 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Mar 7 13:33:22 Tower move: Calculating share usage... (can take a moment) Mar 7 13:33:22 Tower move: cache/domains used: 0B Mar 7 13:33:22 Tower move: ------------------------------------------------------------- Processing [isos] share ----------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: none Mar 7 13:33:22 Tower move: Share Information: Name: isos - Path: /mnt/cache/isos Mar 7 13:33:22 Tower move: Mover action: no action, only cache used (cache:only). Mar 7 13:33:22 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Mar 7 13:33:22 Tower move: Calculating share usage... (can take a moment) Mar 7 13:33:22 Tower move: cache/isos used: 5.3GiB Mar 7 13:33:22 Tower move: ------------------------------------------------------------- Processing [prv] share ------------------------------------------------------------ Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: user0 Mar 7 13:33:22 Tower move: Share Information: Name: prv - Path: /mnt/cache/prv Mar 7 13:33:22 Tower move: Moving threshold: 99% (923GiB) ; Freeing threshold: 0% (0B) Mar 7 13:33:22 Tower move: Mover action: cache->user0 (cache:yes). Pool is below moving threshold percentage: 82% < 99%. Mar 7 13:33:22 Tower move: => Skipping Mar 7 13:33:22 Tower move: ---------------------------------------------------------- Processing [shareddata] share -------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: user0 Mar 7 13:33:22 Tower move: /mnt/cache/shareddata does not exist. Is the share still used? Consider removing /boot/config/shares/shareddata.cfg if not. Mar 7 13:33:22 Tower move: => Skipping Mar 7 13:33:22 Tower move: ------------------------------------------------------------ Processing [system] share ---------------------------------------------------------- Mar 7 13:33:22 Tower move: Primary storage: cache - size: 932GiB - used: 82 % (761GiB) Mar 7 13:33:22 Tower move: Secondary storage: none Mar 7 13:33:22 Tower move: Share Information: Name: system - Path: /mnt/cache/system Mar 7 13:33:22 Tower move: Mover action: no action, only cache used (cache:only). Mar 7 13:33:22 Tower move: => Nothing will be moved. Share usage is taken into account in the calculation of the threshold for other shares. Mar 7 13:33:22 Tower move: Calculating share usage... (can take a moment) Mar 7 13:33:22 Tower move: cache/system used: 16GiB Mar 7 13:33:22 Tower move: ************************************************************ ANALYSING MOVING ACTIONS *********************************************************** Mar 7 13:33:22 Tower move: Deciding the action (move/sync/keep) for each file. There are 4 files, it can take a while... Mar 7 13:33:22 Tower move: No new files will be moved/synced from primary to secondary Mar 7 13:33:22 Tower move: No new files will be moved/synced from secondary to primary Mar 7 13:33:22 Tower move: Cleaning lock and stop files Mar 7 13:33:22 Tower move: ****************************************************************** WE ARE DONE ! ****************************************************************

I am using the age tuner, with the "reverse mover" config in the share setup (array->cache). Under the old mover, you could manually run find and pipe it to move. But that does not seem to work in the new mover/tuner. Is there any way to move a specific file or subdirectory ignoring other mover rules to free up space? (eg, I expect to download some very large files that will overfill my cache, so I want to drain some, but not all of the existing cache)

I can't see the image myself either and I don't remember what it said. However, the easy answer is just to install the asustor platform drivers, and then most things will just work as expected.

a bit of an edge case but a nice feature might be time (hour) based threshholds. So I could say nightly, I want to empty the cache down to 80%, even if only 81% is used. But then I want to run the mover hourly, but only have it do something if current usage is above 90%. That way if things are unexpectedly full, it can get cleaned up before the cache is full. But we aren't eating i/o, spinup, perf, etc for normal filling of the cache during the day.

The mover does not appear to be cleaning up empty directories anymore using the age mover. the "Clean Empty Folders" setting is set to true.

No, just changing the size is all you should need to do. However, I will likely no longer be maintaining this script, since the new unraid 7 version of mover tuning has auto-age threshhold moving available out of the box, which replicates this scripts functionality in a more robust way. If you have moved to unraid 7, I would suggest using that.

@buscopina Unfortunately, I do not speak German. Hopefully you do speak English. While I believe my script does what you would like (keep media on cache longer), the new version of the "Mover Tuning" plugin also does this using the "auto age" feature, and in a more robust/supported way. I would suggest using the new plugin over my script.

So I set my "media" share to array->cache, but the tuner will actually empty it from cache->array to keep it below 80%?

@Reynald I am interpreting that to mean that if I have the auto age set to 80%, and I am at 20%, the mover will fill the cache back up to 80% with the newest files. Is that accurate? If so, how do I enable that? In the logs for the relevant share I see :

@Reynald I rebooted and reinstalled and the link appears to be working now.

ed : I got it working by doing the workaround commands above, but I thought they weren't needed anymore in the fork? Using @Reynald's version, mover has stopped moving. If I "move now" I just see the below line in the log Jul 19 08:32:37 Tower root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start -1 0 0 '' '' '' '' no 95 '' '' 80 if I run mover manually from a console, I get the following error /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 119: /usr/local/sbin/move: No such file or directory Running 7.0.0-beta.2 and tuning version Reynald 2024.07.10 (Will this still show up as an update when its not in CA? Or do I have to manually update somehow?)

Lol, I actually meant to post my comment in the mover tuner thread!