hi long time very happy user!   Upgraded to 7.0 a couple of weeks ago.  Use Radarr, Sonarr and Sabdnzb.    Recently added a tv show for my daughter, and it began downloading 10 seasons lol.   Then next day noticed my sab queue was paused.    Noticed my cache drive almost totally full.    My setup had been to download Movies and Shows to the cache drive and have the Mover move the files to the main array each hour.   But somehow this stopped happening.   When I manually click 'move now' it starts and finishes all within one second.   When I browse the cache drive I can see tons of recently downloaded movies and the new show for my daughter, on the cache.   So I think the mover stopped moving.  logs attached.

 

Any advice?

tower-diagnostics-20250123-2026.zip

Edited January 24, 20251 yr by grither
corrected log files

Following this as I'm also having this problem. I've tried with and without the *new* CA Mover Plugin. Unraid 7.0. Logs attached with mover logging enabled after a clean reboot. The log would show the same that grither was having before turning on logging. Would start and stop within seconds. After rebooting and turning on the logger, it's moving some files, but only 61GiB worth. If I run the mover again after running it, it'll "move" those files again. 

 

The #1 thing that catches my attention are that it states that a share does not exist, but it does exist and is tower-diagnostics-20250124-0116.zipmy main share with all data on it (kirby). 

 

Logs attached.

5 hours ago, grither said:

When I browse the cache drive I can see tons of recently downloaded movies and the new show for my daughter, on the cache.   So I think the mover stopped moving.  logs attached.

What is the share name you expect to be moved?

1 hour ago, waggs15 said:

my main share with all data on it (kirby). 

The problem I think is that it looks like you have share  configuration files with the same name but different capitalisation

K---y                             shareUseCache="yes"     # Share does not exist
k---y                             shareUseCache="no"      # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6, disk7, disk8, disk9, disk10

 

Linux is case sensitive whereas Samba is not so when this happens then you cannot be sure which configuration file will be used for the share.

 

You should first delete from the 'shares' folder on the flash drive the one that does not correspond to the capitalisation of the share folder on your data drives.   After doing that check the settings for the share are as you want them to be.

Jeeze I'm dumb. I knew about capitalization on Linux, but was looking past that. Thank you for the help with my problem, things are moving now. 

I'll let you get back to helping OP with their problem.

3 hours ago, JorgeB said:

What is the share name you expect to be moved?

The share that uses the cache and mover is called "Media"

 

That share is set to cache=yes, but there's no associated pool, click on that share and reapply the settings, make a dummy change if needed, then post new diags.

thanks, I added a comment and then hit apply.    here's the new diagnostics

 

appreciate the help!

tower-diagnostics-20250124-0642.zip

Share now is set to array only, so you need to correct the settings.

The share settings are wrong for mover to take action.   You need:

• primary storage set to cache
• secondary storage set to array
• mover direction set as cache->array

if a share does not have both primary and secondary storage set then mover will ignore it.

ok thank you, made the changes as you described (thanks for being so specific!)

 

here's a snip of the new share settings and new diagnostics

 

and Mover shows as running!   Yay!

tower-diagnostics-20250124-0658.zip