locked
mount error(11): Can't mount Azure file share from an on-premise linux server RRS feed

  • Question

  • Hi,

    I'm not able to mount an Azure file share from an on-premise Ubuntu 18.04.! The Ubuntu is running in a Docker container. I use the following command to run the docker:

    docker run --rm --cap-add SYS_ADMIN --cap-add DAC_READ_SEARCH -i -t rbase:0.0.1 /bin/bash

    Detailed error message:

    - mount error(11): Resource temporarily unavailable
    - Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

    Any help is very welcome!

    Log from AzureFileDiagnostic.sh:

    root@93ed7459340a:/tmp# bash AzureFileDiagnostics.sh

    2019-02-08T13:49:24.451Z Checking: Create a folder MSFileMountDiagLog to save the script output

    2019-02-08T13:49:24.462Z Checking: Client running with "Ubuntu" version 18.04, kernel version is 4.9.125-linuxkit

    2019-02-08T13:49:24.466Z Checking: Check if cifs-utils is installed
    2019-02-08T13:49:24.468Z Cifs-utils is already installed on this client

    2019-02-08T13:49:24.470Z Checking: Check if client has at least SMB2.1 support
    2019-02-08T13:49:24.474Z System supports SMB2.1

    2019-02-08T13:49:24.476Z Checking: Check if client has SMB 3 Encryption support
    2019-02-08T13:49:24.481Z System supports SMB 3 Encryption

    2019-02-08T13:49:24.483Z Checking: Check if client has been patched with the recommended kernel update for idle timeout issue
    2019-02-08T13:49:24.493Z Warning: Kernel has not been patched with the fixes that prevent idle timeout issues, more information, please refer to https://docs.microsoft.com/en-us/azure/storage/storage-troubleshoot-linux-file-connection-problems#mount-error112-host-is-down-because-of-a-reconnection-time-out

    2019-02-08T13:49:24.494Z Checking: Check if client has any connectivity issue with storage account
    2019-02-08T13:49:24.496Z Type the storage account name, followed by [ENTER]:
    XXX
    2019-02-08T13:49:46.587Z Type the share name, followed by [ENTER]:
    test
    2019-02-08T13:50:07.355Z Choose the Azure Environment:
    1) azurecloud         3) azuregermancloud
    2) azurechinacloud    4) azureusgovernment
    Please enter your choice: 1
    2019-02-08T13:50:10.347Z Storage account FQDN is XXX.file.core.windows.net
    2019-02-08T13:50:10.349Z Getting the Iptables policies
    sudo: iptables: command not found
    2019-02-08T13:50:10.354Z Test the storage account IP connectivity over TCP port 445
    2019-02-08T13:50:10.381Z Port 445 is reachable from this client.

    2019-02-08T13:50:10.383Z Checking: Script has validated the client settings and do you want to map drive by script?
    1) yes
    2) no
    Please enter your choice: 1

    2019-02-08T13:50:16.963Z Checking: Do you want to tun on diagnostics logs
    1) yes
    2) no
    Please enter your choice: 1

    2019-02-08T13:50:19.038Z Checking: type the local mount point, followed by [ENTER]:
    /mnt

    2019-02-08T13:50:22.421Z Checking: Type the storage account access key, followed by [ENTER]:
    XXX
    sh: 1: cannot create /sys/kernel/debug/dynamic_debug/control: Directory nonexistent
    sh: 1: cannot create /sys/kernel/debug/dynamic_debug/control: Directory nonexistent
    sh: 1: modprobe: not found
    sh: 1: cannot create /proc/fs/cifs/cifs

    FYI: Read-only file system

    2019-02-08T13:50:43.688Z Checking: Try with mounting share using SMB3.0
    2019-02-08T13:50:43.691Z mount -t cifs //XXX.file.core.windows.net/test /mnt -o vers=3.0,username=XXX,password=XXX,dir_mode=0777,file_mode=0777,sec=ntlmssp

    mount error(11): Resource temporarily unavailable
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)


    • Edited by chrismasch Friday, February 8, 2019 6:23 PM better description of error
    Friday, February 8, 2019 1:59 PM

Answers

  • Ubuntu 18.04 isn’t supported.

    Minimum recommended versions with corresponding mount capabilities (SMB version 2.1 vs SMB version 3.0)

    For more information on prerequisites refer to this article.


    Monday, February 11, 2019 4:48 AM

