I have recently upgraded my UnRAID server to 5.0.5 from 4.7, in part to resolve some disc issues I was having.  After the initial migration I was able to see my disc shares via Windows Explorer using either the mapped drive letters or under the Network > Tardis subtree.  I was able to open the shares and view the directories and files under each share.

 

I have been running a preclear on a new drive to replace my Parity drive but have not yet swapped them.  The only other change I have made since the upgrade is to set a password on the Root account as there was none defined by default.  I do not have any other user accounts defined, same as my old 4.7 setup.

 

I have tried opening a few shares tonight and I'm getting either "access denied" or "you do not have permission" depending on what method I'm using to try opening them (either the mapped drive letter or directly navigating to the share under the Network tree).

 

In trying to resolve this I have tried opening the Shares tab on the UnRAID GUI and checked that all the share permissions are set to public, have even tried re-applying all the share settings.  I have also tried disconnecting each mapped drive and re-connecting it.  Lastly I have tried rebooting both my workstation and the UnRAID server itself.  If I try applying windows permissions from Windows Explorer to the group "everyone" I get the "access denied" message.

 

Is there something I have missed?  Should I be setting the Windows permissions to the group "Users" (Unix Group\Users) instead?  I can't understand why they were working before.

Have you run the 'New permissions' utility.  That is one of the required steps in the 4.7 to 5.x upgrade process to get the permissions right for the 5.x security model.

No I haven't run that utility, I had followed the tutorial instructions in the Wiki here :- http://lime-technology.com/wiki/index.php/Migrating_from_unRAID_4.7_to_unRAID_5.0

 

I have gone back to the 5.0-beta Release Notes linked in that tutorial and can see it noted there, must have overlooked it the first time I read them.  I will give that a try now.

 

UPDATE:  I think it has completed OK :-

 

/usr/local/sbin/newperms

processing /mnt/cache

... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/cache

... chown -R nobody:users /mnt/cache

... sync

processing /mnt/disk1

... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk1

... chown -R nobody:users /mnt/disk1

... sync

processing /mnt/disk2

... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk2

... chown -R nobody:users /mnt/disk2

... sync

processing /mnt/disk3

... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/disk3

... chown -R nobody:users /mnt/disk3

... sync

completed, elapsed time: 00:05:31

 

OK, have done some spot checks and the shares seem to be working OK now.  Do I need to go back and re-apply permissions on the Windows side as well?

 

I also noticed this in the Release Notes as the last step in the upgrade process :-

 

"Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication."

 

I only have a Root user defined currently which I know is not ideal from a security point of view but it has worked in the past.  Since my shares are all set to Public anyway do I even need to create any additional users?

"Go to Users page and re-enter all of your users. If you plan on using SMB and/or AFP with either Secure or Private security mode, you must enter at least one user because the 'root' user name is no longer permitted for network share authentication."

 

I only have a Root user defined currently which I know is not ideal from a security point of view but it has worked in the past.  Since my shares are all set to Public anyway do I even need to create any additional users?

For public shares the username is irrelevant.

For public shares the username is irrelevant.

 

OK, so it's only an issue if you plan to set security to "Secure" or "Private" then.  My UnRaid box is just a media server at present so I'm not too worried about the shares being public.  I've gone and re-applied permissions on the Windows side as well, not sure if I needed to do that in order for my Windows PCs to have full access to the UnRAID shares.

Shares seem to be all good now, marking this issue as solved.