Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Automover for unRAID

Featured Replies

7 hours ago, jcofer555 said:

should be fixed in next update hopefully. should be sometime today that i push the update

I updated the plugin. tried to schedule it, pressed schedule and same error: schedule_create.php returned an empty response — check the PHP file for errors

Downloading plugin
plugin: installing: automover.plg
Executing hook script: CA_preHook
Clearing Community Applications plugin cache
Executing hook script: pre_plugin_checks
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ...
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... 89%
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... 100%
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... done

plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ...
plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ... 100%
plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ... done

plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ...
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 5%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 11%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 17%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 23%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 29%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 35%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 41%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 47%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 53%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 59%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 65%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 71%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 77%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 83%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 89%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 95%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 100%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... done


+===================================================================================================+
| Installing new package /boot/config/plugins/automover/unraid-automover-2026.03.19.01-noarch-1.txz |
+===================================================================================================+

Verifying package unraid-automover-2026.03.19.01-noarch-1.txz.
Installing package unraid-automover-2026.03.19.01-noarch-1.txz:
PACKAGE DESCRIPTION:
Package unraid-automover-2026.03.19.01-noarch-1.txz installed.

+===========================================================================================+
| Installing new package /boot/config/plugins/automover/jdupes-1.30.0-x86_64-2_slackdce.txz |
+===========================================================================================+

Verifying package jdupes-1.30.0-x86_64-2_slackdce.txz.
Installing package jdupes-1.30.0-x86_64-2_slackdce.txz:
PACKAGE DESCRIPTION:
# jdupes (identifying and taking action upon duplicate files)
#
# jdupes is a program for identifying and taking actions upon duplicate
# files.
#
# This fork of fdupes known as 'jdupes' is heavily modified from and
# improved over the original.
#
# https://github.com/jbruchon/jdupes
#
Package jdupes-1.30.0-x86_64-2_slackdce.txz installed.

+===============================================================================================+
| Installing new package /boot/config/plugins/automover/libjodycode-4.0.1-x86_64-2_slackdce.txz |
+===============================================================================================+

Verifying package libjodycode-4.0.1-x86_64-2_slackdce.txz.
Installing package libjodycode-4.0.1-x86_64-2_slackdce.txz:
PACKAGE DESCRIPTION:
# libjodycode (library for tools like jdupes)
#
# libjodycode is a software code library containing code shared among
# several of the programs written by Jody Bruchon such as imagepile,
# jdupes, winregfs, and zeromerge.
#
# https://github.com/jbruchon/libjodycode
#
Executing install script for libjodycode-4.0.1-x86_64-2_slackdce.txz.
Package libjodycode-4.0.1-x86_64-2_slackdce.txz installed.

----------------------------------------------------
 automover has been installed.
 Version: 2026.03.19.01
----------------------------------------------------

⚠️

If you were on version 2025.12.15.04 or earlier, reconfigure your schedule in Settings → Automover


⚠️ It's suggested to disable unraids built in mover schedule at settings > scheduler this requires unraid 7.2.1+

plugin: automover.plg installed
Executing hook script: CA_postHook
Clearing Community Applications plugin cache
Executing hook script: post_plugin_checks
Plugin installed


image.png

Edited by animeking1987

  • Replies 156
  • Views 8.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • unraid doesn't make this easy to do because to do so you have to hijack the native mover entirely and the other complication is for when users have the mover tuning plugin which already hijacks the na

  • that's how the new version i put out the other day does it actually :) so if you are on the newest version then that's how it'll work for ya

  • Thank you. Logs cleared, will check it in the AM. Much better :) Automover session finished - 2025-11-12 06:00:01 Duration: 0s Usage below threshold — nothing to do cache usage: 1% Threshold:75% Stop

Posted Images

@jcofer555 I asked copilot to help me look into the issue and it says it found the reason for the error im seeing:

Subject: Automover CSRF Token Bug in Unraid 6.12+ (save_settings.php returns empty response)

Hi, I’ve identified a CSRF‑related issue in Automover on Unraid 6.12+ that causes both:

Code

/plugins/automover/helpers/save_settings.php
/plugins/automover/helpers/schedule_create.php

to fail with:

Code

webGUI: error: wrong csrf_token

This results in the UI returning an empty response when saving settings.

Root Cause

The CSRF token detection in Automover.page uses:

js

let csrf = "<?= $_SESSION['csrf_token'] ?? $_GET['csrf_token'] ?? $_COOKIE['csrf_token'] ?? '' ?>";

Unraid 6.12+ no longer exposes CSRF tokens through session, GET, or cookies. As a result, the frontend sends no CSRF token, and the backend rejects every request.

Correct Fix

Unraid now exposes the token globally as:

js

csrf_token

So the CSRF block in Automover.page should be replaced with:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

After applying this change, both helper scripts accept the token correctly and settings save normally.

If you need the full file or want me to test a patched build, I’m happy to help.

Thanks for maintaining this plugin — it’s incredibly useful.

  • Author
1 hour ago, animeking1987 said:

I updated the plugin. tried to schedule it, pressed schedule and same error: schedule_create.php returned an empty response — check the PHP file for errors

Downloading plugin
plugin: installing: automover.plg
Executing hook script: CA_preHook
Clearing Community Applications plugin cache
Executing hook script: pre_plugin_checks
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ...
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... 89%
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... 100%
plugin: downloading: jdupes-1.30.0-x86_64-2_slackdce.txz ... done

plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ...
plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ... 100%
plugin: downloading: libjodycode-4.0.1-x86_64-2_slackdce.txz ... done

plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ...
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 5%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 11%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 17%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 23%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 29%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 35%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 41%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 47%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 53%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 59%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 65%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 71%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 77%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 83%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 89%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 95%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... 100%
plugin: downloading: unraid-automover-2026.03.19.01-noarch-1.txz ... done


+===================================================================================================+
| Installing new package /boot/config/plugins/automover/unraid-automover-2026.03.19.01-noarch-1.txz |
+===================================================================================================+

Verifying package unraid-automover-2026.03.19.01-noarch-1.txz.
Installing package unraid-automover-2026.03.19.01-noarch-1.txz:
PACKAGE DESCRIPTION:
Package unraid-automover-2026.03.19.01-noarch-1.txz installed.

+===========================================================================================+
| Installing new package /boot/config/plugins/automover/jdupes-1.30.0-x86_64-2_slackdce.txz |
+===========================================================================================+

Verifying package jdupes-1.30.0-x86_64-2_slackdce.txz.
Installing package jdupes-1.30.0-x86_64-2_slackdce.txz:
PACKAGE DESCRIPTION:
# jdupes (identifying and taking action upon duplicate files)
#
# jdupes is a program for identifying and taking actions upon duplicate
# files.
#
# This fork of fdupes known as 'jdupes' is heavily modified from and
# improved over the original.
#
# https://github.com/jbruchon/jdupes
#
Package jdupes-1.30.0-x86_64-2_slackdce.txz installed.

+===============================================================================================+
| Installing new package /boot/config/plugins/automover/libjodycode-4.0.1-x86_64-2_slackdce.txz |
+===============================================================================================+

Verifying package libjodycode-4.0.1-x86_64-2_slackdce.txz.
Installing package libjodycode-4.0.1-x86_64-2_slackdce.txz:
PACKAGE DESCRIPTION:
# libjodycode (library for tools like jdupes)
#
# libjodycode is a software code library containing code shared among
# several of the programs written by Jody Bruchon such as imagepile,
# jdupes, winregfs, and zeromerge.
#
# https://github.com/jbruchon/libjodycode
#
Executing install script for libjodycode-4.0.1-x86_64-2_slackdce.txz.
Package libjodycode-4.0.1-x86_64-2_slackdce.txz installed.

----------------------------------------------------
 automover has been installed.
 Version: 2026.03.19.01
----------------------------------------------------

⚠️

If you were on version 2025.12.15.04 or earlier, reconfigure your schedule in Settings → Automover


⚠️ It's suggested to disable unraids built in mover schedule at settings > scheduler this requires unraid 7.2.1+

plugin: automover.plg installed
Executing hook script: CA_postHook
Clearing Community Applications plugin cache
Executing hook script: post_plugin_checks
Plugin installed


image.png

i've pushed another update if you can see if it fixes it for you

2 hours ago, jcofer555 said:

i've pushed another update if you can see if it fixes it for you

Hey, thanks for pushing the update. I tested the new version, but the issue is still happening.

