CIFS mounts failing but don't know where they are coming from

Help and Support
1

Hi, I’ve been trying to troubleshoot crashes on my RaspberryPi Volumio (RPi3, Volumio 2.834) by examining the output of dmesg. I see several instances of

    [   69.999218] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
    [   70.148582] CIFS VFS: BAD_NETWORK_NAME: \\192.168.0.21\volume1
    [   70.155384] CIFS VFS: cifs_mount failed w/return code = -2

but I can’t tell what process is trying to mount those apparently-missing shares. 192.168.0.21 is a good address on my network, it is a NAS. Something in Volumio has been set to look for shares there, but I can’t figure out what. Any ideas?

2

Have you checked in sources in Volumio? you need to add vers=1.0 in advanced optiion to mount this share.

3

Thank you. Sources appears to have a proper setup to the target share, showing the correct NAS IP Address (192.168.0.21) and Path seems okay (volume1/Pop Music Lib), and “cifs” and username/pass are good. Without adding “vers=1.0” to the Options fill-in triggers “ERROR WHEN ADDING NETWORK DRIVE (2): No such file or directory” on save. Adding “vers=1.0” to the Options triggers Error (95) “Operation not supported.” “Pop Music Lib” is a shared folder on the NAS, and one I can browse to from other devices on the network, for example my Linux laptop. I have ssh access to the RPi/Volumio if there is something you might recommend I look at more deeply.