Faill to mount cifs network share folder

Creating a bug report/issue

Required Information

  • DietPi version | cat /boot/dietpi/.version
    G_DIETPI_VERSION_CORE=8
    G_DIETPI_VERSION_SUB=9
    G_DIETPI_VERSION_RC=2
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
    bullseye 0

  • Kernel version | uname -a
    Linux DietPi 5.15.61-v7+ #1579 SMP Fri Aug 26 11:10:59 BST 2022 armv7l GNU/Linux

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
    RPi 3 Model B (armv7l)

  • Power supply used | (EG: 5V 1A RAVpower)
    5V 2A

  • SD card used | (EG: SanDisk ultra)
    Toshiba Exceria 8GB

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)
  • Was the software title installed freshly or updated/migrated?
  • Can this issue be replicated on a fresh installation of DietPi?
    Yes
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID

Steps to reproduce

Basic dietpi with Mopidy, Alsa, and cifs-utils installed
Previously running v8.1.2 with no problems
fstab entry :
//192.168.1.1/usb /mnt/sambausb cifs cred=/var/lib/dietpi/dietpi-drive_manager/mnt-sambausb.cred,iocharset=utf8,uid=dietpi,gid=dietpi,file_mode=0770,dir_mode=0770,vers=1.0,nofail,noauto,x-systemd.automount
allows access to shared drive on network box

also I can create a directory and mount with usual command -
mkdir /mnt/usb
sudo mount -t cifs -o username=admin,password=MareCroix,vers=1.0 //192.168.1.1/usb /mnt/usb
and I get another entry to browse shared files in Mopidy.

Subsequently I did an update to latest diepi v8.9.2 and could no longer access network share
I also did a clean install with same behaviour. Manual mount command also returns error.

dmesg startup error :
brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.bin failed with error -2
brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1

dmesg error when attempting access via Mopidy (using fstab)
CIFS: Attempting to mount \192.168.1.1\usb
CIFS: VFS: \192.168.1.1 failed to connect to IPC (rc=-6)
CIFS: VFS: cifs_mount failed w/return code = -6

with mount command error :
mkdir /mnt/usb
sudo mount -t cifs -o username=admin,password=MareCroix,vers=1.0 //192.168.1.1/usb /mnt/usb

mount error(6): No such device or address
and dmesg output :
CIFS: Attempting to mount \192.168.1.1\usb
CIFS: VFS: \192.168.1.1 failed to connect to IPC (rc=-6)
CIFS: VFS: cifs_mount failed w/return code = -6

using dietpi-drive_manager error ;
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)
Retrying with upper case share name
mount error(6): No such device or address

we did a litte bit of resource and it seems since kernel version 5.15, CIFS did not support SMBv1 anymore. https://bugzilla.kernel.org/show_bug.cgi?id=215375

What SMB server did you use? Does it really need to be SMBv1?

Thanks Joulinar for your very quick answer. This was driving me bonkers ! Yes I need smb v1 my internet box only supports this. I read most of the bug report link so I see it is basically a kernel “improvement”. Is there a simple way of substituting a previous kernel into dietpi without braking anything else ? Thanks again. Tim

As you are running RPI, you could use official tools to switch back to oldstable - 5.10.103 GitHub - raspberrypi/rpi-update: An easier way to update the firmware of your Raspberry Pi

apt install rpi-update
sudo BRANCH=oldstable rpi-update
reboot

WARNING
You do this on your own risk as downgrading a kernel could have other side effect

Again thanks again for your rapid reply Joulinar !
I did as you suggest to go back to 5.10.103 kernel, and this immediately solved my problem, fantastic !
Thanks,
Tim