bigfoot18

Appreciate it. Its a great plugin so keep up the good work. For anyone who wants to use TW when running the mover on a cron schedule you can do what I did. Disable the force move in the plugin settings and create a userscript that runs at the cron interval you want. Put this inside the script. You can adjust the sleeps to whatever you prefer as the mover will consider itself done before all of the disk activity is actually finished. #!/bin/bash sleep 30 /usr/local/sbin/mdcmd set md_write_method 1 sleep 5 /usr/local/sbin/mover.old start sleep 180 /usr/local/sbin/mdcmd set md_write_method 0

That kinda seems like an oversight to me but ok. There should be an option to enable turbowrite even on the cron force move. Also the setting says "Forces unRaid to switch to turbo write mode (reconstruct write) when mover is running." That wording makes it seem like it should always enable turbo write when the mover is running regardless of how its initiated.

Mover is not disabled. But here are new logs. Turbowrite is now working with manual move. But still not with cron force move all. ca.mover.tuning-debug-20251005-0959.zip

ca.mover.tuning-debug-20251004-0320.zip

No not in test mode. Still doesnt run with turbowrite no matter what I change. No turbowrite with manual or cron mover. But I do get turbowrite when mover runs due to usage threshold.

Correct. It is enabled but it does not turn tubo write on before the mover runs. I have tried with it both enabled and disabled. Neither works. Id assume turbo write is not part of the "Filters" as it is not in that section and would always enable turbo write on every mover start.

On 7.1.4, turbo write does not enable when running mover manually or when the force move on schedule runs. Turbo write only enables when mover is triggered by used space threshold.

Any updates on the turbo write issues?

So the plugin does function perfectly when it reaches the capacity threshold. My cache hit 50% usage and on the next hour, it enabled turbo write, moved files over until my 25% threshold freedown point was hit, then disabled turbo write. So that part of the plugin is working as intended.

As far as I can tell it does not run the command to change the write method before starting the mover. I will test when the next update drops. Edit: Confirmed Turbo Write is not enabled for either the manual or cron initiated mover.

So that was something I tried already. Doesnt update the cron file. For now I just manually used nano to edit the file then ran update_cron. Turbo write on manual mover still doesnt function after disabling and enabling the plugin. Appreciate your help.

Either Windows Explorer or nano from terminal. Either shows the same thing. 7.1.4 ca.mover.tuning-debug-20250903-0151.zip

I open the file that is created in the flash/config/plugins/movertuning folder. Yes By Clicking the "Move Now" button on the main page.

Thats the question. I have reinstalled the plugin multiple times but the .cron file never updates with the new plugin settings. Im not changing the cron file manually im changing it via the plugin gui. However the file does not change. Also Force Turbo Write during mover does not work for me when running the mover manually so thats the other issue im trying to solve.

Ok so the plugin is not updating the .cron file that is created in the flash drive plugin folder. So when I make changes to the cron schedule in the plugin its not updating the .cron file. Also I have disabled logging in the plugin but since the cron file isnt being updated its not disabling the logging. Would I put that here in BEFORE mover? Then set the write method back in the AFTER mover box?

Yes but I want it to enable turbo write during the mover when I use the Move Now button but I dont want it to respect the threshold set in the plugin. Apparently changing the settings in the plugin does update the .cfg but doesnt update the .cron. I have logging set to disabled in both the normal mover settings as well as the plugin but the .cron file does not update.

Ok so I still want turbo write to enable when I run the mover manually. With how the plugin is currently the mover will not run with the "move now" button unless the cache is above 50% used. The only way to run the mover with this plugin installed if the cache is below 50% is to disable "Move Now button follows plug-in filters". But this means turbo write wont enable during the move process unless I change the disk mode manually first. Basically I just want the move now button to enable turbo write but ignore the threshold. If thats even possible. Also I have the logging disabled but the cron that is created still shows it enabled. 0 7 * * * /usr/local/sbin/mover.old start |& logger -t move

