I'm on UNRAID version 7.0. I've had this permission issue on the share where it would tell me "you need permission to perform this action" seemly randomly when I try create a folder/file, copy over something.

But this only happens randomly sometimes, and when it does I'll just try copy/move/whatever again and it'll go through fine with no error.

 

I also have python scripts that copy/move and create folders and files to the share and it prints out "PermissionError Permission Denied" for some files so I have to put retries.

 

Though if I do any actions directly to the disk shares there's no permission issues of any kind.

 

Any ideas what could be causing this strange permission issue to flare up?

Edited March 7, 20251 yr by Hellomynameisleo

Post up your Diagnostics file in a new post.

 

Now go to Shares, click on each Disk share and tell us if the Security on them is anything but 'Public'.

 

Have you setup a Windows Credential to this server?

 

2 minutes ago, Frank1940 said:

Post up your Diagnostics file in a new post.

 

Now go to Shares, click on each Disk share and tell us if the Security on them is anything but 'Public'.

 

Have you setup a Windows Credential to this server?

 

The disk shares SMB Security Settings are all "Private" same with my user share.

 

yes, Window credentials is setup and it was setup automatically when I first connected to the server over SMB from my windows computer

 

unraid-diagnostics-20250307-2204.zip

You have only one Share "M---a" that is exported.  It appears to be a hidden share.  If this is the share with the problem, try unhiding it.  (There have been some issues at times with 'hidden' shares.) 

 

You are also sharing the 'appdata' Share.  This is considered to be a system share is normally not to used by anything but Docker containers.  If you are accessing it to get at information from one or more Docker containers, you should ask in the support thread for the container(s) as to how to map the files that it has to a standard Unraid User Share. 

11 minutes ago, Frank1940 said:

You have only one Share "M---a" that is exported.  It appears to be a hidden share.  If this is the share with the problem, try unhiding it.  (There have been some issues at times with 'hidden' shares.) 

 

You are also sharing the 'appdata' Share.  This is considered to be a system share is normally not to used by anything but Docker containers.  If you are accessing it to get at information from one or more Docker containers, you should ask in the support thread for the container(s) as to how to map the files that it has to a standard Unraid User Share. 

I don't have a share called M--a though the diagnositcs file does have this at the top "# Share does not exist" so it might be a ghost share.

 

I only have the B----p user share. This is the one that is export (hidden), I can try unhiding it but will that make a difference considering the disk shares and the same export (hidden)?

 

I'm not doing anything with my appdata just I've forgotten to hide that share,

Just for some feedback after changing the shares to export not hidden, I still get the random permission denied errors.

The appdata share has files on 13 array disks.   What is going on here?

 

Sorry about the confusion with M--a and B---p.  In jumping around looking at settings in different files, I made a mistake. 

 

So is the permission problem with the appdata share or with the B---p share?  (appdata is not exported by default....) 

 

Or are you moving files between them? 

2 minutes ago, Frank1940 said:

The appdata share has files on 13 array disks.   What is going on here?

 

Sorry about the confusion with M--a and B---p.  In jumping around looking at settings in different files, I made a mistake. 

 

So is the permission problem with the appdata share or with the B---p share?  (appdata is not exported by default....) 

 

Or are you moving files between them? 

Sorry if I didn't make it clear, yes its with the B---p share thats having the issue, possibly appdata and other shares that unraid makes by default but I don't use them myself to store stuff so I haven't tested.

I don't use the appdata really other than unraid's docker containers puts stuff in there, the files spread out on 13 array disks because of the allocation.

 

 

11 minutes ago, Hellomynameisleo said:

appdata

The files within this share in particular have their own permissions dictated by the container which creates them, and there isn't an guarantee that those permissions are compatible with exporting to Windows to any random user, and if you do happen to change the permissions within this share to make them compatible you run the risk that the containers will then have problems with accessing thing.

 

The B---p share.  What is creating the files within them?  Assuming a docker container, many containers have within their settings the ability to set what permissions to use on the files it writes (outside of appdata).  Setting it to 0777 would give full access to those files over the network

11 minutes ago, Squid said:

The files within this share in particular have their own permissions dictated by the container which creates them, and there isn't an guarantee that those permissions are compatible with exporting to Windows to any random user, and if you do happen to change the permissions within this share to make them compatible you run the risk that the containers will then have problems with accessing thing.

 

The B---p share.  What is creating the files within them?  Assuming a docker container, many containers have within their settings the ability to set what permissions to use on the files it writes (outside of appdata).  Setting it to 0777 would give full access to those files over the network

I create them like a normal user would over the network, right click create folder -> create file etc. in file explorer.

or use a python/powershell script to copy things over

