FreeNAS 11.3-U5 -> TrueNAS 12.0-U1.1 update dumps SMB shares

TurboTas

Cadet
Joined
Aug 20, 2019
Messages
5
Hi all,

Apologies, looking for a steer: updated today as above from 11.3U5 to 12.0U1.1. As per normal the update was painless but on reboot none of the SMB shares were browseable. Messed around for a few minutes and then went back to 11.3U5 and shares work fine again.

Does anyone have suggestions for diagnostic steps to take to try and resolve? all previous updates have been solid and never had shares missing before.

GUI *seems* to indicate that they are they okay, but can't seem to find the best place to look for failure indications.

Cheers!
 

ccssid

Explorer
Joined
Dec 12, 2016
Messages
86
did you try remapping your shares?
 

TurboTas

Cadet
Joined
Aug 20, 2019
Messages
5
Hi, thanks for your response. Do you mean remapping from the clients? After the reboot to 12.0u1.1, it's not possible to browse to the NAS at all from windows, either from a new machine or a machine with a mapped drive. Normally I would just have browsed to \\ip.adddress\ and that would have shown me the list of SMB shares. I'm guessing 12.0u1.1 has changed a setting but I'm a bit lost where to look!
 

ccssid

Explorer
Joined
Dec 12, 2016
Messages
86
\\ip.address should get you a list of the shares. I moved from 11.3 to 12.0-u1. all worked fine....although i did not do an upgrade. I did a fresh install. and recreated shares. Did the same going from 9.10 to 12.0-u1 in another machine and no issues.....fresh install. I have a very basic system, however, for file storage and plex. So, recreating shares was a very simple task.
 

TurboTas

Cadet
Joined
Aug 20, 2019
Messages
5
Yes, I agree that it should, but it doesn't. Is there something semi-obvious to check on the TruesNAS end in terms of logs etc?
 

LarsR

Guru
Joined
Oct 23, 2020
Messages
714
Did you perhaps use root as the user to connect the smb shares? As of 12.0 it was implemented as a safety measure that root no longer has acces to shares. Try Creating a new user, add it to the wheel user-group and edit the Share ACL's that your new user has read write and execute rights.
 

TurboTas

Cadet
Joined
Aug 20, 2019
Messages
5
I didn't use root to connect, but I'll give the new user approach a try and check wheel user-group membership , thankyou!
 

TurboTas

Cadet
Joined
Aug 20, 2019
Messages
5
I got a little further: One of the shares is full of music that the Sonos accesses. It seems that when the Sonos tries to access the share after booting to 12.0U1.1, samba crashes. Here is the auth_audit.log:

Code:
  {"timestamp": "2021-01-26T22:11:37.228427+0000", "type": "Authentication", "Authentication": {"version": {"major": 1, "minor": 2}, "eventId": 4624, "logonId": "0", "logonType": 3, "status": "NT_STATUS_OK", "localAddress": "ipv4:192.168.51.12:445", "remoteAddress": "ipv4:192.168.51.180:35725", "serviceDescription": "SMB", "authDescription": null, "clientDomain": "", "clientAccount": "sonos", "workstation": "192.168.51.180", "becameAccount": "sonos", "becameDomain": "FREENAS", "becameSid": "S-1-5-21-3317927091-4123077096-415176198-3000", "mappedAccount": "sonos", "mappedDomain": "", "netlogonComputer": null, "netlogonTrustAccount": null, "netlogonNegotiateFlags": "0x00000000", "netlogonSecureChannelType": 0, "netlogonTrustAccountSid": null, "passwordType": "NTLMv1", "duration": 4867}}


and here is a section from log.smbd:

Code:
[2021/01/26 22:15:25.976126,  0] ../../lib/util/fault.c:80(fault_report)
  INTERNAL ERROR: Signal 11 in pid 9161 (4.12.9)
  If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
[2021/01/26 22:15:25.976319,  0] ../../lib/util/fault.c:86(fault_report)
  ===============================================================
[2021/01/26 22:15:25.976372,  0] ../../source3/lib/util.c:830(smb_panic_s3)
  PANIC (pid 9161): internal error
[2021/01/26 22:15:25.978860,  0] ../../lib/util/fault.c:265(log_stack_trace)
  BACKTRACE: 6 stack frames:
   #0 0x801952d17 <log_stack_trace+0x37> at /usr/local/lib/samba4/libsamba-util.so.0
   #1 0x802ccfb86 <smb_panic_s3+0x56> at /usr/local/lib/samba4/libsmbconf.so.0
   #2 0x801952b07 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
   #3 0x801952eee <log_stack_trace+0x20e> at /usr/local/lib/samba4/libsamba-util.so.0
   #4 0x801952ae9 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
   #5 0x80fd48c20 <_pthread_sigmask+0x530> at /lib/libthr.so.3
[2021/01/26 22:15:25.979223,  0] ../../source3/lib/dumpcore.c:315(dump_core)
  dumping core in /var/db/system/cores
[2021/01/26 22:15:26.064600,  0] ../../lib/util/fault.c:79(fault_report)


these errors repeat about 3 times per second.

Any thoughts what to try and diagnose next?
 

ccssid

Explorer
Joined
Dec 12, 2016
Messages
86
how about going back to 11.3, saving config, install a fresh copy of 12.0-u1 (not updating), import pool, update config. (just taking a flyer here)
 
Top