Hi all,

 

I noticed this happened when I first updated to the RC2 release of Unraid 7, but it seems like mover isn't working.  Looking at the mover log, I get the message that it stopped immediately, and gave the message "<disk_name> must match pattern 'disk[0-9]*'".  I'm not sure what's going on here, and I've never had such an issue before.

Syslog attached.

alexnas-diagnostics-20250111-1207.zip

Try removing the Mover Tuning plugin and then trying again.

21 hours ago, itimpi said:

Try removing the Mover Tuning plugin and then trying again.

Yup, that's what did it.  Thanks!

I am also having the same issue, but I have removed the plugin, and still not moving files off my cache pools please help! Unraid 7.0.

tower-diagnostics-20250112-1715.zip

12 minutes ago, Madman2012 said:

I am also having the same issue, but I have removed the plugin, and still not moving files off my cache pools please help! Unraid 7.0.

tower-diagnostics-20250112-1715.zip 226.78 kB · 0 downloads

What shares are these?     You have a couple of shares (appdata, system) that have files split between pool and array but have the wrong settings to get files moved to the array and these seem to be the only ones that have files on a pool that probably should not be there (although most people want these on a pool to maximise performance).

appdata and system are the two biggest offenders but there are a few more like downloads that appear to be stuck on the cache drive. I wanted to upgrade the cache nvme drive to a larger one so I set it to move to the array but it will not move the files back to the array so I can upgrade the capacity of the drive.

On 1/11/2025 at 12:23 PM, itimpi said:

Try removing the Mover Tuning plugin and then trying again.

Did not work for me.

5 hours ago, Madman2012 said:

a few more like downloads that appear to be stuck on the cache drive.

That share is configured to use cache=no, so the mover won't touch it.

I don't know if this is helpful to others or the root cause of the issue.  

 

When I tried to run mover from the command line, it shows error related to the /usr/local/sbin/move command.  Sure enough, the file at /usr/local/sbin is a link to itself.   At least on my recently upgraded 6.12 to 7.0 release of unRAID.

 

Haven't tried resolving mine yet, figured I'd throw this out there before I start up my testing box and see about resolving the link to itself.

 

Hope this information does not help than harm, my issue might be unrelated or it might be directly related. 

 

unRAID01:/mnt/disk1# mover start -e disk2
/usr/local/sbin/move does not exists, creating soft link
ln: failed to create symbolic link '/usr/local/sbin/move': File exists
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory
/usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 250: /usr/local/sbin/move: No such file or directory

 

 

unRAID01:/mnt/disk1# ls -al /usr/local/sbin/move
lrwxrwxrwx 1 root root 19 Jan 18 12:24 /usr/local/sbin/move -> /usr/local/bin/move

20 minutes ago, Robert Annetta said:

I don't know if this is helpful to others or the root cause of the issue.

Uninstall the mover plugin and retest.

Thank you!   Figured out what was going on.  Appears there are two Mover Tuning plugins.  The one I had installed hasn't been updated in over a year, the other one mentioned being updated to support 7.0 in September.  Uninstalled the one and installed the one with a newer release day.  Instantly resolved mover issues.

 

Hope this helps other running into an issue with Mover.  Might be worth figuring out who maintains the Fix Common Problems to detect the version that hasn't been updated in over a year and highlight the use of the other one.  The other version was always up to date, because there wasn't a newer version than the 2023 version for that one.

 

@Squidis the older version still relevant?

Thank you, removing the plugin and reinstalling did the trick.

I was wrong, mover is not working on both my servers since upgrading to version 7. Still looking into what the issue is.

Attach DIagnostics to your NEXT post in this thread.

Fixed it, my share / cache / array settings got changed around with the upgrade.

Just wanted to pop in and say, for anyone that does not have the plugin installed, and is still seeing the issue, this fixed it for me:

The .cfg files in the /boot/config/shares directory did not match my shares config in the GUI. Must have renamed them at some point

Edited January 27, 20251 yr by Kris6673

Thanks, this solved my issue. did not realise myself there was two versions

 

On 1/19/2025 at 9:59 PM, Robert Annetta said:

Thank you!   Figured out what was going on.  Appears there are two Mover Tuning plugins.  The one I had installed hasn't been updated in over a year, the other one mentioned being updated to support 7.0 in September.  Uninstalled the one and installed the one with a newer release day.  Instantly resolved mover issues.

 

Hope this helps other running into an issue with Mover.  Might be worth figuring out who maintains the Fix Common Problems to detect the version that hasn't been updated in over a year and highlight the use of the other one.  The other version was always up to date, because there wasn't a newer version than the 2023 version for that one.

 

 

Edited January 29, 20251 yr by Rittzy

On 1/23/2025 at 5:26 PM, Lebowski said:

Fixed it, my share / cache / array settings got changed around with the upgrade.

This is what happened with mine. Instead of Cache -> Array like it was before upgrading to 7.0.0, it showed "circle icon" -> Array. I had to go back in to each share and change the primary storage to Cache and re-add array as a secondary storage. It is like the upgrade didn't copy over my share settings correctly.

Removing mover tuning plugin fixed it for me. Did anyone re-install it? I don't think I was really using it. 

On 1/31/2025 at 10:40 PM, theplexguy605 said:

This is what happened with mine. Instead of Cache -> Array like it was before upgrading to 7.0.0, it showed "circle icon" -> Array. I had to go back in to each share and change the primary storage to Cache and re-add array as a secondary storage. It is like the upgrade didn't copy over my share settings correctly.

Thanks for this, had happened to me too after I upgraded to 7.0.0 the day before yesterday and couldn't work out what had changed to stop my disks spinning down. Is there a list anywhere of what other settings get reset in an upgrade, as I've noticed a couple of other things too?

Worked for me unistalling mover tuning thankyou very much 

just found some dockers not responding and realized cache drive full. uninstalling mover tuning helped me out, thank you.

it didnt work for me removing the mover tuning

4 hours ago, Albahttiti said:

it didnt work for me removing the mover tuning

Enable mover logging, run the mover, post the diagnostics and the share names you expect to be moved.