January 14, 20251 yr Hey all, I successfully upgraded from 6.12.14 to 7 and all seems well. However I noticed that the cache drive is getting full and when I manually run Mover, the button immediately comes back and nothing happens. Enabling mover logging or running it manually simply comes back with: Jan 14 10:25:47 Storage move: mover: started Jan 14 10:25:47 Storage move: mover: finished I tried re-configuring the share to Array only, then back to Cache-Array, but didn't make a difference. Tried stopping all dockers - no change. I don't have the mover tuner plugin installed (never have). Logs attached for reference - thanks! storage-diagnostics-20250114-1032.zip
January 14, 20251 yr Community Expert The only share that has files on the cache that look like the might be ones you want moved is: t---------e shareUseCache="no" # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6 However, that share is not configured correctly for this to happen. It needs to be configured with Primary Storage as ‘cache’. Secondary Storage as ‘array’ and mover direction as cache->array. With its current settings that share will be ignored by mover.
January 14, 20251 yr Author So it appears that the shareDisks.txt has 2 versions of a share; TimeMachine shareUseCache="yes" # Share does not exist timemachine shareUseCache="no" # Share exists on cache, disk1, disk2, disk3, disk4, disk5, disk6 Only the latter one appears in the list and I have it set to use cache (and it does), but mover doesn't move them. Can I simply remove the 1st one or will that get recreated at reboot? Or should I remove the share entirely and recreate (assuming that removing it will cause both entries to be removed?) Edited January 14, 20251 yr by jazzysmooth
January 14, 20251 yr Community Expert Solution You need to keep the one that has the same capitalisation as the folder name for that share (Linux is case sensitive whereas Samba shares are not). Then make sure the settings for the remaining one is what you want.
January 14, 20251 yr Author I used the "clean up" button and that removed the one with capitalization. Mover still didn't run, but once I stopped / started the array it now appears to be working - thank you!
January 14, 20251 yr I have a similar issue with mover; however, I'm using the mover tuning plugin. If I remove the plugin and run the normal mover manually it functions properly. Once I add it back in I get the same results. Here is the output from the tail when using mover tuning when ran manually. mvlogger: Log Level: 1 mvlogger: *********************************MOVER -SHARE- START******************************* mvlogger: Tue Jan 14 12:55:55 EST 2025 mvlogger: Share supplied media Sharecfg: /boot/config/shares/media.cfg mvlogger: Cache Pool Name: cache_ssd mvlogger: Share Path: /mnt/cache_ssd/media mvlogger: Complete Mover Command: find "/mnt/cache_ssd/media" -depth | /usr/local/sbin/move -d 1 mvlogger: Tue Jan 14 12:55:55 EST 2025 mvlogger: ********************************Mover Finished***************************** whitenoisemedia-diagnostics-20250114-1256.zip
January 14, 20251 yr Community Expert 22 minutes ago, blackbullitt said: Once I add it back in I get the same results. Please use the existing mover plugin support thread:
January 14, 20251 yr The mover tuning plugin was working prior to the upgrade to 7.0.0, that's why I'm bringing it up in this thread to help others if there is a fix action for it.
January 16, 20251 yr had this exact same problem this week, had to uninstall mover tuning to get the mover to work again, apparently they have not fixed there app for 7.0 yet, hopefully soon
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.