Need some help, always had mover set to move everything, but recently started seeding more etc and keep much more data on cache, hence I was going to upgrade my cache. To do it I have to move all files, so I changed settings to what I think should enforce movement but it mover moved only 5Gb etc despite saying in notification that it moved 600Gb in 3min(got fast HDD😅) can someone tell me which setting is messing with move?

4 hours ago, yanno said:

Rebalance ?

Rebalance for unnanttend files iirc

2 hours ago, Joloxx9 said:

. To do it I have to move all files, so I changed settings to what

To move all files without plugin settings, you need to use force move that will run unraid move. Or `mover.old start` in cli

Any updates on the turbo write issues?

Hi i have mover tuning plugin installed and i have set it to disable the mover running on schedule, in other words i dont want mover to run at all , but mover is still running on date and time i set and its moving the files from cache to array

What i want is to disable mover on schedule completely

Images related to the issue

Unraid version 7.0.1

5 hours ago, bigfoot18 said:

Any updates on the turbo write issues?

What issues?

9 minutes ago, drmetro said:

What i want is to disable mover on schedule

Do you have force mover enabled?

Post debug.zip

11 hours ago, Masterwishx said:

What issues?

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.

12 hours ago, bigfoot18 said:

does not enable when running mover manually or when the force move on schedule runs.

Do you mean if turbowrite enabled in settings?

12 hours ago, bigfoot18 said:

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.

Do you have this enabled ?

7 hours ago, Masterwishx said:

Do you mean if turbowrite enabled in settings?

Correct. It is enabled but it does not turn tubo write on before the mover runs.

7 hours ago, Masterwishx said:

Do you have this enabled ?

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.

1 hour ago, bigfoot18 said:

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.

Do you run I test mode maybe?

mvlogger "$(titleLine 'LET THE MOVING SHOW BEGIN !' '*')"
    if [ "$ENABLETURBO" = "yes" ]; then
        mvlogger "Forcing turbo write on"
        [ "$TESTMODE" != "yes" ] && /usr/local/sbin/mdcmd set md_write_method 1
    fi

2 hours ago, bigfoot18 said:

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.

It's just section name, all options are in same code, that read your config.

3 hours ago, Masterwishx said:

Do you run I test mode maybe?

No not in test mode.

2 hours ago, Masterwishx said:

It's just section name, all options are in same code, that read your config.

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.

Edited October 3, 2025Oct 3 by bigfoot18

6 hours ago, bigfoot18 said:

No turbowrite with manual or cron mover. But I do get turbowrite when mover runs due to usage threshold.

Post debug.zip

2 hours ago, Masterwishx said:

Post debug.zip

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

1 hour ago, bigfoot18 said:

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

You have mover disabled no, also nothing in logs, I need debug, after you run a couple of times when you disable mover on shedule to see what happened

On 10/4/2025 at 4:31 AM, Masterwishx said:

You have mover disabled no, also nothing in logs, I need debug, after you run a couple of times when you disable mover on shedule to see what happened

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

Hi @Masterwishx ,

I think the latest update v2025.10.03 broke "ignore files and folders listed inside of a text file" functionality

This feature was working for me before the update and now after updating it does not work.

I have File List Path set to /mnt/user/Media/scripts/mover_exclusions.txt and the contents of that file are:

/mnt/plotter_cache/Media/Usenet/Incomplete
/mnt/user/Media/Usenet/Incomplete

But now post-update, the files inside of those folders are being moved. Here is a screenshot of all of my settings

22 minutes ago, msalad said:

But now post-update, the files inside of those

There was no changes for this in last update, post debug.zip

4 minutes ago, Masterwishx said:

There was no changes for this in last update, post debug.zip

I'm trying to create it but I'm getting an error message:

ERROR: The Mover Tuning Debug Package Generation Script has failed - no response from the bash backend.

1 hour ago, bigfoot18 said:

But here are new logs. Turbowrite is now working with manual move

In your log you can see:

09:00:02.222 Enable Turbo: yes

When you run force cron it run unraid move without plugin options, so it use your unraid settings for turbo write

10 minutes ago, msalad said:

I'm trying to create it but I'm getting an error message:

Run in cli: mover debug

39 minutes ago, Masterwishx said:

Run in cli: mover debug

Thank you that worked

ca.mover.tuning-debug-20251005-1339.zip

5 hours ago, Masterwishx said:

When you run force cron it run unraid move without plugin options, so it use your unraid settings for turbo write

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.

Edited October 5, 2025Oct 5 by bigfoot18