June 14Jun 14 After the latest update I am unable to access my Samba shares from my Linux machine I am asked for credentials which were already saved in my kwallet. I'm not sure where to look further.I tried rolling back with but seeing the same problem I verified permission of the /tmp directory and ran Docker Safe New PermsI am seeing these errors[2026/06/13 18:52:43.494866, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) chdir_current_service: vfs_ChDir(/tmp) failed: Permission denied. Current token: uid=1002, gid=100, 4 groups: 100 3003 3004 3006[2026/06/13 15:05:51.059445, 0] ../../source3/smbd/smbXsrv_session.c:1728(smbXsrv_session_remove_channel_done) smbXsrv_session_remove_channel_done: smbXsrv_session_logoff(3239775705) failed: NT_STATUS_INTERNAL_ERROR root@Odin:/var/log/samba# ls -ld /tmp drwxrwxrwt 23 root root 660 Jun 13 21:47 /tmp/What confuses me is checking smbstatus I see connections root@Odin:/var/log/samba# smbstatus Samba version 4.22.10 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 2863367 xxxxxxxxxx users heimdall (ipv4:10.103.53.50:39594) SMB3_11 - partial(AES-128-GMAC) 2863474 xxxxxxxxxx users 10.103.53.50 (ipv4:10.103.53.50:50510) SMB3_11 - partial(AES-128-GMAC) 2868150 xxxxxxxxxx users 10.103.53.50 (ipv4:10.103.53.50:36618) SMB3_11 - partial(AES-128-GMAC) 2786119 xxxxxxxxxx users 10.103.53.50 (ipv4:10.103.53.50:59616) SMB3_11 - partial(AES-128-GMAC) 2790760 nobody users 10.103.53.50 (ipv4:10.103.53.50:35744) SMB3_11 - - 2864749 nobody users 10.103.53.50 (ipv4:10.103.53.50:51088) SMB3_11 - - 2863497 xxxxxxxxxx users heimdall (ipv4:10.103.53.50:39596) SMB3_11 - partial(AES-128-GMAC) 2786389 nobody users 10.103.53.50 (ipv4:10.103.53.50:59638) SMB3_11 - - Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- IPC$ 2863497 heimdall Sat Jun 13 03:01:30 PM 2026 EDT - - IPC$ 2786389 10.103.53.50 Sat Jun 13 02:51:59 PM 2026 EDT - - IPC$ 2863474 10.103.53.50 Sat Jun 13 03:01:29 PM 2026 EDT - - IPC$ 2790760 10.103.53.50 Sat Jun 13 02:52:32 PM 2026 EDT - - IPC$ 2868150 10.103.53.50 Sat Jun 13 03:02:02 PM 2026 EDT - - IPC$ 2864749 10.103.53.50 Sat Jun 13 03:01:38 PM 2026 EDT - - IPC$ 2863367 heimdall Sat Jun 13 03:01:29 PM 2026 EDT - - Documents 2863474 10.103.53.50 Sat Jun 13 03:01:29 PM 2026 EDT - - 3D Models 2864749 10.103.53.50 Sat Jun 13 03:01:38 PM 2026 EDT - - Storage 2786389 10.103.53.50 Sat Jun 13 02:51:59 PM 2026 EDT - - backups 2868150 10.103.53.50 Sat Jun 13 03:02:02 PM 2026 EDT - - IPC$ 2786119 10.103.53.50 Sat Jun 13 02:51:57 PM 2026 EDT - - appdata 2786119 10.103.53.50 Sat Jun 13 02:51:57 PM 2026 EDT - - Documents 2790760 10.103.53.50 Sat Jun 13 02:52:32 PM 2026 EDT - - odin-diagnostics-20260613-2143.zip
June 14Jun 14 This looks to me more like an issue on the Mac side, can you browse the shares from another device, like a phone or table if you don't have a PC?
June 14Jun 14 Author 5 hours ago, JorgeB said:This looks to me more like an issue on the Mac side, can you browse the shares from another device, like a phone or table if you don't have a PC?I had several Linux servers, Macbooks ,windows laptop and a NVR that was connecting to samba shares previously all of them lost access. I even went to the cli and used "smbpasswd" and ensured all the passwords were correct for all the users.
June 15Jun 15 Author 4 hours ago, JorgeB said:Can you access the flash drive if you export that publicly?Wow I was amazed that actually worked I can access the flash share both private and public I hope that means you have an idea on whats happening to my system.root@Odin:~# smbstatus Samba version 4.22.10 PID Username Group Machine Protocol Version Encryption Signing ---------------------------------------------------------------------------------------------------------------------------------------- 2718168 nobody users 10.103.53.50 (ipv4:10.103.53.50:37690) SMB3_11 - - 2718172 nobody users 10.103.53.50 (ipv4:10.103.53.50:37738) SMB3_11 - - 2718169 nobody users 10.103.53.50 (ipv4:10.103.53.50:37702) SMB3_11 - - 2718170 nobody users 10.103.53.50 (ipv4:10.103.53.50:37716) SMB3_11 - - 2718171 nobody users 10.103.53.50 (ipv4:10.103.53.50:37726) SMB3_11 - - 2695528 nobody users heimdall (ipv4:10.103.53.50:40558) SMB3_11 - - 2717448 nobody users heimdall (ipv4:10.103.53.50:59126) SMB3_11 - - 2716731 nobody users 10.103.53.50 (ipv4:10.103.53.50:39818) SMB3_11 - - Service pid Machine Connected at Encryption Signing --------------------------------------------------------------------------------------------- flash 2718169 10.103.53.50 Mon Jun 15 10:13:00 AM 2026 EDT - - flash 2718171 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - IPC$ 2716731 10.103.53.50 Mon Jun 15 10:12:50 AM 2026 EDT - - IPC$ 2718172 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - flash 2716731 10.103.53.50 Mon Jun 15 10:12:50 AM 2026 EDT - - IPC$ 2718170 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - IPC$ 2718171 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - IPC$ 2695528 heimdall Mon Jun 15 10:10:31 AM 2026 EDT - - IPC$ 2718169 10.103.53.50 Mon Jun 15 10:13:00 AM 2026 EDT - - IPC$ 2717448 heimdall Mon Jun 15 10:12:55 AM 2026 EDT - - flash 2718168 10.103.53.50 Mon Jun 15 10:13:00 AM 2026 EDT - - flash 2718170 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - flash 2718172 10.103.53.50 Mon Jun 15 10:13:01 AM 2026 EDT - - IPC$ 2718168 10.103.53.50 Mon Jun 15 10:13:00 AM 2026 EDT - - Locked files: Pid User(ID) DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 2718169 0 DENY_NONE 0x1 RDONLY NONE /boot . Mon Jun 15 10:13:00 2026
June 15Jun 15 32 minutes ago, p0intman said:I hope that means you have an idea on whats happening to my system.Not really, but if that works, it means SMB is not totally broke. Try removing the following files from the flash drive config folder: "passwd", "secrets.tdb", "shadow", "smbpasswd", you can move them somewhere else instead of deleting them just in case, after that, reboot the server and retest, also note that you will need to recreate the users if you have some, but you should only need to set the name and password, the permissions on the shares should be retained in the shares config files.
June 15Jun 15 Author So I remove "passwd", "secrets.tdb", "shadow", "smbpasswd" and rebooted I had to recreate the root password and users but I am still unable to even see the share list and trying to assess a share directly I get asked for a password the logs are filled with the following I tested from my linux machine and from my NVR and a old Windows laptop still no luck[2026/06/15 16:02:58.514820, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) chdir_current_service: vfs_ChDir(/tmp) failed: Permission denied. Current token: uid=99, gid=100, 5 groups: 100 98 3003 3004 3002And when accessing a share directly I see these messages[2026/06/15 16:09:45.491251, 0] ../../source3/smbd/smb2_service.c:117(chdir_current_service) chdir_current_service: vfs_ChDir(/mnt/user/backups/Unifi_Protect_Archiving) failed: Permission denied. Current token: uid=1001, gid=100, 4 groups: 100 3003 3004 3006
June 15Jun 15 What if you make a share public? Also make sure to delete the credentials from Credential Manager in Windows (and the equivalent on Mac)
June 15Jun 15 Author I change all the shares to public rebooted and still same the weird part is to keep my services running I switched to NFS and that's working with out issues but not everything can use NFS. p.s just ramblingThis whole experience is leaving me unsatisfied with Unraid having crazy thoughts of just buying a Synology so disappointed.
June 15Jun 15 My only thought is some config issue creating problems, this assuming multiple clients still cannot login.You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.
June 15Jun 15 Author 4 hours ago, JorgeB said:My only thought is some config issue creating problems, this assuming multiple clients still cannot login.You can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.I appreciate the ideas but that sound like a drastic course of action to rebuilding the entire nas over again and that shouldn't be the case for just samba which was working fine a few releases ago. I been using Unraid over 10yrs and today is the first time I really feel like switching. I changed nothing before the upgrade and was left with a degraded system after the upgrade.
June 16Jun 16 Author Any ideal what this error could be pointing tootree connect failed: NT_STATUS_BAD_NETWORK_NAME
June 16Jun 16 Not really, haven't seen anyone else with similar issues, and assuming you upgraded from 7.2.x, Samba is the same version, so there shouldn't be any issues.That procedure is quite simple to do, at least the initial part to confirm if it's a config problem, you can also downgrade to the previous release to confirm if the upodate is reallythe problem.
June 16Jun 16 Author So this is the first positive sign I have gotten so far I did your suggested downgrade now I can access the samba server but getting a permission denied but its progress.This is me connecting from my linux machine via the command line.❯ smbclient //odin.h0me/TimeMachine -W H0ME -D TimeMachine Can't load /etc/samba/smb.conf - run testparm to debug it Password for [H0ME\nxxxxxxxxxr]: cd \TimeMachine\: NT_STATUS_ACCESS_DENIED ❯ smbclient //odin.h0me/TimeMachine -W H0ME Can't load /etc/samba/smb.conf - run testparm to debug it Password for [H0ME\nxxxxxxxxxr]: Try "help" to get a list of possible commands. smb: \> ls NT_STATUS_ACCESS_DENIED listing \* smb: \>
June 16Jun 16 That, to me confirms the upgrade wasn't the issue, if multiple clients are still failing to access the shares, I suspect a config problem.
June 16Jun 16 Author This is what testparm outputsroot@Odin:~# testparm Load smb config files from /etc/samba/smb.conf lpcfg_do_global_parameter: WARNING: The "null passwords" option is deprecated Loaded services file OK. Weak crypto is allowed by GnuTLS (e.g. NTLM as a compatibility fallback) WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients results in undefined behaviour. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] bind interfaces only = Yes disable netbios = Yes disable spoolss = Yes interfaces = 10.103.53.10/24 127.0.0.1 load printers = No logging = syslog@0 map to guest = Bad User max open files = 40960 multicast dns register = No ntlm auth = ntlmv1-permitted null passwords = Yes passdb backend = smbpasswd printcap name = /dev/null security = USER server min protocol = SMB2 server multi channel support = No server signing = if_required server string = Media server show add printer wizard = No smb1 unix extensions = No smb3 directory leases = No workgroup = H0ME fruit:nfs_aces = No idmap config * : range = 3000-7999 idmap config * : backend = tdb acl allow execute always = Yes aio read size = 0 aio write size = 0 create mask = 0777 directory mask = 0777 hide dot files = No include = /etc/samba/smb-shares.conf invalid users = root use sendfile = Yes wide links = Yes [Unifi_Protect_Archiving] create mask = 0664 directory mask = 0775 hide dot files = Yes include = /boot/config/plugins/custom.smb.shares/smb-custom.conf path = /mnt/user/backups/Unifi_Protect_Archiving valid users = nxxxxxxxxxr unifiprotect write list = nxxxxxxxxxr unifiprotect [TimeMachine] comment = TimeMachine Backups create mask = 0664 directory mask = 0775 guest ok = Yes hide dot files = Yes include = /boot/config/plugins/custom.smb.shares/smb-custom.conf path = /mnt/user/backups/TimeMachine_backup read only = No vfs objects = catia fruit streams_xattr Edited June 16Jun 16 by p0intman
June 16Jun 16 Have a good look at this file (Used two places and see what is doing) I have only a single Custom SMB Share and this is what my file looks like:
June 16Jun 16 Author This is what is included in that fileI will try to match your file and see the resultsroot@Odin:~# cat /boot/config/plugins/custom.smb.shares/smb-custom.conf [Unifi_Protect_Archiving] path = /mnt/user/backups/Unifi_Protect_Archiving browseable = yes guest ok = no valid users = nxxxxxxxxxr unifiprotect write list = nxxxxxxxxxr unifiprotect read only = yes create mask = 0664 directory mask = 0775 hide dot files = yes [TimeMachine] path = /mnt/user/backups/TimeMachine_backup comment = TimeMachine Backups browseable = yes vfs objects = catia fruit streams_xattr guest ok = yes read only = no create mask = 0664 directory mask = 0775 hide dot files = yes Edited June 16Jun 16 by p0intman
June 17Jun 17 3 hours ago, p0intman said:This is what is included in that fileI will try to match your file and see the resultsDon't do this. I wanted to make sure that the file was not corrupted in some way. From what I can see, it is not.
June 18Jun 18 Author This problem has me frustrated I have been researching anything to do with samba and these errors I am seeing and I think I tried everything all of them suggested except for recreating the usb drive. The problem is the nas is so integrated into my ecosystem it will cause a big interruption so any other suggestions of fixing without recreating the flash drive is appreciated willing to try anything at this point.
June 27Jun 27 I got the exact same error message (...vfs_ChDir(/tmp) failed: Permission denied...) and couldn't access the shares via SMB. In my case, the problem was that I had placed the /tmp share on my cache drive. After I changed this back to "Array" and restarted the Samba service, I was able to access the shares via SMB without any problems.
June 28Jun 28 Author 6 hours ago, mcandy said:I got the exact same error message (...vfs_ChDir(/tmp) failed: Permission denied...) and couldn't access the shares via SMB. In my case, the problem was that I had placed the /tmp share on my cache drive. After I changed this back to "Array" and restarted the Samba service, I was able to access the shares via SMB without any problems.Hi @mcandy i'm glad you got it working again, I didn't have a "/tmp" share where exactly did you change the to the array I may test it out as I am still unable to access. My solution was to buy a Ugreen nas and I have started migrating over to it but I would like to save my unraid.
June 28Jun 28 I have a user share named "tmp," but it isn't being exported via Samba. After the change, it is mounted at /user/disk1/tmp. That's why I'm wondering myself why setting the settings to "Array" instead of "Cache" affects its behavior. (Share Settings/Primary Storage) The original error message mentioned access problems to /tmp in the Samba VFS. And I don’t think this was referring to my user share.So unfortunately, I can’t explain to you in more detail why it’s working now....
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.