In our Azure RESOURCE_GROUP rg-hpc-prod-soutus01 we have created a Locally-redundant storage (LRS) which is our Networkshare. We also have a Virtual Machine as a Jumphost where the Networkshare is mounted on which is working fine. But in our Virtual machine scale set with Almalinux-HPC the Networkshare isnt working / bzw. im note able to mount the Share:

[root@vmss-hpc-000000 ~]# mount -t cifs //***********.file.core.windows.net/installfiles /media/installfiles -o vers=3.1.1,credentials=/etc/smbcredentials/*********.cred,dir_mode=0755,file_mode=0644,serverino

mount error: cifs filesystem not supported by the system

mount error(19): No such device

Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

mount: (hint) your fstab has been modified, but systemd still uses

   the old version; use 'systemctl daemon-reload' to reload. 

[root@vmss-hpc-000000 ~]#

I already load the CIFS Module

[root@vmss-hpc-000000 ~]# lsmod | grep cifs

cifs 16384 0

mlx_compat 16384 16 rdma_cm,ib_ipoib,cifs,mlxdevm,nvme_tcp,nvme,iw_cm,nvme_core,nvme_fabrics,ib_umad,ib_core,rdma_ucm,ib_uverbs,mlx5_ib,ib_cm,mlx5_core

[root@vmss-hpc-000000 ~]# modinfo cifs

filename: /lib/modules/4.18.0-553.16.1.el8_10.x86_64/extra/mlnx-ofa_kernel/fs/cifs/cifs.ko

version: 2.31

license: Dual BSD/GPL

description: cifs dummy kernel module

author: Mohammad Kabat

rhelversion: 8.10

srcversion: 01E451882B55F354B7F130B

depends: mlx_compat

name: cifs

vermagic: 4.18.0-553.16.1.el8_10.x86_64 SMP mod_unload modversions

[root@vmss-hpc-000000 ~]#

Here the output of existing Modules :

[root@vmss-hpc-000000 ~]# grep CIFS /boot/config-$(uname -r)

CONFIG_CIFS=m

CONFIG_CIFS_STATS2 is not set

CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y

CONFIG_CIFS_WEAK_PW_HASH=y

CONFIG_CIFS_UPCALL=y

CONFIG_CIFS_XATTR=y

CONFIG_CIFS_POSIX=y

CONFIG_CIFS_DEBUG=y

CONFIG_CIFS_DEBUG2 is not set

CONFIG_CIFS_DEBUG_DUMP_KEYS is not set

CONFIG_CIFS_DFS_UPCALL=y

CONFIG_CIFS_SWN_UPCALL is not set

CONFIG_CIFS_SMB_DIRECT=y

CONFIG_CIFS_FSCACHE is not set

[root@vmss-hpc-000000 ~]#

any ideas for troubleshooting, am I missing something?

I was able to install Kernel and CIFS Module but its still using Mellanox Kernel Module:

[root@vmss-hpc-000000 ~]# modinfo cifs | grep filename

filename: /lib/modules/4.18.0-553.54.1.el8_10.x86_64/weak-updates/mlnx-ofa_kernel/fs/cifs/cifs.ko

[root@vmss-hpc-000000 ~]#

Hey Pau, thanks for your answer, I already thought it must be something with the CIFS Module.

In our Azure Almalinux-HPC Im not able to install any Kernel Modules:

[root@vmss-hpc-000000 ~]# yum install cifs-utils kernel-modules kernel-core

Last metadata expiration check: 2:31:27 ago on Tue 10 Jun 2025 05:39:57 AM UTC.

Package cifs-utils-7.0-1.el8.x86_64 is already installed.

All matches were filtered out by exclude filtering for argument: kernel-modules

All matches were filtered out by exclude filtering for argument: kernel-core

Error: Unable to find a match: kernel-modules kernel-core

[root@vmss-hpc-000000 ~]#

Is there a Solution for that ?

Thx in advance.

Hi, I’m Pau, an Independent Advisor. Your VM is showing this error because it is loading a Mellanox dummy CIFS module instead of the regular one.

Kindly adhere to the following steps:

1. Remove the dummy CIFS module:

sudo modprobe -r cifs

2. Take out the Mellanox OFA kernel modules:

sudo yum remove -y mlnx-ofa_kernel

3. Install the standard CIFS and kernel modules:

sudo yum install -y cifs-utils kernel-modules kernel-core

4. Restart the VM:

sudo reboot

5. Check that the right CIFS module is loaded:

modinfo cifs | grep filename

(Should point to /kernel/fs/cifs/cifs.ko.xz)

6. Remount your Azure Files share:

sudo mount -t cifs //<storageaccount>.file.core.windows.net/installfiles /media/installfiles -o vers=3.1.1,credentials=/etc/smbcredentials/<your_credential>.cred,dir_mode=0755,file_mode=0644,serverino

Optional: Include the share in /etc/fstab and refresh with:

sudo systemctl daemon-reexec

sudo systemctl daemon-reload

sudo mount -a

This will fix the mount error by making sure SMB3 is fully supported.

If you need more help, just let me know.

Kind regards,

Pau

[root@vmss-hpc-000000 ~]# grep -E "CONFIG_CIFS_SMB3|CONFIG_CIFS_ALLOW_INSECURE_LEGACY" /boot/config-$(uname -r)

CONFIG_CIFS_ALLOW_INSECURE_LEGACY=y

[root@vmss-hpc-000000 ~]#

CONFIG_CIFS_SMB3=y # SMB3 is supported is missing - may is cause the issue ?