After updating, both helper scripts still fail with:

Code

schedule_create.php returned an empty response

And the syslog still shows:

Code

webGUI: error: /plugins/automover/helpers/schedule_create.php?csrf_token= - wrong csrf_token

I checked the updated files, and the problem is still in Automover.page.

The CSRF token detection block is unchanged:

js

let csrf = "<?= $_SESSION['csrf_token'] ?? $_GET['csrf_token'] ?? $_COOKIE['csrf_token'] ?? '' ?>";

Unraid 6.12+ no longer exposes CSRF tokens through session, GET, or cookies, so this always evaluates to an empty string. That means the frontend sends no CSRF token, and both helper scripts reject the request.

The correct way to get the token in Unraid 6.12+ is:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

Once this is updated in Automover.page, both save_settings.php and schedule_create.php work normally again.

Happy to test another build if needed.

  • Author
2 hours ago, animeking1987 said:

Hey, thanks for pushing the update. I tested the new version, but the issue is still happening.

After updating, both helper scripts still fail with:

Code

schedule_create.php returned an empty response

And the syslog still shows:

Code

webGUI: error: /plugins/automover/helpers/schedule_create.php?csrf_token= - wrong csrf_token

I checked the updated files, and the problem is still in Automover.page.

The CSRF token detection block is unchanged:

js

let csrf = "<?= $_SESSION['csrf_token'] ?? $_GET['csrf_token'] ?? $_COOKIE['csrf_token'] ?? '' ?>";

Unraid 6.12+ no longer exposes CSRF tokens through session, GET, or cookies, so this always evaluates to an empty string. That means the frontend sends no CSRF token, and both helper scripts reject the request.

The correct way to get the token in Unraid 6.12+ is:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

Once this is updated in Automover.page, both save_settings.php and schedule_create.php work normally again.

Happy to test another build if needed.

new build out if you could test please

6 hours ago, jcofer555 said:

new build out if you could test please

The update didn’t fix the CSRF issue.

I checked the updated Automover.page, and the CSRF block is still using multiple fallback methods:

  • parent.csrf_token

  • window.csrf_token

  • cookies

  • meta tags

  • PHP session / GET / cookie

None of these work in Unraid 6.12+, so csrf is always empty.

This means the frontend still sends no CSRF token, and both:

Code

save_settings.php
schedule_create.php

continue to fail with:

Code

wrong csrf_token

The correct Unraid 6.12+ method is simply:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

Once this is used, the helper scripts accept the token and the plugin works normally.

Happy to test another build.

Edited by animeking1987

Here is the patch that fixes the CSRF issue in Automover on Unraid 6.12+.

The current CSRF logic in Automover.page tries multiple fallback methods:

  • parent.csrf_token

  • window.csrf_token

  • cookies

  • meta tags

  • PHP session / GET / cookie

None of these work in Unraid 6.12+, so csrf is always empty. As a result, both save_settings.php and schedule_create.php return:

Code

wrong csrf_token

The correct method is simply:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

Unraid injects csrf_token globally into every page.

Here is the exact patch:

Code

--- a/Automover.page
+++ b/Automover.page
@@ -1,20 +1,7 @@
 <script>
 'use strict';
 const A_H='/plugins/automover/helpers',A_F=1000,A_S=1000;
-let csrf = '';

-try {
-  if (typeof parent !== 'undefined' && parent.csrf_token) {
-    csrf = parent.csrf_token;
-  }
-  if (!csrf && typeof csrf_token !== 'undefined' && csrf_token) {
-    csrf = csrf_token;
-  }
-  if (!csrf && document.cookie) {
-    const m = document.cookie.match(/(?:^|;\s*)csrf_token=([^;]+)/);
-    if (m && m[1]) csrf = decodeURIComponent(m[1]);
-  }
-  if (!csrf) {
-    const meta = document.querySelector("meta[name='csrf_token']");
-    if (meta) csrf = meta.getAttribute('content') || '';
-  }
-} catch(e) {}

