This topic describes how to fix issues that may occur when you mount Apsara File Storage NAS file systems.

Important Before you troubleshoot issues, make sure that the mount target is in the Available state. If the mount target is in the Hibernated state, you must re-enable the mount target by using the console or API. For more information, see Hibernate a mount target.

Mount an NFS file system on a Linux ECS instance

If you are unable to mount an NFS file system on a Linux ECS instance, perform the following steps to identify the potential causes:

  1. Log on to the Linux ECS instance.
  2. Run the following command to download the check_alinas_nfs_mount.py script: 
    wget https://nas-client-tools.oss-cn-hangzhou.aliyuncs.com/linux_client/check_alinas_nfs_mount.py -P /tmp/
  3. Run the following command to run the check_alinas_nfs_mount.py script. Then, check whether the returned configurations are valid. 
    python2.7 /tmp/check_alinas_nfs_mount.py file-system-id.region.nas.aliyuncs.com:/ /mnt
    You can configure the parameters in the command based on your business requirements. The following list describes the parameters.
    • file-system-id.region.nas.aliyuncs.com: the domain name of the mount target for the NFS file system. To obtain the domain name of the mount target, perform the following steps: Log on to the NAS console. On the File System List page, click the file system ID. Click the Mount Targets tab. Then, move the pointer over the Mount target icon in the Mount Target column.
    • /: the directory of the NAS file system.
    • /mnt: the mount directory that resides on the current ECS instance.

    After you modify the mount configurations, the script returns a mount command, and a message appears. This indicates that the automatic check is complete.

  4. Copy and run the mount command to mount the file system, and then check the result.

If you are unable to fix some mount issues by using the preceding script, you can manually fix the issues. For more information, see the "Mount an NFS file system on Linux" section in FAQ about mounting.

Mount an SMB file system on a Windows ECS instance

If you are unable to mount an SMB file system on a Windows ECS instance, perform the following steps to identify the potential causes:

  1. Log on to the Windows ECS instance.
  2. Run the following commands in PowerShell or PowerShell ISE to download and run the alinas_smb_windows_inspection.ps1 script. Then, perform the steps that are provided in the script.
    1. Download the alinas_smb_windows_inspection.ps1 script. 
      Invoke-WebRequest https://nas-client-tools.oss-cn-hangzhou.aliyuncs.com/windows_client/alinas_smb_windows_inspection.ps1 -OutFile alinas_smb_windows_inspection.ps1
    2. Run the alinas_smb_windows_inspection.ps1 script. 
      .\alinas_smb_windows_inspection.ps1 -MountAddress abcde-123.region-id.nas.aliyuncs.com -Locale zh-CN

      In the preceding command, abcde-123.region-id.nas.aliyuncs.com specifies the mount target. Replace it with the actual mount target.

For more information, see the "Mount an SMB file system on Windows" section in FAQ about mounting.

Mount an SMB file system on a Linux ECS instance