Go to shares, and click the B---p share.  On it's settings, there's a number within min free space.  Change it to 1. (no suffix's or anything just 1). Don't leave the entry blank.

 

Does that fix it?  (Possible you might also have to reboot the server)

29 minutes ago, Squid said:

Go to shares, and click the B---p share.  On it's settings, there's a number within min free space.  Change it to 1. (no suffix's or anything just 1). Don't leave the entry blank.

 

Does that fix it?  (Possible you might also have to reboot the server)

I gave this a try and no luck on it fixing sadly

Then clearing the credentials on Windows in credential manager and reconnecting.   I'm assuming that the creds you're using for the shares match the username on Windows.

26 minutes ago, Squid said:

Then clearing the credentials on Windows in credential manager and reconnecting.   I'm assuming that the creds you're using for the shares match the username on Windows.

yes the creds match on what I'm using on the shares and windows account. I've did a disconnect, cleared the credentials in my windows manager and connected again, though still no luck on the pemission issue.

Did a bit more testing and found it occurs even if I create a new user share and use that the error will occur randomly still on there.

Find a file with the problem.  Then open the GUI Terminal from the Unraid GUI.  (It is the symbol on the right side of the tool bar.)  Now type this command:

ls -al "/mnt/user"

 

Now drill down to the directory with the problem and get a screenshot of the file with the problem.  (We don't need the file name itself UNLESS it has some unusual characters in its name!) Remember that Linux is case sensitive so you will have to observe upper and lower case letters as you edit/type the path.  (Remember that the BASH shell has an editor built into it so the arrow keys will recall previous commands and allow editing of those commands.)

36 minutes ago, Frank1940 said:

Find a file with the problem.  Then open the GUI Terminal from the Unraid GUI.  (It is the symbol on the right side of the tool bar.)  Now type this command:

ls -al "/mnt/user"

 

Now drill down to the directory with the problem and get a screenshot of the file with the problem.  (We don't need the file name itself UNLESS it has some unusual characters in its name!) Remember that Linux is case sensitive so you will have to observe upper and lower case letters as you edit/type the path.  (Remember that the BASH shell has an editor built into it so the arrow keys will recall previous commands and allow editing of those commands.)

I tried creating a new folder and it errors as shown.

 

But if I click try again it successfully creates the folder, this is random, you can see the new text document I created had no issues. but the folder did in this case.

 

and here it is in the terminal:

 

it happens with all files and all folders there is no pattern I see with their names copy/move/delete etc, it happens on random chance

 

 

Edited March 8, 20251 yr by Hellomynameisleo

Try adding this to smb extras under settings-SMB:

 

domain master = yes
preferred master = yes
os level = 255
force user = nobody
force group = users
create mask = 0666
force create mode = 0666
directory mask = 0777
force directory mode = 0777

 

Then try again

Edited March 8, 20251 yr by strike

I don't like it when I see this in a Unraid share:

 

This has caused problems in the past.  See here:

     https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/#findComment-1058963

 

That having been said, I see that you are using a Windows mapped drive (P:) to do these operations.  Let try it using a direct connection to your server from Windows File Manager/Explorer.  To do this, type    \\Unraid   (or     \\192.168.11.1    if that does not work) in the 'Address bar' of the Windows File Manager. (Ideally, you want to use the one that you created a Windows Credential for the Windows Credential Manager.)   Then select your 'Backup' share and try the same kind of operations from there.  

 

27 minutes ago, Frank1940 said:

I don't like it when I see this in a Unraid share:

 

This has caused problems in the past.  See here:

     https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/#findComment-1058963

 

That having been said, I see that you are using a Windows mapped drive (P:) to do these operations.  Let try it using a direct connection to your server from Windows File Manager/Explorer.  To do this, type    \\Unraid   (or     \\192.168.11.1    if that does not work) in the 'Address bar' of the Windows File Manager. (Ideally, you want to use the one that you created a Windows Credential for the Windows Credential Manager.)   Then select your 'Backup' share and try the same kind of operations from there.  

 

I'm not quite sure where the extra "+" permission came from, I've not modified the permission through the command line, just used it as any normal user would.

 

I've given the new network path a try but no luck there either, I'm still getting permission errors even without going through the mapped path.

 

Edited March 8, 20251 yr by Hellomynameisleo

1 hour ago, strike said:

Try adding this to smb extras under settings-SMB:

 

domain master = yes
preferred master = yes
os level = 255
force user = nobody
force group = users
create mask = 0666
force create mode = 0666
directory mask = 0777
force directory mode = 0777

 

Then try again

I've also given this a try, took a while since it takes a while to start my array. No luck either on this side after putting this in my SMB extra configs then starting the array and giving it a test.

1 hour ago, Hellomynameisleo said:

I'm not quite sure where the extra "+" permission came from, I've not modified the permission through the command line, just used it as any normal user would.

 

It is usually set by the user who has access to ACL (ACL = Advance Control Language, if I remember correctly).  One way to set these permissions is from Windows.  If you right-click on a file or directory (that is on the Unraid server), pick 'Properties' and then change the settings under the 'Security' tab, you can set the ACL permissions on your server.  This is more likely to happen when it is a mapped drive. 

 

If I remember correctly, the ACL permissions on Unraid can be removed by running the 'New Permissions' tool on just the share which has them.  (Observe the warning about NOT running it on the appdata share!!!!)  But I don't think that is what is causing your problem.  To be honest, I don't recall ever seeing a problem where the action fails because it is prohibited and then succeeds on a retry. 

1 hour ago, Frank1940 said:

It is usually set by the user who has access to ACL (ACL = Advance Control Language, if I remember correctly).  One way to set these permissions is from Windows.  If you right-click on a file or directory (that is on the Unraid server), pick 'Properties' and then change the settings under the 'Security' tab, you can set the ACL permissions on your server.  This is more likely to happen when it is a mapped drive. 

 

If I remember correctly, the ACL permissions on Unraid can be removed by running the 'New Permissions' tool on just the share which has them.  (Observe the warning about NOT running it on the appdata share!!!!)  But I don't think that is what is causing your problem.  To be honest, I don't recall ever seeing a problem where the action fails because it is prohibited and then succeeds on a retry. 

starting to think maybe its my windows computer. But I don't have any other computer on hand to test the connection with unfortunately

If you want to test on another windows machine you can just set up a vm. ISO is free to download and you don't need to buy a key to activate it. 

1 minute ago, strike said:

If you want to test on another windows machine you can just set up a vm. ISO is free to download and you don't need to buy a key to activate it. 

I will give this a shot. But it would be ideal to use a whole another computer to isolate any old lingering settings on the host machine that will transfer over to the VM will have to passthrough.