Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Help with recent CIFS issue

  1. #1
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,994

    Question Help with recent CIFS issue

    Something got messed up in Tumbleweed. What worked flawlessly nowfails with:
    Code:
    Jun 23 07:59:52 erlangen kernel: FS-Cache: Loaded
    Jun 23 07:59:52 erlangen kernel: Key type dns_resolver registered
    Jun 23 07:59:52 erlangen kernel: Key type cifs.spnego registered
    Jun 23 07:59:52 erlangen kernel: Key type cifs.idmap registered
    Jun 23 07:59:52 erlangen kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
    Jun 23 07:59:52 erlangen kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
    Jun 23 07:59:52 erlangen kernel: CIFS: Attempting to mount \\fritz.box\FRITZ.NAS 
    Jun 23 08:02:58 erlangen kernel: CIFS: VFS: \\fritz.box has not responded in 180 seconds. Reconnecting...
    Jun 23 08:06:05 erlangen kernel: CIFS: VFS: \\fritz.box has not responded in 180 seconds. Reconnecting...
    Jun 23 08:06:05 erlangen kernel: CIFS: VFS: \\fritz.box Send error in SessSetup = -11
    Jun 23 08:09:12 erlangen kernel: CIFS: VFS: \\fritz.box has not responded in 180 seconds. Reconnecting...
    Jun 23 08:09:12 erlangen kernel: CIFS: VFS: \\fritz.box Send error in SessSetup = -11
    Jun 23 08:12:18 erlangen kernel: CIFS: VFS: \\fritz.box has not responded in 180 seconds. Reconnecting...
    Jun 23 08:12:18 erlangen kernel: CIFS: VFS: \\fritz.box Send error in SessSetup = -11
    Last edited by deano_ferrari; 23-Jun-2022 at 14:35. Reason: Moderator Edit
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  2. #2
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,994

    Default Re: CIFS: VFS: cifs_mount failed w/return code = -22

    Cifs worked for years without any problems. Could be an issue caused by a fix such as:

    - Update to version 6.15
    * CVE-2022-27239: mount.cifs: fix length check for ip option parsing
    Previous check was true whatever the length of the input string was,
    leading to a buffer overflow in the subsequent strcpy call.
    * mount.cifs: fix verbose messages on option parsing
    Last edited by deano_ferrari; 23-Jun-2022 at 14:35. Reason: Moderator Edit
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  3. #3
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,994

    Default Re: CIFS: VFS: cifs_mount failed w/return code = -22

    Updated Leap 15.3 and retried:
    Code:
    Leap-15-3:~ # mount /fritz.box 
     Password for ftpuser@//fritz.box/FRITZ.NAS:  ********                 
    mount error: Server abruptly closed the connection. 
    This can happen if the server does not support the SMB version you are trying to use. 
    The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. 
    mount error(112): Host is down 
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 
    Leap-15-3:~ #
    

    Code:
    Leap-15-3:~ # journalctl -b -g cifs 
    -- Logs begin at Fri 2021-08-06 10:17:37 CEST, end at Thu 2022-06-23 11:26:12 CEST. -- 
    Jun 23 11:23:08 Leap-15-3 kernel: FS-Cache: Netfs 'cifs' registered for caching
    Jun 23 11:23:08 Leap-15-3 kernel: Key type cifs.spnego registered
    Jun 23 11:23:08 Leap-15-3 kernel: Key type cifs.idmap registered
    Jun 23 11:23:08 Leap-15-3 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
    Jun 23 11:23:08 Leap-15-3 kernel: CIFS: Attempting to mount \\fritz.box\FRITZ.NAS 
    Jun 23 11:23:08 Leap-15-3 kernel: CIFS: VFS: cifs_mount failed w/return code = -112
    Leap-15-3:~ #
    Code:
    Leap-15-3:~ # grep fritz.box /etc/fstab 
    //fritz.box/FRITZ.NAS                      /fritz.box              cifs   noauto,username=ftpuser,vers=1.0  0  0 
    Leap-15-3:~ #
    Removed the media from the FRITZ!Box and replugged.

    Success:
    Code:
    Jun 23 11:37:17 Leap-15-3 kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
    Jun 23 11:37:17 Leap-15-3 kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
    Jun 23 11:37:17 Leap-15-3 kernel: CIFS: Attempting to mount \\fritz.box\FRITZ.NAS 
    Jun 23 11:37:17 Leap-15-3 kernel: CIFS: VFS: multichannel is not supported on this protocol version, use 3.0 or abov
    
    Error messages can be confusing.
    Last edited by deano_ferrari; 23-Jun-2022 at 14:36. Reason: Moderator Edit
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  4. #4

    Default Re: CIFS: VFS: cifs_mount failed w/return code = -22

    Quote Originally Posted by karlmistelberger View Post
    Cifs worked for years without any problems. Could be an issue caused by a fix such as:
    https://www.suse.com/releasenotes/x8...SP4/index.html

    5.10.1.3 SMB1 support has been deprecated

    With Samba 4.17 it is planned to disable the SMB1 protocol. We therefore deprecated SMB1 for a possible future update of Samba. This affects the Samba file server, its libraries and clients, as well as the kernel CIFS client (cifs.ko and mount.cifs). This version of the protocol is insecure and usage of version 2.02 or later is recommended.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    24,117
    Blog Entries
    1

    Default Re: Help with recent CIFS issue

    @karlmistelberger: Can you connect successfully using SMB2? And using smbclient?
    Code:
    smbclient -L <server_name>/<share> -U <username> -d 256
    Last edited by deano_ferrari; 23-Jun-2022 at 16:06.
    openSUSE Leap 15.4; KDE Plasma 5

  6. #6
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,994

    Default Re: Help with recent CIFS issue

    Quote Originally Posted by deano_ferrari View Post
    @karlmistelberger: Can you connect successfully using SMB2? And using smbclient?
    Code:
    smbclient -L <server_name>/<share> -U <username> -d 256
    No way: https://en.avm.de/service/knowledge-...the-FRITZ-Box/
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    24,117
    Blog Entries
    1

    Default Re: Help with recent CIFS issue

    Quote Originally Posted by karlmistelberger View Post
    Then you have a decision to make
    The FRITZ!Box supports version 1.0 of the network protocol SMB. The FRITZ!Box does not support versions 2 and 3 of the SMB protocol (SMB2, SMB3).
    If you cannot use SMB 1.0 or do not want to, use http://fritz.nas or the FTP protocol to access the storage, for example with Cyberduck, FileZilla, or WinSCP.
    openSUSE Leap 15.4; KDE Plasma 5

  8. #8
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,994

    Default Re: Help with recent CIFS issue

    Quote Originally Posted by deano_ferrari View Post
    Then you have a decision to make
    Yep. I use it mostly for testing connectivity of the machines users are bringing in: https://forums.opensuse.org/showthre...ouble-Shooting
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  9. #9
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    7,217

    Default AW: Help with recent CIFS issue

    I use for a Fritzbox 7490:
    Code:
    //192.168.0.254/fritz.nas /mnt/fritznas cifs vers=3.1.1,noserverino,username=xxxxxx,password=yyyyyyy,uid=1000,gid=100 0 0
    Important was the noserverino....

    Fritzbox is not using samba V 1.0 anymore, there was a Firmware Update some time before.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    24,117
    Blog Entries
    1

    Default Re: AW: Help with recent CIFS issue

    Quote Originally Posted by Sauerland View Post
    I use for a Fritzbox 7490:
    Code:
    //192.168.0.254/fritz.nas /mnt/fritznas cifs vers=3.1.1,noserverino,username=xxxxxx,password=yyyyyyy,uid=1000,gid=100 0 0
    Important was the noserverino....
    Good find! I note other similar recommendations to use the same...

    https://www.reddit.com/r/fritzbox/co..._broke_my_git/
    http://www.daprose.de/article/linux-...-fritz-box-nas

    Fritzbox is not using samba V 1.0 anymore, there was a Firmware Update some time before.
    That makes sense.

    Both links mention FRITZ!OS upgrading. In the second link it was mentioned...
    In my home setup i have a FRITZ!Box 7490 serving an USB 3.0 SSD as my local NAS to be accessed by multiple different devices. Some of these are Linux laptops running an openSUSE 15.2 distribution. The NAS itself supported the SMB 1 protocol only in the past, but after upgrading to a newer FRITZ!OS i can use SMB 3 now.
    However, the OP's hardware model is too old it would seem.
    Last edited by deano_ferrari; 23-Jun-2022 at 23:03.
    openSUSE Leap 15.4; KDE Plasma 5

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •