I “upgraded” my Freenas 13.x system to TrueNAS core. It failed to install properly, so I tried again and it worked. I imported the FreeNAX pools but found that no PC could access the SMB shares. I tried resetting the permissions and anything I could think of. Nothing. They showed as an available share but could not be accessed.
I installed another FreeNAS thumb drive v13 and loaded the OS. All was well, but the original pools are not there… nothing. I tried decrypting or no encryption but they were not visitble.
One issue you need to clarify is your upgrade route - for instance, there was no FreeNAS 13 (last version was 11.3 in mid-2020).
I’m going to hazard a guess about your inability to access SMB shares - that you are using a windows client with the credentials of your TrueNAS root account. Windows no longer allows that access - if this is your issue, make a new user account on TrueNAS and use that to (attempt to) access your SMB shares.
I errored in my sentence and meant an “upgrade” from FreeNAS to TrueNAS 13. It failed to complete, just froze so I eventually rebooted and tried to install again. It worked.
I imported the pools and attempted to SMB into them on the newly installed v13 TrueNAS core using Windows SMB, on different machines with different user accounts. All showed that the SMB shares were inaccesible, although could be mapped to drive letters. The root account was not involved, just standard user accounts that worked with FreeNAS. The user accounts were added.
I recreated the FreeNAS installation, but the pools could not be imported or seen as I think they were changed by the prior TrueNAS importation.
I reinstalled TrueNAS again. The pools are there but SMB does not allow access through ANY user account.
/var/log/samba4/log.smbd may give some indication.
Ability to mount / map an SMB share but not access data is typical for case where user lacks filesystem permissions. When a client performs an initial SMB tree connect only the share’s ACL (which is typically wide-open) is checked. Then once user tries to access data, the filesystem ACL rejects access.
The most common reason I’ve seen for this to happen is the administrator removing execute permissions from some parent directory of share (cutting off access to all users). For instance, were some youtube how-to videos a few years back that told users to chmod 700 /mnt/tank that got heavily promoted (yes, this is egregiously bad even by the low-low standards of youtube tech influencers), and we had to deal with fairly constant bug reports from users about SMB access being broken.
The simplest way to test for this is to SSH into truenas, su to a user in question, and try to cd into the path of one of these shares.
Thanks. I will work on it, although never had a problem with FreeNAS. And it was suprising that a virtual new isntance of TrueNAS has the same issues, in spite of 777 permission given tot he non root test user. When I find the solution, I’ll publish.