If you are unable to mount an SMB file system on a Linux ECS instance, perform the following steps to identify the potential causes, or check the /var/log/messages file and the output of the dmesg command.

  1. Check the version of the Linux operating system.
    Linux is not highly compatible with the SMB protocol. The following table lists the Linux operating system versions that are supported by NAS SMB file systems.
    Operating systemOperating system version
    CentOSCentOS 7.6: 3.10.0-957.21.3.el7.x86_64 and later
    Alibaba Cloud LinuxAlibaba Cloud Linux 2.1903: 4.19.43-13.2.al7.x86_64 and later
    DebianDebian 9.10: 4.9.0-9-amd64 and later
    UbuntuUbuntu 18.04: 4.15.0-52-generic and later
    openSUSEopenSUSE 42.3: 4.4.90-28-default and later
    SUSE LinuxSUSE Linux Enterprise Server 12 SP2: 4.4.74-92.35-default and later
    CoreOSCoreOS 2079.4.0: 4.19.43-coreos and later
  2. Check the CIFS client.
    Run the cifs-utils command to check whether the CIFS client is installed on the Linux operating system, or run the mount.cifs command to check whether the CIFS client exists in the specified directory.
    The following table lists the commands that you can run to check whether the CIFS client is installed. If the CIFS client is not installed or is not in the specified directory, reinstall the CIFS client. For more information, see Install a CIFS client.
    Operating systemCommand
    Ubuntu
    sudo apt list cifs-utils
    Debian
    RHEL
    sudo yum list cifs-utils
    CentOS
    OpenSUSE
    sudo zypper search -i cifs-utils
    SLES12-SP2
    CoreOS
    which mount.cifs
  3. Check the network connectivity.
    You can run the ping <VolumeDomainName> command to check the network connectivity.
    1. Check whether the Linux ECS instance and the SMB file system belong to the same Alibaba Cloud account.
      If the Linux ECS instance and the SMB file system belong to different Alibaba Cloud accounts, create an SMB file system by using the account to which the ECS instance belongs, or connect the Linux ECS instance and the SMB file system by using Cloud Enterprise Network (CEN). For more information, see Mount a file system across accounts and regions.
    2. Check whether the Linux ECS instance and the SMB file system reside in the same virtual private cloud (VPC).
      If the Linux ECS instance and the SMB file system reside in different VPCs, create another SMB file system, or connect the Linux ECS instance and the SMB file system by using CEN. For more information, see Mount a file system across VPCs in the same region.
  4. Check port 445.
    • Check that the security group of the Linux ECS instance denies access to the IP address or port 445 of the SMB file system.

      You can run the telnet <VolumeDomainName> 445 command to check the network connectivity.

      If port 445 is disabled, you must add a rule to the security group of the ECS instance for the port. For more information, see Add a security group rule.

    • Check that the Linux ECS instance does not attempt to connect to the network over an unsupported TCP port.
  5. Check the permission group.
    Check whether the permission group of the mount target of the SMB file system allows access to the Linux ECS instance.

    If the Linux ECS instance is not allowed access, modify the configuration of the permission group. For more information, see Manage a permission group.

  6. Check the mount permissions of the ECS instance administrator.

    Check that the administrator of the Linux ECS instance has the root or sudo permissions.

  7. Check the mount command.

    Check that the mount command used to mount the SMB file system is valid. Command syntax:

    sudo mount -t cifs //file-system-id.region.nas.aliyuncs.com/myshare /mnt -o vers=2.0,guest,uid=0,gid=0,dir_mode=0755,file_mode=0755,mfsymlinks,cache=strict,rsize=1048576,wsize=1048576

    If the parameters specified in the mount command are invalid, change the parameter settings. For more information about the mount parameters, see Mount an SMB file system on a Linux ECS instance.

  8. Check Security-Enhanced Linux (SELinux) settings.
    Check that the SELinux settings for the mount directory are valid.
  9. Check the number of compute nodes on which the file system is mounted at the same time.
    Check whether the number of Linux ECS instances on which the file system is mounted exceeds 1,000.
    • If the number exceeds the upper limit, change the number based on your business scenario.
    • If the number does not exceed the upper limit, contact NAS technical support.

      When you submit a ticket, you must provide the file system information, version of your Linux distribution, mount commands, /var/log/messages file, and output of the dmesg command.

For more information, see the "Mount an SMB file system on Linux" section in FAQ about mounting.

Mount a General-purpose NFS file system on a Windows ECS instance

If you are unable to mount a General-purpose NFS file system on a Windows ECS instance, perform the following steps to identify the potential causes:

  1. Check the account.

    Check whether the ECS instance and the mount target belong to the same account. If the ECS instance and the mount target belong to different accounts, you can use CEN to connect the networks of the accounts and then mount the NFS file system. For more information, see Mount a file system across accounts and regions.

  2. Check the network of the mount target.

    Check whether the ECS instance and the mount target belong to the same VPC. If the ECS instance and the mount target belong to different VPCs, you can use CEN to connect the VPCs and then mount the NFS file system. For more information, see Mount a file system across VPCs in the same region.

  3. Check port 2049.

    Check whether the security group of the ECS instance allows access to port 2049 of the mount target. If the security group of the ECS instance does not allow access to port 2049 of the mount target, modify the security group rule. For more information, see Modify security group rules.

    You can run the telnet or Test-NetConnection command to check the port connectivity.
    • Run the telnet command in Command Prompt. 
      telnet $mount_point.$region.nas.aliyuncs.com 2049
    • Run the Test-NetConnection command in PowerShell. 
      Test-NetConnection $mount_point.$region.nas.aliyuncs.com -Port 2049
  4. Check the permission group of the NFS file system.

    Check whether the permission group of the mount target allows access to the ECS instance. If the permission group of the mount target does not allow access to the ECS instance, modify the configuration of the permission group. For more information, see Manage a permission group.

For more information, see the "Mount an NFS file system on Windows" section in FAQ about mounting.