SMB not working after upgrade from 12.0-U6 to 13.0

[AltecBX]

I just updated from 12.0-U6 to 13.0 last night. I have 2 Samba shared folders and one seems to work and the other doesn't. What went wrong?

 

[TrueUserGuy]

I just updated from 12.0-U6 to 13.0 last night. I have 2 Samba shared folders and one seems to work and the other doesn't. What went wrong?

Me too.

Just upgraded to v13.U1 from 12.U8

Suddenly and without any other changes - after the installation reboot, My NVidia Shield Pro (2021) can no longer play or view media. It can however list directory content.

However, I connect via windows 10, and there are no issues!

Something has changed within the SMB implementation here, this might be due to upgrading the SMB libraries as part of moving to v13.

It would good to understand how we start trouble shooting this vary odd behaviour. NVidia have a very poor implementation of SMB, that's well known, also criminal by all accounts is quiet appalling. They mandate NetBios on etc, but do at least support SMB2. However, this strange behaviour presents as if the execute permission was not set, but it most certainty is set.


My first step was to strip the ACLs from the Dataset, and re-add them. I removed the SMB shares too, and re-added them with default share prams.

Works perfectly on my windows 10 laptop, however the same issue persists on the Android device. Very odd.

 

[TrueUserGuy]

Just adding some log file entries behind this, I cleared the log file, then restarted the service. Then attempted to play a video file on the android device.

root@truenas[~]# less /var/log/samba4/log.smbd
[2022/07/13 00:17:16.984582, 0] ../../source3/smbd/server.c:1734(main)
smbd version 4.15.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2021
[2022/07/13 00:17:16.987228, 1] ../../source3/profile/profile.c:55(set_profile_level)
INFO: Profiling turned OFF from pid 15133
[2022/07/13 00:17:17.072707, 1] ../../source3/smbd/files.c:809(file_init_global)
file_init_global: Information only: requested 462204 open files, 59392 are available.
[2022/07/13 00:17:19.802488, 3] ../../auth/auth_log.c:665(log_authentication_event_human_readable)
Auth: [SMB2,(null)] user [TRUENAS]\[smbmedia] at [Wed, 13 Jul 2022 00:17:19.802481 UTC] with [NTLMv2] status [NT_STATUS_OK] workstation [] remote host [ipv4:192.168.1.132:52426] became [TRUENAS]\[smbmedia] [S-1-5-21-2286527191-2304684957-3930965839-1005]. local host [ipv4:192.168.1.199:445]
[2022/07/13 00:17:19.803452, 4] ../../auth/auth_log.c:765(log_successful_authz_event_human_readable)
Successful AuthZ: [SMB2,NTLMSSP] user [TRUENAS]\[smbmedia] [S-1-5-21-2286527191-2304684957-3930965839-1005] at [Wed, 13 Jul 2022 00:17:19.803447 UTC] Remote host [ipv4:192.168.1.132:52426] local host [ipv4:192.168.1.199:445]
(END)

 

[TrueUserGuy]

root@truenas[~]# midclt call smb.status
{"sessions": [{"session_id": "16696", "uid": 1000, "gid": 65533, "username": "smbmedia", "groupname": "nogroup", "remote_machine": "192.168.1.132", "hostname": "ipv4:192.168.1.132:52578", "session_dialect": "SMB3_00", "encryption": "-", "signing": "UNKNOWN_DIALECT(0x00000300)"}], "shares": [], "locked_files": []}

 

[TrueUserGuy]

I changed the ACL permissions from Readonly to Modify and now the media files will play. However this was not the behaviour that was operational before the update. And is not what is expected since readonly also grants the execute permission on the file. something is wrong with the way the SMB service is handling permissions.

 

[AltecBX]

I changed the ACL permissions from Readonly to Modify and now the media files will play. However this was not the behaviour that was operational before the update. And is not what is expected since readonly also grants the execute permission on the file. something is wrong with the way the SMB service is handling permissions.

I have mine at Full Persimsion and it still doesn't allow me to open the folder.
The crazy part is that I have another shared folder in SMB and I can access sit just as I did before the upgrade.

 

[TrueUserGuy]

Hopefully an expert who understands the SMB subsystem will have insights that clear this up or identify a bug. Currently it would seem the Read permission is not working with all clients correctly as it should indicating some sort of negotiation issues or maybe even, the client is to blame.

Hard to say until someone with solid trouble shooting skills in this area is able to guide this. The pain of using Truenas vs Microsoft Server is when it goes wrong, its not easy to fix unless you have extensive FreeBSD skills / Linux skills.

 

[TrueUserGuy]

Perhaps this is one for @anodos to consider. Any ideas ?

 

[Arvi LEFEVRE]

This is a very serious issue, the Truenas I've installed for my brother for his video editing company had a similar issue after upgrading to 13.U1 from 12.7, couldn't even read most of the premiere pro projects files (but somehow the rest is fine) while all the permissions were fine. Thankfully there a multiple backups, but this is used for work, that's why we waited for U1, I guess next time we'll wait for U2.
(I also still keep in mind it could be adobe as they are specialists of this kind of shit, but the timing is weird and we didn't update premiere on any of the desktops)

 

[AltecBX]

I can't believe this hasn't been resolved as so many other people are having the same issue. Any updates?

 

[verada12]

This is a very serious issue, the Truenas I've installed for my brother for his video editing company had a similar issue after upgrading to 13.U1 from 12.7, couldn't even read most of the premiere pro projects files (but somehow the rest is fine) while all the permissions were fine. Thankfully there a multiple backups, but this is used for work, that's why we waited for U1, I guess next time we'll wait for U2.
(I also still keep in mind it could be adobe as they are specialists of this kind of shit, but the timing is weird and we didn't update premiere on any of the desktops)

Hi mate. Was having the same issue - unable to access some files via Windows after upgrading from 13.0 to 13.0-U1.
I've gone back to 13.0 boot environment and problem solved.
Guess will have to wait for the next update.

 

[Arvi LEFEVRE]

Hi mate. Was having the same issue - unable to access some files via Windows after upgrading from 13.0 to 13.0-U1.
I've gone back to 13.0 boot environment and problem solved.
Guess will have to wait for the next update.

My problem is that I've waited for 13.U1 to upgrade, I don't have 13.0 :(

 

[anodos]

My problem is that I've waited for 13.U1 to upgrade, I don't have 13.0 :(

There are instructions to manually fix here: https://www.truenas.com/community/threads/truenas-13-0-u1-is-now-available.102326/page-4#post-706487

 

[Arvi LEFEVRE]

There are instructions to manually fix here: https://www.truenas.com/community/threads/truenas-13-0-u1-is-now-available.102326/page-4#post-706487

I'm not touching anything while waiting for an official fix, there is 60TB of data and they can manage with backups so I'm not risking anything now, I'll wait for the next update.

 

[anodos]

I'm not touching anything while waiting for an official fix, there is 60TB of data and they can manage with backups so I'm not risking anything now, I'll wait for the next update.

Official fix is scheduled for this upcoming thursday