Hey guys,

I ran in to a problem with the SMB users in unraid.

I recently updated from 6.12.9 to 7.1.4.

Till the update every file was registered to the owner nobody. Now all new files are registered to the user that creates them without access for any other user to that file.

Am i missing something ?

I attach a screenshot of that. All other files were owned by the user nobody and accessable by every user that had access right to that specific share.

Do i really have to set the permission by hand each time i create a new folder as a registered user via my windows machine?

Or is there a setting that i am missing ?

Thanks in advise please let me know if you need more information.

Edited September 19, 2025Sep 19 by BastianBayer

How are the files being created, with a container or over SMB?

Give us the screenshots of the output of these two commands:

ls -al /mnt/user/BayerNAS

ls -al /mnt/user/BayerNAS/bastian

On 9/19/2025 at 3:59 PM, JorgeB said:

How are the files being created, with a container or over SMB?

over SMB and the user that i´m logged in with is the user called bastian_nas.

On 9/20/2025 at 2:17 AM, Frank1940 said:

Give us the screenshots of the output of these two commands:

ls -al /mnt/user/BayerNAS

ls -al /mnt/user/BayerNAS/bastian

and

Edited September 22, 2025Sep 22 by BastianBayer

You see that "+" in the permissions. That means that there are addition permissions on those files/directories using Access Control Lists (ACL). Here is a couple of links explaining what is going on:

https://www.linuxquestions.org/questions/linux-newbie-8/what-is-in-drwxrwxrwx-915243/

and

https://forums.unraid.net/topic/116389-access-denied-printer-unraid-share/?tab=comments#comment-1059803

You can find more information by googling "ACL permissions in Linux"

I believe the permissions can be fixed on your Unraid by running the New Permissions tool against the share with the problem. But you will still have to figure why that client is setting the ACLs in the first place. (I believe that Clients using Active Directory can set ACLs... Basically, never use Windows to control permissions on an Unraid share to set permissions on a Linux file system you know exactly why you need to do so!) )

Edited September 22, 2025Sep 22 by Frank1940

Files copied over SMB should always use nobody, unless you are using AD instead of workgroup.

16 minutes ago, JorgeB said:

Files copied over SMB should always use nobody, unless you are using AD instead of workgroup.

It has been my experience (using workgroup) that if you have login for your Windows 11 pro clients, these are the permissions that you get:

The user 'nobody' was a file written before I moved to a secured environment. 'user' and 'smbuser' are the two user profiles that I use for my clients to log into my Unraid server. Since these are actually Linux logins, LimeTech has set up these users as being members of the group 'users'. So all three (nobody, user and smbuser) have access to the files at the Linux level. Samba, of course, then controls the access via the SMB level.

IF you have questions, see this thread for more information on how I see SMB/SAMBA working:

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/

EDIT: Just realized something. You can force the user to always be ;nobody' via samba-extras file. to check for this--- run testparm on the GUI Terminal.

Edited September 22, 2025Sep 22 by Frank1940

53 minutes ago, Frank1940 said:

It has been my experience (using workgroup) that if you have login for your Windows 11 pro clients, these are the permissions that you get:

I may be wrong; I'm using a private user account and still seeing nobody, but it's from a different Windows.

Okay guys thanks for your help so far. I Checked your ideas and thought that the machine that I were using caused the ACL problem.
So I tried another machine that I use for my server that is my MacBook that is signed in to the smb share with another user just called bastian.

Here I also see after the update the same problem with the "+" for ACL.
Its the same machines that I used before performing the update and I changed nothing in either configurations..
simply creating a user that is called nobody with access to all shares is no option for me..

For now I have to run the new permissions tool every night.. and that's absolutely disgusting
And I also have seen that files in an other share that are created via the UrBackup Docker container are also with the wrong permissions after the update..
There the owner of the files is still nobody but the permissions are now drwxrwx---

Where is this configuration coming from ?

Edited September 28, 2025Sep 28 by BastianBayer

1 hour ago, BastianBayer said:

simply creating a user that is called nobody with access to all shares is no option for me..

Don't even try this! 'nobody' is a special user to to the Linux OS. (Don't ask me about this as it it beyond me. If you want to know more, Google is your friend to ask.)

1 hour ago, BastianBayer said:

And I also have seen that files in an other share that are created via the UrBackup Docker container are also with the wrong permissions after the update.

See these posts:

https://forums.unraid.net/topic/71764-support-binhex-krusader/page/38/#findComment-1486740

and

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

Sorry I am going to be an infrequent visitor to the forum over the next few weeks. So I will not be able to provide much more help than this. Real Life is coming for a extended visit...

3 minutes ago, Frank1940 said:

Don't even try this! 'nobody' is a special user to to the Linux OS. (Don't ask me about this as it it beyond me. If you want to know more, Google is your friend to ask.)

Don't worry this was just a comment and I will never do something like that.

4 minutes ago, Frank1940 said:

See these posts:

https://forums.unraid.net/topic/71764-support-binhex-krusader/page/38/#findComment-1486740

and

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

I will have a look on this thanks!

5 minutes ago, Frank1940 said:

Sorry I am going to be an infrequent visitor to the forum over the next few weeks. So I will not be able to provide much more help than this. Real Life is coming for a extended visit...

That's not a problem thanks for your help. normally I should be writing my bachelor documentation right now :D but that not working anymore is triggering me..

3 minutes ago, BastianBayer said:

and

https://forums.unraid.net/topic/188600-share-permissions-changed-to-owner-99/#findComment-1540351

Ive already checked that and the configuration of my docker seems also fine. As I said it worked for nearly 2 years now till the update to 7.1.4
UID 99 and UMASK 000 is set in the config of my dockers and that hasn't changed and was up and running for two years.

Anyone any ideo how to fix this ? Otherwise i will rollback to 6.12.9 because running the permission tool everyday seems pretty dumb.

I have also seen that in my time machine backup share the files that are created after my Unraid OS update are also not owned by nobody. The are owned by the user that i logged in to the smb.
There i have done absolutely no changes that has just gone on and on. I am completely at a loss i have checked all release notes again and still dont know what could cause that shit

Edited October 6, 2025Oct 6 by BastianBayer

On 9/22/2025 at 4:36 PM, Frank1940 said:

IF you have questions, see this thread for more information on how I see SMB/SAMBA working:

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/

For your information i had configured my SMB exactly like it is discribed here

I am sorry I don't have time right now to work with you.

Read this post again:

https://forums.unraid.net/topic/193625-after-update-from-6129-to-714-folders-in-files-in-user-shares-are-only-accessable-as-the-user-that-created-them/#findComment-1579898

Any time your find permissions that are not 777 for directory (666 for files) and the group not being users there is problem with the process that is 'asking' Unraid to create the resource. ACL permissions are not required by Unraid Samba to work in the Workgroup mode and often cause problems. (I have never used the Microsoft Active Directory (AD) environment so I don't know what happens there.)