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.

[SOLVED] Another Mover Post

Featured Replies

I've read all the posts I can find about mover not moving from Cache (pool) to Array, none helped.

I have Cache as a SSD Pool and Array as 1 HDD. I'm trying to move all of my data from Cache to Array so I can reformat the Cache as zfs (taking advantage of a lull in user demand). However it moved only 32 GB (the ISOs user share) of the 3.22 TB of data and then stopped. VM and Docker services are both disabled. I have invoked manual Move (Main > Move button) 3 time since but no change. All shares in User Shares are set to Array (high-water). I've attached screenshots of Shares and Main screens and the diagnostics file.

What possible problems could crop up if I move these shares myself via command line?

Is it possible that the manual mover isn't doing anything because the move schedule is for 3:30 am and it's currently daytime? I didn't see anything about this in known issues for 7.1.x.


The array drive has some SMART errors - Unraid doesn't have logic that prevents the mover from moving to a drive with SMART errors right? This is a calculated risk and have made this decision based on how much I care about the data. I'll be replacing the Array drive soon enough.

Main showing array, pool, boot.jpg

User and Disk Shares.jpg

metaverse-diagnostics-20250621-0924.zip

Edited by gusgus

Solved by Faceman

  • gusgus changed the title to Another Mover Post
  • Author

I'm currently trying to move the data myself with rsync:
rsync -rltgoDhUHX --remove-source-files --info=progress2 --verbose /mnt/cache/ /mnt/disk1/

  • Solution

if the shares are set to "array" only the mover wont do anything, even though there are files in /mnt/cache/share it ignores them.

You need to set the shares to Cache>Array, so set primary as cache, secondary as the array, then the mover action to cache>array, then the mover knows it needs to clear the cache. now when you force run the mover it will notice there are files to be moved.

You CAN move them manually, but you need to ensure everything goes to the right spot and you are writing INTO the folders and not overwriting them, and you need to maintain permissions.

I would recommend not using --remove-source-files until you have copied everything and verified it is all good then format the disk. just in case something goes wrong.

  • Author

Yes this was it, I didn't configure the shares correctly!

For future readers, the solution is:
1. Go to Shares tab
2. Click on each share and choose Array or Cache to indicate where they should reside.
3. Once done, go to Main, scroll to the bottom, and click on Move. The folders will move between /mnt/disk1 and /mnt/cache but will universally be available at /mnt/user no matter where they are.

Edited by gusgus

  • gusgus changed the title to [SOLVED] Another Mover Post

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.