tojoski

Can confirm this is fixed after applying the patch. Thanks!

Confirmed above is the issue: I made a share called "test share" and the mover doesn't work

Ok so we may be getting somewhere. I made a share called "test" on the array, copied some data to it, then went in and set it to my zfs array (primus) and ran the mover. It ran fine, created the dataset and copied the data. The only thing I can guess is the mover in v7 has an issue with spaces in the share names? As far as I can see that's the only difference between the "TV Series" share and the "test" share.

I did some more testing and it seems this only affects moving data to the zfs dataset. I copied some data to my cache drive, then invoked the mover and it copied it to the array fine. Jan 10 20:35:22 Orientis emhttpd: shcmd (55124): /usr/local/sbin/mover start |& logger -t move & Jan 10 20:35:22 Orientis move: mover: started Jan 10 20:35:22 Orientis move: move: /mnt/cache/Company/Shares.PNG Success Jan 10 20:35:22 Orientis move: move: /mnt/cache/Company/Shares2.PNG Success Jan 10 20:35:22 Orientis move: mover: finished

I have been unable to find a solution as of yet; I don't have any plugins installed that affect the mover to my knowledge.

Upgraded to v7 without issue but ran into an issue trying to use mover. I have a traditional array as well as a ZFS pool (Primus) that I have been moving data to slowly. I have previously moved two or my shares using this method but either I am missing something or this is broken now. I am attempting to move data from Array > Primus, I have Primus set as the primary storage and the Array set as secondary, mover action is set to move from secondary to primary. The log shows: Jan 10 08:01:00 Orientis emhttpd: shcmd (49582): /usr/local/sbin/mover start |& logger -t move & Jan 10 08:01:00 Orientis move: mover: started Jan 10 08:01:00 Orientis move: mover: finished I am not using the "mover tuner" plugin nor can I remember ever using it. Edit: forgot to mention the share name: TV Series orientis-diagnostics-20250110-1002.zip

Upgraded last night but the mover isn't working. Seemed to be a common issue with the beta with the mover tuner plugin but I am not using that plugin. The log shows: shcmd (45584): /usr/local/sbin/mover start &> /dev/null &

Yes, both of them. It's just frustrating. Creating a user account on Unraid to match the account on the Windows 10 box is not a great solution. And since its a Microsoft account, I don't think it's even possible on the Unraid side.

Recent convert from a Server 2016 Essentials server to Unraid and I am getting the "Multiple connections to a server or shared resource by the same user, using more than one user name are not allowed" issue on my password-protected share. This wasn't an issue with the shares on the 2016 Essentials box. I could authenticate to a share using domain\user even though I sign into my PC as a Microsoft account and I wasn't joined to AD. Interestingly, if I change the permissions on the share from read/write to read-only, then back to read/write, I can authenticate and get access once, then back to the error.

Recent convert from a Server 2016 Essentials server to Unraid.. this wasn't an issue with the shares on that box, but for some reason is with samba? I could authenticate to a share using domain\user even though I sign into my PC as a Microsoft account and I wasn't joined to the domain. Interestingly, if I change the permissions on the share from read/write to read-only, then back to read/write, I can authenticate and get access once, then back to the error. EDIT: Just realized that this thread was super old.. Issue still exists on current version though,