-
[Plugin] Mover Tuning
New version is out, fixed calculations for threshold pool used, users who used : 75% to 25% or any others, now should work correctly! Will be cool to have feedback that is fine now :)
-
[Plugin] Mover Tuning
For users that have plugin not moving data with thresholds! Seems I found the bug, should be fixed in next version...
-
[Plugin] Mover Tuning
I can't reproduce it, but will try to fix it, you can help with testing?
-
[Plugin] Mover Tuning
OK ,i checked the diagnostic , you have all data from media share (keep on primary) : 03:40:01.335 Using global (cache:yes) moving threshold: 40 % 03:40:01.336 Using global (cache:yes) freeing threshold: 25 % 03:40:01.337 Using global (cache:prefer) fillup threshold: 80 %cache|media|yes|1784793600|6857058039|31774043642|124965909504|1|4192366|keep on primary|/mnt/cache|none|media/TV Shows/Ransom Canyon (2025) {tvdb-443051}/Ransom Canyon (2025) - S02E01 - Hey There Cowboy [NF WEBDL-2160p][DV HDR10][EAC3 Atmos 5.1][HEVC]-Kitsune.mkv|f I think you need to make more gap between moving - freeing thresholds (more than 15%) .... Like wrote in `Note:`
-
[Plugin] Mover Tuning
Found in mover logs : ``` 11:40:01.728 ----------------------------------------------------------------- Global settings --------------------------------------------------------------- 11:40:01.733 Using global (cache:yes) moving threshold: 90 % 11:40:01.736 Using global (cache:yes) freeing threshold: 50 % 11:40:01.738 Using global (cache:prefer) fillup threshold: 90 % 11:40:01.745 Age: Automatic (smart caching) 11:40:01.759 ATIME: yes 11:40:01.767 mover: already running ... ``` You have latest version but in syslog old version: `Installing new package /boot/config/plugins/ca.mover.tuning/ca.mover.tuning-2026.06.24-x86_64-1.txz`
-
[Plugin] Mover Tuning
Do you run empty disk or remove share maybe at same time? Or age_mover status? You didn't included syslog to diagnostic
-
[Plugin] Mover Tuning
If notify set to No or errorOnly, it should NOT send any notify, you sended diagnostic without debug enabled and can't find in syslog anything about plugin running. Also you have set to run plugin every 5 min this is not good idea, can be plugin can't move all in this time, so you got notify it still running or you have another script also run plugin? You need more gap between plugin runs... You can send diagnostic with log, debug enabled (file and syslog) after some runs I can check it again. Also should be some info in syslog about plugin
-
[Plugin] Mover Tuning
What exactly notify do you have i cant see it in diagnostic
-
[Plugin] Mover Tuning
Do you mean privios version same behavior? You can send me by pm the diagnostic (this not contain any sensitive data) :) Or you can check settings and mover logs debug logs...
-
[SUPPORT] TEMPLATE MASTERWISHX - FileBrowser Quantum
I'm not checked other configs than when I made a template xml, for me all working fine as I wrote in first message (also updated config file recently) ... So I think you can find more info about in FileBrowser Quantum github docs, issues or discussions..
-
Shutdown deprecated - how to do a clean shutdown via CLI
Will be cool , if it will be updated in docs also : https://docs.unraid.net/unraid-os/system-administration/advanced-tools/command-line-interface/#powerdown to `shutdown -h now`
-
[SUPPORT] TEMPLATE MASTERWISHX - FileBrowser Quantum
Container Path = folder name in container mounted from host path. You can use container cli to check container paths...
-
[SUPPORT] TEMPLATE MASTERWISHX - FileBrowser Quantum
You need first mount host folder to container, then you need to edit FileBrowser config for this folder. Check here : https://filebrowserquantum.com/en/docs/configuration/users/
-
[Plugin] FanCrtl Plus
it seems we have updated version: FanCtrl Plus 2
-
[Support] MOTD (Message of the Day)
Today got : panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7678dc] goroutine 22 [running]: github.com/dkaser/unraid-motd/datasources.processDriveZFS(0xc00040e000, {0xc000234001?, 0x10?}, {0xbdb010, 0x1}) /home/runner/work/unraid-motd/unraid-motd/tag/datasources/drives_common.go:55 +0x5c github.com/dkaser/unraid-motd/datasources.processDrive(0xc0004f609d?, {0xc000234001?, 0x83a375?}, {0xc0004f6099?, 0x0?}, {0xbdb010?, 0xc000067d08?}) /home/runner/work/unraid-motd/unraid-motd/tag/datasources/drives_common.go:32 +0x3e github.com/dkaser/unraid-motd/datasources.getUserDriveUsage(0xc00040e000) /home/runner/work/unraid-motd/unraid-motd/tag/datasources/drives_user.go:52 +0x5ff github.com/dkaser/unraid-motd/datasources.GetUserDrives(0xc0001a4ea0, 0xc0001a0b60) /home/runner/work/unraid-motd/unraid-motd/tag/datasources/drives_user.go:19 +0x19a created by github.com/dkaser/unraid-motd/datasources.RunSources in goroutine 1 /home/runner/work/unraid-motd/unraid-motd/tag/datasources/common_vars.go:103 +0x469