-if (!csrf) {
-  csrf = "<?= htmlspecialchars($_SESSION['csrf_token'] ?? $_GET['csrf_token'] ?? $_COOKIE['csrf_token'] ?? '', ENT_QUOTES) ?>";
-}
+// Correct Unraid 6.12+ CSRF handling
+// Unraid injects csrf_token globally into every page
+let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

 const WH_SAVED={DISCORD:"<?=htmlspecialchars($settings['WEBHOOK_DISCORD']??'')?>",GOTIFY:"<?=htmlspecialchars($settings['WEBHOOK_GOTIFY']??'')?>",NTFY:"<?=htmlspecialchars($settings['WEBHOOK_NTFY']??'')?>",PUSHOVER:"<?=htmlspecialchars($settings['WEBHOOK_PUSHOVER']??'')?>",SLACK:"<?=htmlspecialchars($settings['WEBHOOK_SLACK']??'')?>"};
 const PO_SAVED="<?=htmlspecialchars($settings['PUSHOVER_USER_KEY']??'')?>";
 </script>

Once this is applied, the frontend sends a valid token and both helper scripts work normally. Happy to test the next build.

"Copilot helped me"

Edited by animeking1987

  • Author
9 minutes ago, animeking1987 said:

Here is the patch that fixes the CSRF issue in Automover on Unraid 6.12+.

The current CSRF logic in Automover.page tries multiple fallback methods:

  • parent.csrf_token

  • window.csrf_token

  • cookies

  • meta tags

  • PHP session / GET / cookie

None of these work in Unraid 6.12+, so csrf is always empty. As a result, both save_settings.php and schedule_create.php return:

Code

wrong csrf_token

The correct method is simply:

js

let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

Unraid injects csrf_token globally into every page.

Here is the exact patch:

Code

--- a/Automover.page
+++ b/Automover.page
@@ -1,20 +1,7 @@
 <script>
 'use strict';
 const A_H='/plugins/automover/helpers',A_F=1000,A_S=1000;
-let csrf = '';

-try {
-  if (typeof parent !== 'undefined' && parent.csrf_token) {
-    csrf = parent.csrf_token;
-  }
-  if (!csrf && typeof csrf_token !== 'undefined' && csrf_token) {
-    csrf = csrf_token;
-  }
-  if (!csrf && document.cookie) {
-    const m = document.cookie.match(/(?:^|;\s*)csrf_token=([^;]+)/);
-    if (m && m[1]) csrf = decodeURIComponent(m[1]);
-  }
-  if (!csrf) {
-    const meta = document.querySelector("meta[name='csrf_token']");
-    if (meta) csrf = meta.getAttribute('content') || '';
-  }
-} catch(e) {}

-if (!csrf) {
-  csrf = "<?= htmlspecialchars($_SESSION['csrf_token'] ?? $_GET['csrf_token'] ?? $_COOKIE['csrf_token'] ?? '', ENT_QUOTES) ?>";
-}
+// Correct Unraid 6.12+ CSRF handling
+// Unraid injects csrf_token globally into every page
+let csrf = (typeof csrf_token !== 'undefined') ? csrf_token : '';

 const WH_SAVED={DISCORD:"<?=htmlspecialchars($settings['WEBHOOK_DISCORD']??'')?>",GOTIFY:"<?=htmlspecialchars($settings['WEBHOOK_GOTIFY']??'')?>",NTFY:"<?=htmlspecialchars($settings['WEBHOOK_NTFY']??'')?>",PUSHOVER:"<?=htmlspecialchars($settings['WEBHOOK_PUSHOVER']??'')?>",SLACK:"<?=htmlspecialchars($settings['WEBHOOK_SLACK']??'')?>"};
 const PO_SAVED="<?=htmlspecialchars($settings['PUSHOVER_USER_KEY']??'')?>";
 </script>

Once this is applied, the frontend sends a valid token and both helper scripts work normally. Happy to test the next build.

"Copilot helped me"

it's shouldn't be a token issue, ive confirmed the token is working, if you are seeing wrong csrf_Token where are you seeing this? can you show the full console request and response

Edited by jcofer555

9 minutes ago, jcofer555 said:

it's not a token issue, ived confirmed the token is working, if you are seeing wrong csrf_Token where are you seeing this? can you show the full console request and response

Just tested both URLs:

Local GUI: https://192-168-1-75...myunraid.net/Settings/Automover Automover works perfectly — CSRF token is present and requests succeed.

Unraid Connect remote UI: https://connect.myunraid.net/server/iframe/... Automover fails with:

Code