Wondering if theres an option to still force turbo write when forcing a move but to ignore the Only move if above this threshold of used Primary (cache) space option. For example when I need to reboot my server id like to have everything moved off of cache and into the array beforehand. Currently I have to adjust the threshold first then run the mover manually and then change the threshold back.

Hello Running into an issue with remote SMB shares. I've got my primary unraid server mounted to my backup storage server via UD's remote SMB share. The remote is my main server, so I have it mounted via its IP address on my backup server. I can search and mount the remote share just fine but as soon as I try to either browse the files with the unraid file manager or try to navigate to the "remotes" folder in something like Appdata Backup, it locks up and starts throwing errors. Source and Target: 6.12.15 Ive had this set up and working for almost a year and nothing about my setup has changed recently. So unsure as to what the issue is. Aug 7 02:21:55 Parallax kernel: CIFS: Attempting to mount \\ZENITH.LOCAL\ZenithArray Aug 7 02:22:10 Parallax kernel: CIFS: VFS: cifs_mount failed w/return code = -512 Aug 7 02:22:10 Parallax unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_ZenithArray' '//ZENITH.LOCAL/ZenithArray' '/mnt/remotes/ZenithArray' 2>&1) took longer than 15.0s! Aug 7 02:22:10 Parallax unassigned.devices: Mount SMB share '//ZENITH.LOCAL/ZenithArray' using SMB 3.0 protocol. Aug 7 02:22:10 Parallax unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,hard,relatime,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,,actimeo=10,rsize=1048576,wsize=1048576,closetimeo=30,vers=3.0,credentials='/tmp/unassigned.devices/credentials_ZenithArray' '//ZENITH.LOCAL/ZenithArray' '/mnt/remotes/ZenithArray' Aug 7 02:22:10 Parallax kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified Aug 7 02:22:10 Parallax kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified Aug 7 02:22:10 Parallax kernel: CIFS: Attempting to mount \\ZENITH.LOCAL\ZenithArray Aug 7 02:22:10 Parallax unassigned.devices: Successfully mounted '//ZENITH.LOCAL/ZenithArray' on '/mnt/remotes/ZenithArray'. Aug 7 02:22:10 Parallax unassigned.devices: Device '//ZENITH/ZenithArray' is not set to be shared. Aug 7 02:22:24 Parallax unassigned.devices: Unmounting Remote SMB/NFS Share '//ZENITH/ZenithArray'... Aug 7 02:22:24 Parallax unassigned.devices: Synching file system on '/mnt/remotes/ZenithArray'. Aug 7 02:22:24 Parallax unassigned.devices: Unmount cmd: /sbin/umount -t cifs -l '/mnt/remotes/ZenithArray' 2>&1 Aug 7 02:22:24 Parallax unassigned.devices: Successfully unmounted '//ZENITH.LOCAL/ZenithArray' Aug 7 02:24:13 Parallax kernel: CIFS: VFS: \\ZENITH.LOCAL has not responded in 180 seconds. Reconnecting... parallax-diagnostics-20250807-0250.zip

So can confirm my creds are correct. Fan control works and I can get sensor data with the same creds via CLI. But the GUI part here will not connect.

Could an option be implemented to allow 2 separate usb external drives to run in a raid 1 config?

No change..

This is what I get. # sensors chip "w83795adg-i2c-0-2f" ignore "fan1" chip "w83795adg-i2c-0-2f" ignore "fan3" chip "w83795adg-i2c-0-2f" ignore "fan4" chip "w83795adg-i2c-0-2f" ignore "fan5" chip "w83795adg-i2c-0-2f" ignore "fan7" chip "coretemp-isa-0000" label "temp4" "CPU Temp" chip "w83795adg-i2c-0-2f" label "fan8" "Array Fan"

All I get from running that in console is a list of errors. Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 8: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 10: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced sensors_init: Can't parse bus name

So I installed System Temp after installing Perl. Initially, everything worked fine. But when I attempt to save the settings, the drop down boxes for the senors only have one option "Not Used"