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.

[Unraid 7.0.1] Mover not actually running, cache drive nearly full

Featured Replies

Hello all,

 

I am not sure when this started, but I noticed my cache drive was full, and the mover no longer seems to work (scheduled or manual).

 

Attaching my syslog and diags. I hate to be so vague in the post but I don't see any error that seems relevant in the syslog, at least to a layman like myself.

 

Thank you as always.

min-syslog-20250318-1519.zip min-diagnostics-20250318-1020.zip

Solved by JorgeB

  • Community Expert

Enable the mover logging, run the mover, post new diags and the share name(s) you expect to be moved.

  • Author

disabled mover logging, set it to monthly, applied. 
enabled mover logging, set to to daily, applied.
hit "move now". Doesn't appear to have done anything.

I would expect it to move everything in the following directories currently holding what should be temporary data on the cache drive to their array shares:

 

Backups\*.*
Distributed Backups\*.*
Plexmin\*.*
UsenetIncoming\*.*

 

there is roughly 200gb or so of data just hanging out there.

 

I attached my syslog and diags again but to save you a search:

 

Mar 18 10:57:10 Min emhttpd: shcmd (166): /usr/local/sbin/update_cron Mar 18 10:57:33

Min emhttpd: shcmd (169): /usr/local/sbin/update_cron Mar 18 10:57:53

Min emhttpd: shcmd (170): /usr/local/sbin/mover start |& logger -t move & Mar 18 10:57:53

Min move: mover: started Mar 18 10:57:53

Min move: mover: finished Mar 18 10:58:51 Min emhttpd: shcmd (171): /usr/local/sbin/mover start |& logger -t move & Mar 18 10:58:51

Min move: mover: started Mar 18 10:58:51 Min move: mover: finished

 

Thank you again for your swift responses Jorge, I really appreciate you!
 

min-syslog-20250318-1604.zip min-diagnostics-20250318-1103.zip

  • Community Expert
  • Solution
28 minutes ago, Ouze said:

UsenetIncoming\*.*

This is one is set to cache=only, so you would need to adjust the settings, the other shares are correctly set to cache=yes, but there's no pool specified, still not sure why this only sometimes happens, but it should still work, and it doesn't for some, go to those shares, set primary=cache, secondary=array, apply the settings, if they already show like that, make a dummy change so that you can click apply, and retest.

  • Community Expert

Set each of those shares to Primary:cache; Secondary:array; Mover action:cache->array

 

and try again.

  • Author

Thank you both. I didn't mess with this so not sure how this happened, but easy enough to fix. 

 

I really, really appreciate being able to come here and fix stuff within like, 2 hours. :) 

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.