schedule_create.php returned an empty response
wrong csrf_token

This happens because Unraid Connect loads plugin pages inside a sandboxed iframe. Inside this iframe:

  • window.csrf_token is not exposed

  • cookies are not shared

  • session data is not shared

  • iframe cannot access parent tokens

So the plugin cannot obtain a valid CSRF token, and all POST requests fail.

This appears to be a limitation of Unraid Connect, not Automover.

  • Author
1 minute ago, animeking1987 said:

Just tested both URLs:

Local GUI: https://192-168-1-75...myunraid.net/Settings/Automover Automover works perfectly — CSRF token is present and requests succeed.

Unraid Connect remote UI: https://connect.myunraid.net/server/iframe/... Automover fails with:

Code

schedule_create.php returned an empty response
wrong csrf_token

This happens because Unraid Connect loads plugin pages inside a sandboxed iframe. Inside this iframe:

  • window.csrf_token is not exposed

  • cookies are not shared

  • session data is not shared

  • iframe cannot access parent tokens

So the plugin cannot obtain a valid CSRF token, and all POST requests fail.

This appears to be a limitation of Unraid Connect, not Automover.

ok now that i have all the information i'll see what is possible

Hello,

I can no longer install Automover. It was previously installed but then removed. The following messages appear:

Downloading plugin plugin: installing: automover.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks ERROR: Missing default settings file: /usr/local/emhttp/plugins/automover/helpers/default_settings.cfg plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed

  • Author
26 minutes ago, colonia1972 said:

Hello,

I can no longer install Automover. It was previously installed but then removed. The following messages appear:

Downloading plugin plugin: installing: automover.plg Executing hook script: CA_preHook Clearing Community Applications plugin cache Executing hook script: pre_plugin_checks ERROR: Missing default settings file: /usr/local/emhttp/plugins/automover/helpers/default_settings.cfg plugin: run failed: '/bin/bash' returned 1 Executing hook script: CA_postHook Clearing Community Applications plugin cache Executing hook script: post_plugin_checks Plugin installed

fixed

I am getting below message when I run automover. Anyone know what is wrong here? It was running fine until 3/23. I must have updated it at that time and 3/22 update broke it for me. Plugin version: 2026.03.19.04 was working fine.

I tried removing and reinstalling but same issue.

Anyone have any ideas?

Autmover.sh.png

Autmover_Activity_Log.png

  • Author
5 hours ago, B_Sinn3d said:

I am getting below message when I run automover. Anyone know what is wrong here? It was running fine until 3/23. I must have updated it at that time and 3/22 update broke it for me. Plugin version: 2026.03.19.04 was working fine.

I tried removing and reinstalling but same issue.

Anyone have any ideas?

Autmover.sh.png

Autmover_Activity_Log.png

fixed in latest release i pushed just now

Good morning.

I have two cache Cache-disk and Cache (see image below.)caches-s.png

But in app only show cache.

{0F3501EB-EAA5-422A-A04E-8FF7CA30338A}.png

How to solve ?

Thanks for all.

  • Author
6 hours ago, Adriano Frare said:

Good morning.

I have two cache Cache-disk and Cache (see image below.)caches-s.png

But in app only show cache.

{0F3501EB-EAA5-422A-A04E-8FF7CA30338A}.png

How to solve ?

Thanks for all.

fix is released

hi.

so i thought this dint happen again, but it still happening.

it is leaving empty folders, eventhough i already enable cleanup

image.png
image.png

also, another thing i notice, is that if i dont enable jdupes, qbittorrent will report alot of noHL for recent torrent that just been downloaded and moved by automover.
this doesnt happen when using the built in unraid mover. i always stop qbit, run mover, and start back qbit after mover ends.
is there anything misconfigure?

Can someone please explain I/O Priority to me?

Best Efforts?

When/Why would I want to change from Normal?

Thank you.

The Activity Log search box doesn't search/filter.

Clicking the "clear" button in File Moved Log doesn't clear the log.

Would be nice to have a progress bar measuring files, size, and transfer rate, elapsed time, remaining time.

Version 2026.03.31.01

I see the Activity Log in the top right corner displaying: Last Run 1d ago.

Yet the Activity Log says (today):

Session finished - 2026-04-03 16:08:00

Duration: 0s

Usage below threshold — nothing to do

