I am trying to fix permissions of one folder on my cache disk. I called it "permission". It is weird though as the task (tools / new permissions / target:shares / items:permission) and it completed. However, the permissions didn't change.

Permission folder is still "drw-rw-rw- / nobody". The folders within are either "drw-rw-rw- / nobody" or "drw-rw-rw- / myusername".

Any idea why this is happening and what I can do to fix? Helpful to send diagnostic log?

I already rebooted Unraid, but no change.

First, please post up the diagnostics file in a NEW post in this thread. (Otherwise, we receive no notification that you have responded with additional information!)

Next, either name the share that has the problem or give us the first and last letter of the Share with the issue.

The share is called "permission". Please see diagnostic attached. Thanks for your help!

tower-diagnostics-20251123-2347.zip

You might want to make the share settings match its location:

p--------n shareUseCache="no" # Share exists on cache

In addition to what @itimpi saw, when I looked at the tower-diagnostics-20251123-2347\system\testparm.txt file which is the output of a Samba diagnostics tool, I saw that the "permission" share was not in the list of shares that Samba was servicing. You need to open up that share under SHARES on the GUI and on its settings page, set it for access by whatever sharing protocols you need. (I believe the default permissions for any new share is for no access--- period!)

6 hours ago, itimpi said:

You might want to make the share settings match its location:

p--------n shareUseCache="no" # Share exists on cache

Thanks. Where do I do that? Commandline?

18 minutes ago, steve1977 said:

Thanks. Where do I do that? Commandline?

HERE:

There is a help for each setting which can be toggled by clicking on the description:

Make sure that "Minimum free Space" (top figure) is set to be a bit larger than the largest size file that will ever be written to the share.

Thanks. That's exactly how it it shows in my settings.

To be precise, the export wasn't enabled, but I did so after your commnent. Didn't change anything though.

I still cannot access in Windows any of the files in this folder / share. And the permissions are inconsistent (see my opening email).

Now go to TOOLS >>> New Permissions then Select Shares' as the Target

Then open the dropdown box and click only the 'Permission' share. (Do not select any other share unless you have problem. READ the cautions for the reasons why you don't want willy-nilly be doing things!)

'

Thats's exactly what I did and yet again did just now. That's why I am so confused that nothing is changing although it says it completes.

When you did the checking on my earlier about where to set up where things are stored, Change an item and click the 'APPLY' button  to make sure they are actually set.  

If things are not working post up a new set of diagnostics and let's see what changed.

Thanks. I had applied, but just redid everything and yet again "applied". Below new diagnostic logs. What will have changed is the samba sharing (which I enabled since), but I still cannot accesss the files in Windows and the permissions are still inconsistent. The files are still there though as I can access them via the Unraid GUI.

tower-diagnostics-20251124-0803.zip

Ok. At this point, I am assuming that you have run the New Permissions script on that Share. Let's get some configuration data on your server. Below, you will find three sets of commands to run on your server. You will be using the GUI terminal. Please provide a screen capture (screenshot) of the output of each one:

ls -al /mnt

ls -al /mnt/user

ls -al /mnt/user/permission

If you can't do screenshots, please format the inserted copied text by going to the ... in the edit line of the reply editor and format that text as </> Inline Code !!!

19 hours ago, steve1977 said:

Permission folder is still "drw-rw-rw- / nobody". The folders within are either "drw-rw-rw- / nobody" or "drw-rw-rw- / myusername"

Let me give you a little bit of an explanation of what appears to be happening. The permissions for a directory should be drwxrwxrwx and the 'x' makes the the resource 'executable'. While this makes sense for a file as it might be a program (Remember Linux does not use file extensions to indicate what a file is used for), it does not seem to make sense for a directory. What t he execute bit does for a directory is to allow you to browse inside of it-- e.i. to view the contents of that directory. (IF you want more information about what is going on, google directory permissions in linux. )

Thanks. Have done it multiple times. Please see screenshots below:

Let's see the output of this one

ls -al /mnt/user/permission/

Note the forward slash at the end of the line...

total 190

drw-rw-rw- 11 nobody users 11 Nov 23 12:06 ./

drwxrwxrwx 7 nobody users 8 Nov 24 08:04 ../

drw-rw-rw- 8 nobody users 8 Nov 14 23:12 .removed/

drw-rw-rw- 3 nobody users 3 Nov 17 22:19 5\ removed

drw-rw-rw- 2 myusername users 16 Nov 23 11:55 removed\ -\ Album\ -\ 2025\ -\ removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:04 removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:04 removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:04 removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:07 removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:05 removed/

drw-rw-rw- 3 myusername users 3 Nov 23 08:05 removed/

The new permission tool doesn't work on exclusive shares; you can get around the issue by running the tool on the disk(s) the share occupies (make sure appdata is not one of those disks)

Alternatively, disable exclusive shares, run the tool on the share, re-enable it again.

Got it. This explains. The work-around works.