SMB Mount Errors found in dmesg

In the middle of an afternoon, my Debian 11 server that host Jellyfin started producing the error, “File type was not available”. That typically means I have not mounted the file share to the compute cluster. This always happens after a power outage or a full system shutdown. I mount the NAS manually to stay in practice. However when I opened dmesg to see what happened, here are the multitude of errors I saw.

[  573.179120] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[  573.507953] CIFS: VFS: parse_server_interfaces: malformed interface info

[65242.528585] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
[65242.529501] FS-Cache: Duplicate cookie detected

[65242.529596] FS-Cache: N-key=[8] '020001bdc0a80002'
[65243.228867] CIFS: VFS: cifs_mount failed w/return code = -112

Trying to mount the share as an NFS volume seemed to cause the login failure that you see below. I was using the same service account and the NFS & SMB share permissions were properly configured on the TrueNAS Scale. I eventually opted to slowly reboot both the NAS and Compute server to see how things would work out. Plot twist, no change.

[ 2107.847210] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 2107.847226] CIFS: VFS: \\REDACTED2 Send error in SessSetup = -13
[ 2107.848221] CIFS: VFS: cifs_mount failed w/return code = -13

#This was the final error message I encountered before I opted to take the update path.

[ 2441.265093] CIFS: VFS: cifs_mount failed w/return code = -95
[ 2501.643485] CIFS: Attempting to mount //REDACTED
[64768.297389] CIFS: VFS: \\REDACTED has not responded in 180 seconds. Reconnecting...
[65177.473781] CIFS: Attempting to mount //REDACTED
[65177.477091] CIFS: VFS: cifs_mount failed w/return code = -2

Resolution Path

Last ditch effort, I opted to update from TrueNAS Scale Bluefin 22.12.1 up to the latest available release, TrueNAS-SCALE-23.10.2 in the now depricated release chain. If I encounter anymore issues moving forward it does appear I will be forced to once again update TrueNAS Scale from Bluefin to Dragonfish or possibly Electric Eel.

TrueNAS Road Map

JellyFin

2024 29
2023 13
2022 4
2021 7

SMB Mount Errors found in dmesg

Resolution Path

2024

2023

2022

2021