linux-image-6.2.0-1016-azure cifs is not supported

Khaled AlAkhras 110 Reputation points
2023-10-31T09:27:21.38+00:00

Ubuntu 22.04.3 LTS (GNU/Linux 6.2.0-1016-azure x86_64)

After upgrading from linux-image-6.2.0-1015-azure to linux-image-6.2.0-1016-azure, we are unable to mount cifs file shares.

sudo mount -a

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)

sudo lsmod | grep cifs

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,293 questions
{count} votes

Accepted answer
  1. James Smith 175 Reputation points
    2023-11-02T13:58:13.35+00:00

    Functional workaround found in a different discussion.

    The current workaround answer for new (i.e. no rollback kernel option) systems is to:

    apt install -y linux-modules-extra-azure
    

    Apparently the problem is that they moved the location of the CIFS driver from fs/cifs/ to fs/smb/client/, but didn't update the include file for building the base modules package to include the new path.

    https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg514627.html

    20 people found this answer helpful.

8 additional answers

Sort by: Most helpful
  1. Matthew Mckenzie 5 Reputation points
    2023-11-13T01:37:49.5+00:00

    For now, I am thinking James Smith's answer should be the accepted answer. It occurs to me that on the next Kernel that 6.2.0-1016 will be #2 and both kernels may have the problem.

    As a minimum we would need to revert the Grub change back to the most recent Kernel and cross our fingers.
    As noted in one of my comments, 6.2.0-1016 is currently the default kernel for new VM's and out of the box they cannot connect to Storage Account Fileshares (or other CIFS). It seems a short term fix would be to roll "extras" into the image.

    1 person found this answer helpful.
    0 comments No comments

  2. Andris Veidemanis 55 Reputation points
    2023-11-09T12:46:10.35+00:00

    This impacts Azure Batch as well.
    New nodes are unusable if Azure Batch provided mount solution is used because after failing mount, start task can't be executed.

    0 comments No comments

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Ian Watts 0 Reputation points
    2023-12-04T23:57:00.37+00:00

    Fast forward to now, there are no previous kernels to revert to on my new VM.... I am now at an impasse.

    0 comments No comments