All replies

  • Ubuntu 18.04 isn’t supported.

    Minimum recommended versions with corresponding mount capabilities (SMB version 2.1 vs SMB version 3.0)

    For more information on prerequisites refer to this article.


    Monday, February 11, 2019 4:48 AM
  • Thank you!

    I tried Centos (centos-release-7-6.1810.2.el7.centos.x86_64) instead facing exact the same problem. Here is my setup:

    - Docker Host: Windows 10 (1803)

    - Docker Desktop Version 2.0.0.2 (30215)

    - CIFS-Utils is installed

    - No firewall issues (nmap gives me: 445/tcp open  microsoft-ds)

    Error message:

    mount error(11): Resource temporarily unavailable
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

    Monday, February 11, 2019 7:56 AM
  • Just for clarification: I presume that you have followed the steps mentioned for performing the Azure File Share.

    SMB Version Supported SMB 2.1 and 3.0, Have tried with the both version? 

    Can you perform "TcptestSucceeded" and share me the status? 

    You may have stale mounts - try clearing all CIFS mounts with:

    umount -a -f cifs
    
    Then re-mount everything in the fstab file:
    mount -a
    

    You have rebooted the Linux clients and tried to mount them manually

    You may also refer to the suggestion mentioned in the SO thread. Troubleshooting tool for Azure Files mounting errors on Linux

    Additional information:

    If you are using Azure VM, This happens only when storage account is in a different region than the virtual machine. For now, they must be in the same region. Both latest version of Ubuntu and CentOS 7.1 support SMB 2.1 so they can be used to mount the file share created in Azure File Storage (within same region)

    If the issue persists, kindly share the screen shot of the error message with the code.

    Monday, February 11, 2019 10:55 AM
  • Your assumption is correct I followed all the steps.

    Just for clarification: I try to mount from on premises. My understanding is that I can only use SMB 3.0 (encrypted) as mentioned in your link. I'm using centos-release-7-6.1810.2.el7.centos.x86_64 (CentOS 7.5+ should work).

    To check the ports I used "nmap":

    Starting Nmap 6.40 ( http://nmap.org ) at 2019-02-11 11:40 UTC
    Nmap scan report for STORAGENAME.file.core.windows.net (XX.XXX.XXX.XXX)
    Host is up (0.0056s latency).
    Not shown: 997 filtered ports
    PORT    STATE SERVICE
    80/tcp  open  http
    443/tcp open  https
    445/tcp open  microsoft-ds

    When I try to mount the Azure fileshare I get:

    mount -t cifs //STORAGENAME.file.core.windows.net/SHARENAME /mnt -o vers=3.0,username=STORAGENAME,password=XXX,dir_mode=0777,file_mode=0777,sec=ntlmssp
    mount error(11): Resource temporarily unavailable
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    I used the troubleshooting tool which was perfectly fine until I tried to mount (getting the same error message as mentioned above).

    I tried clearing all CIFS mounts with no effect.

    Monday, February 11, 2019 11:51 AM
  • @chrismasch In meanwhile can you try to use SMB 2.0 and let me know the status? It will be more useful for future troubleshooting. 
    Monday, February 11, 2019 1:17 PM
  • Ubuntu should be supported starting at 16.04 (when they had the SMB 3 with encryption). Are you unable to mount directly from the Linux VM as well?

    Can you share the exact mount command?

    Here’s the page with the exact information on supported Linux distros: https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-linux

    Friday, February 15, 2019 8:24 AM
  • I followed the description you posted step by step. I already posted my exact mount command above:

    mount -t cifs //STORAGENAME.file.core.windows.net/SHARENAME /mnt -o vers=3.0,username=STORAGENAME,password=XXX,dir_mode=0777,file_mode=0777,sec=ntlmssp
    
    I don't have any issues with the mount from a Linux VMs (within Azure subscription) but I can't mount from an on-prem machine.




    Wednesday, February 20, 2019 2:21 PM
  • @chrismasch can you share me the screenshot of the error message?
    Wednesday, February 20, 2019 5:01 PM
  • As you can see in my post above the error message is:

    mount error(11): Resource temporarily unavailable
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    In my initial post you can see the log from AzureFileDiagnostic.sh.

    Friday, February 22, 2019 1:27 PM
  • This may require a deeper investigation, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email toAzCommunity[at]Microsoft[dot]com referencing this thread. Please mention "ATTN subm" in the subject field. Thank you for your cooperation on this matter and look forward to your reply.

    Monday, February 25, 2019 6:52 AM
  • Thank you.  I have a dev support plan. I will file a support ticket within the next days.
    • Edited by chrismasch Monday, February 25, 2019 6:58 AM typo
    Monday, February 25, 2019 6:56 AM
  • @chrismasch Thank you! You can provide me the ticket number and also share the troubleshooting steps once the issue is been fixed, which would certainly help other community members.
    Monday, February 25, 2019 9:14 AM