SOLVED Following unplanned powerloss, shares authentication no longer works

[Linkex]

A few days ago, my home lab suffered a powerloss. On booting back up, freenas appears to have survived, however I'm seeing some odd behaviour on the shared drives.

On windows shares, mapped drives that require authentication will no longer allow connection. Remapping fails with an authentication error. However, mappings to shares that are configured to allow guest access seem to be working normally.

For NFS drives, I can connect, however no data or folder structure is present.

My /var/log/samba4/log.smdb contains the following, so I have re-checked credentials/reset passwords etc are correct.

Code:

[2019/01/08 20:06:55.131922,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.132284,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.135020,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.135327,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.380208,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.380627,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.381334,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.381605,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.381904,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.382282,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.382590,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED
[2019/01/08 20:06:55.388577,  1] ../source3/smbd/service.c:521(make_connection_snum)
  create_connection_session_info failed: NT_STATUS_ACCESS_DENIED

My guess is there is some kind of authentication mechanism that isn't working, but I don't know enough about freenas to know what I need to look for. Any suggestions for next steps would be gratefully received. In particular, I'm assuming the NFS service logs somewhere, but I cannot find anything in the docs showing where they live.

 

[Linkex]

As with so many of these things, it turned out to be quite simple.

The NFS side was a red herring, it was a mis-configuration on the part of the server accessing the share that was revealed by the reboot.

The Samba issue appears to have been a corruption of the passdb.tdb file. Removing the file and then manually adding the user back with smbpasswd -a <user> resolved it. I would note that other than the user I manually added, no pre-existing accounts have access to SMB. If I create a new account, they do have access, so I assume some kind of rebuild would be required to enable existing users