cache usage: 39% Threshold:60% Stop Threshold:0%

Plugin version: 2026.03.31.01

Session started - 2026-04-03 16:08:00

My guess is the "Last Run" only displays if 1) there was an actual move. 2) On after the run is complete.

I would expect the Last Run would be based on the start date or end date (whichever is greater), regardless if files were moved or not.

I get messages "File still in use after 10 attempts".

I would like to know if the file cannot be moved because it is being read or written.

I have large files being copied to the cache pool, which can take a long time. Is Automover aware when the file has completed being copied (no more writes), therefore won't trying to move a file off cache that is being written to?

If the problem is the file is being written to, then could we have a Age Based Filter for hours to avoid trying to move files that have not completed being written to?

Thank you.

On 3/9/2026 at 4:27 PM, ados said:

Have a feature request, option to override the file age.

Example, full threshold is 80% and minimum 1%, with file age on x number of days.

When the schedule runs it will check if space is over 80% and then move files over the set days.

However, if new files are created in high enough volume it will fill the drive with most files newer than set days.

You could turn off the age setting, but most of the time you want to keep files on the cache a while to make use of the speed and avoiding disk spin.

What I'm proposing is an overflow setting.

If when the mover runs and the disk space is over full threshold but there's no files old enough, move the oldest files until below the full threshold.

Hopefully this makes sense and isn't burdensome add.

Any thoughts on this, make sense? Good idea?

i'm just being picky here, but shouldnt this be "shown below"? haha

image.png

  • Author
On 4/3/2026 at 1:19 PM, Jaybau said:

Can someone please explain I/O Priority to me?

Best Efforts?

When/Why would I want to change from Normal?

Thank you.

only if you wanted automover when moving files to have more or less i/o priority from the system than normal.

On 4/3/2026 at 5:39 PM, Jaybau said:

The Activity Log search box doesn't search/filter.

Clicking the "clear" button in File Moved Log doesn't clear the log.

Would be nice to have a progress bar measuring files, size, and transfer rate, elapsed time, remaining time.

Version 2026.03.31.01

clear button issue fixed. progress bar would be nice. it's on my todo list but not sure how long that'd take

On 4/3/2026 at 5:47 PM, Jaybau said:

I see the Activity Log in the top right corner displaying: Last Run 1d ago.

Yet the Activity Log says (today):

Session finished - 2026-04-03 16:08:00

Duration: 0s

Usage below threshold — nothing to do

cache usage: 39% Threshold:60% Stop Threshold:0%

Plugin version: 2026.03.31.01

Session started - 2026-04-03 16:08:00

My guess is the "Last Run" only displays if 1) there was an actual move. 2) On after the run is complete.

I would expect the Last Run would be based on the start date or end date (whichever is greater), regardless if files were moved or not.

the way i see it, a "run" is one in which files were moved, i see where you're coming from and i'll consider it no guarantees i'll change it

On 4/3/2026 at 5:56 PM, Jaybau said:

I get messages "File still in use after 10 attempts".

I would like to know if the file cannot be moved because it is being read or written.

I have large files being copied to the cache pool, which can take a long time. Is Automover aware when the file has completed being copied (no more writes), therefore won't trying to move a file off cache that is being written to?

If the problem is the file is being written to, then could we have a Age Based Filter for hours to avoid trying to move files that have not completed being written to?

Thank you.

yes automover doesn't move files that are currently in use, once the files are not in use and automover runs it will then move that file

  • Author
On 4/2/2026 at 2:06 AM, i1mran92 said:

hi.

so i thought this dint happen again, but it still happening.

it is leaving empty folders, eventhough i already enable cleanup

image.png
image.png

also, another thing i notice, is that if i dont enable jdupes, qbittorrent will report alot of noHL for recent torrent that just been downloaded and moved by automover.
this doesnt happen when using the built in unraid mover. i always stop qbit, run mover, and start back qbit after mover ends.
is there anything misconfigure?

should be fixed in latest update

5 hours ago, i1mran92 said:

i'm just being picky here, but shouldnt this be "shown below"? haha

image.png

it's 100% a personal preference and for me i prefer it on top, you could edit the code with a userscript on array start for the schedule so that those tooltips show below not above if you'd like as an option to get it how you want

Edited by jcofer555

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.