File Storage NAS:Troubleshoot file system mount failures

Automatic check script for failures to mount an NFS file system on a Linux server

Failures to mount a Network File System (NFS) file system on a Linux server can have multiple causes. Follow these steps to use the automatic check script to identify the issue.

1. Log on to the Linux server where the file system failed to mount.

2. Download the automatic check script.

   wget https://nas-client-tools.oss-cn-hangzhou.aliyuncs.com/linux_client/check_alinas_nfs_mount.py -P /tmp/

3. Run the automatic check script and check whether the returned configuration is correct.

   python2.7 /tmp/check_alinas_nfs_mount.py file-system-id.region.nas.aliyuncs.com:/ /mnt

   The following table describes the important parameters. Replace the placeholder values with your actual values.

   • The mount target address of a NAS NFS file system uses the format file-system-id.region.nas.aliyuncs.com. To obtain the address, go to the NAS console, click the target file system, click Mount Targets, and then hover over the icon in the Mount Target Address column.

   • /: The root directory of the NAS file system.

   • /mnt: The local path on the current server to which you want to mount the file system.

   After you correct the mount configuration, the automatic check script returns a mount command and a message that indicates that the check is complete.

4. Copy the mount command, execute it, and check the result.

Automatic check script for failures to mount an SMB file system on a Windows server

Failures to mount a Server Message Block (SMB) file system on a Windows server can have multiple causes. Follow these steps to use the automatic check script to identify the issue.

1. Log on to the Windows server where the file system failed to mount.

2. In PowerShell or PowerShell ISE, run the following commands to download and run the mount troubleshooting script. Then, perform the operations based on the solution provided by the script.

   1. You can download the troubleshooting 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 troubleshooting script.

      .\alinas_smb_windows_inspection.ps1 -MountAddress abcde-123.region-id.nas.aliyuncs.com -Locale en-US

      In the command, abcde-123.region-id.nas.aliyuncs.com is the mount target. Replace it with your actual value.

Troubleshoot failures to mount an SMB file system on a Linux server

Failures to mount an SMB file system on a Linux server can have multiple causes. Follow these steps to troubleshoot the issue. You can also check the output of the /var/log/messages and dmesg files.

1. Check the Linux operating system version.

   Because Linux systems have limited compatibility with the SMB protocol, NAS SMB file systems support only the following Linux operating system versions.

   Operating system	Version
   CentOS	CentOS 7.6 64-bit: 3.10.0-957.21.3.el7.x86_64 and later
   Alibaba Cloud Linux	Alibaba Cloud Linux 2.1903 64-bit: 4.19.43-13.2.al7.x86_64 and later Alibaba Cloud Linux 3.2104 64-bit: 5.10.23-4.al8.x86_64 and later
   Debian	Debian 9.10 64-bit: 4.9.0-9-amd64 and later
   Ubuntu	Ubuntu 18.04 64-bit: 4.15.0-52-generic and later
   openSUSE	openSUSE 42.3 64-bit: 4.4.90-28-default and later
   SUSE Linux	SUSE Linux Enterprise Server 12 SP2 64-bit: 4.4.74-92.35-default and later
   CoreOS	CoreOS 2079.4.0 64-bit: 4.19.43-coreos and later

2. Check the CIFS client.

   Confirm that the Common Internet File System (CIFS) client (cifs-utils) is installed on the Linux operating system, or that mount.cifs is in a directory specified by the PATH environment variable.

   Run the following commands to check if 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 system	Executing a command
   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.

   Run the ping <VolumeDomainName> command to check the network connectivity.

   1. Confirm that the Linux ECS instance and the SMB file system are in the same Alibaba Cloud account.

      If they are not in the same Alibaba Cloud account, create an SMB file system in the account to which the ECS instance belongs, or connect the networks using Cloud Enterprise Network (CEN). For more information, see Use CEN to mount a NAS file system across accounts and regions.

   2. Confirm that the Linux ECS instance and the SMB file system are in the same VPC.

      If they are not in the same VPC, create a new SMB file system, or connect the networks using CEN. For more information, see Use CEN to mount a NAS file system across VPCs in the same region.

4. Check port 445.

   • Check if the security group for the Linux ECS instance is blocking the IP address of the SMB file system or port 445.

     Run the telnet <VolumeDomainName> 445 command to check the connectivity.

     If port 445 is not open, add a security group rule that allows access to port 445 to the security group of the target ECS instance. For more information, see Add a security group rule.

   • Confirm that the Linux ECS instance is not trying to connect through an unsupported TCP port.

5. Check the permission group.

   Confirm that the permission group of the mount target for the SMB file system allows access from the ECS instance.

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

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

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

7. Check the mount command.

   Confirm that the mount command for the SMB file system is correct. The manual mount command is as follows:

   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 mount command parameters are incorrect, use the correct command. For more information about the mount parameters for an SMB file system on a Linux server, see Mount parameters for an SMB file system on a Linux server.

8. Check SELinux.

   Confirm that the SELinux settings for the target mount directory are correct.

9. Check the number of compute nodes on which the file system is mounted simultaneously.

   Check if an Elastic Compute Service (Linux) instance has more than 1,000 mount connections to a single file system.

   • If the limit is exceeded, make adjustments as needed.

   • If the limit is not exceeded, submit a ticket for assistance.

     Provide the file system information, Linux version, specific mount command, and the output from the `/var/log/messages` and `dmesg` files.

Troubleshoot failures to mount a General-purpose NFS file system on a Windows system

Failures to mount a General-purpose NFS file system on a Windows system can have multiple causes. Follow these steps to troubleshoot the issue.

1. Check the account.

   Confirm that the ECS instance and the mount target are in the same account. If the ECS instance and the mount target are not in the same account, connect the accounts using CEN and then mount the NFS file system. For more information, see Use CEN to mount a NAS file system across accounts and regions.

2. Check the mount target network.

   Confirm that the ECS instance and the mount target are in the same VPC. If the ECS instance and the mount target are not in the same VPC, connect the VPCs using CEN and then mount the NFS file system. For more information, see Use CEN to mount a NAS file system across VPCs in the same region.

3. Check ports 2049 and 111.

   Confirm that the ECS security group allows access to ports 2049 and 111 of the mount target. If the ECS security group does not allow access to ports 2049 and 111 of the mount target, modify the security group rules. For more information, see Modify security group rules.

   Use the telnet command or the Test-NetConnection command to test port connectivity.

   • Use the telnet command in Command Prompt.

     telnet $mount_point.$region.nas.aliyuncs.com 2049
     telnet $mount_point.$region.nas.aliyuncs.com 111

   • Use the Test-NetConnection command in PowerShell.

     Test-NetConnection $mount_point.$region.nas.aliyuncs.com -Port 2049
     Test-NetConnection $mount_point.$region.nas.aliyuncs.com -Port 111

4. Check the permission group of the NFS file system.

   Confirm that the permission group of the mount target allows access from the ECS instance. If the permission group of the mount target does not allow access from the ECS instance, modify the permission group configuration. For more information, see Modify the configuration of a permission group.

How do I resolve the 'subdirectory does not exist' error?

Error message: mount.nfs: access denied by server while mounting xxxx.nas.aliyuncs.com:/<dir>

When you mount a subdirectory, this error occurs because the NAS subdirectory `` specified in the mount command does not exist. First, mount the NAS root directory. After the mount is successful, create the required subdirectory and then mount the subdirectory again. For more information, see How do I create and mount a subdirectory of a NAS file system on a Linux system?.

How to resolve an error when renaming an ECS instance?

Problem

When you use NFSv4.0 to mount a file system, the error message mount.nfs: Operation not permitted or mount.nfs: an incorrect mount option was specified is returned. However, the file system can be successfully mounted using NFSv3.

Cause

A conflict can occur with some kernel versions. This happens if you try to mount a file system on an ECS instance that has the same hostname as another ECS instance where the same NFS mount target is already mounted using NFSv4.0.

Solution

1. Run the following command on the ECS instance where the error occurred.

   echo 'install nfs /sbin/modprobe --ignore-install nfs nfs4_unique_id=`cat /sys/class/dmi/id/product_uuid`' >> /etc/modprobe.d/nfs.conf

2. Restart the ECS instance during off-peak hours.

   You can also manually unmount all mounted NFS file systems and run the rmmod command to uninstall the NFSv4.0 client and the NFS kernel module.

3. Mount the NFS file system again. For more information, see Mount an NFS file system.

What do I do if the mount.nfs: No such device error is returned when I mount an NFS file system?

Problem

When you mount a NAS NFS file system on an ECS instance, the following error message is returned.

mount.nfs: No such device

Cause

The options sunrpc tcp_slot_table_entries=128 configuration in the /etc/modprobe.d/sunrpc.conf file may be misspelled as options sunrpc tcp_slot_entries=128. This prevents the sunrpc module from loading into the kernel correctly.

Solution

1. Change the configuration in the /etc/modprobe.d/sunrpc.conf file to options sunrpc tcp_slot_table_entries=128.

2. Run the modprobe sunrpc command to load the sunrpc module.

3. Mount the NFS file system again.

What do I do if the mount: can't find /root/nas in /etc/fstab error is returned when I mount an NFS file system?

Problem

When you mount a NAS NFS file system on an ECS instance, the following error message is returned.

mount: can't find /root/nas in /etc/fstab

Cause

The command format may be incorrect.

Solution

Use the correct mount command to mount the NAS NFS file system. For more information about the mount command parameters for an NFS file system on a Linux server, see Mount command parameters.

• For a General-purpose NAS file system, run one of the following commands.

  To mount a file system using the NFSv3 protocol:

  sudo mount -t nfs -o vers=3,nolock,proto=tcp,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport file-system-id.region.nas.aliyuncs.com:/ /mnt

  To mount a file system using the NFSv4 protocol:

  sudo mount -t nfs -o vers=4,minorversion=0,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport file-system-id.region.nas.aliyuncs.com:/ /mnt

• For an Extreme NAS file system, run the following command.

  sudo mount -t nfs -o vers=3,nolock,noacl,proto=tcp,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport file-system-id.region.extreme.nas.aliyuncs.com:/share /mnt

In the commands, file-system-id.region.nas.aliyuncs.com is the mount target address of the NFS file system. Replace it with your actual value.

How do I resolve the file handle error when I mount a General-purpose NAS NFS file system?

• Cause

  The Locking registry may not exist, or the Locking registry exists but its Locking value is not 1.

• Solution

  1. Open Command Prompt and run the regedit command to open Registry Editor.

  2. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > ClientForNFS > CurrentVersion > Users > Default > Mount, right-click a blank area, and then choose New > DWORD (32-bit) Value.

  3. Rename the registry entry to Locking and double-click Locking. In the Edit DWORD (32-bit) Value window, set the Value Data to 1.

  4. Click OK.

  5. Restart the ECS instance.

  6. Mount the General-purpose NAS file system using the NFS protocol again.

     mount -o nolock -o mtype=hard -o timeout=60 \\file-system-id.region.nas.aliyuncs.com\! Z:

     Replace the drive letter Z: and the mount target domain name file-system-id.region.nas.aliyuncs.com with your actual values.

  7. Run the mount command to check whether the mount is successful.

     After mounting, verify that the output includes `mount=hard`, `locking=no`, and a timeout value of 10 or greater. Otherwise, the mount has an issue.

     

How do I check for and resolve system error 53 when mounting an SMB file system on a Windows server?

• Error message

  The network path was not found.

• Causes

  • The network connection is unavailable.

  • The TCP/IP NetBIOS Helper service is not started.

  • LanmanWorkstation is not correctly configured in the registry.

• Solution

  1. Run the ping <mount_target_address> command to check if the mount target address is connected and if the latency is normal.

     • If the network connection is normal, go to the next step.

     • If the network is not connected, troubleshoot the network issue:

       • Confirm that the mount command is correct and does not contain extra or missing characters, such as /, \, spaces, or myshare.

         The correct format of the command to mount an SMB file system is:

         net use <target_drive_letter> \\<mount_target_address>\myshare

         Example:

         net use z: \\xxxx.cn-hangzhou.nas.aliyuncs.com\myshare

       • In the console, confirm that the file system type is SMB.

       • Confirm that the mount target address is correct.

       • Confirm that the ECS instance and the mount target are in the same VPC.

       • For clients connected across VPCs or through a VPN, confirm that the network configuration is correct.

  2. Run the telnet <mount_target_address> 445 command to check if the SMB service is available.

  3. Confirm that the TCP/IP NetBIOS Helper service is started. For more information, see Mount an SMB file system.

  4. Open Registry Editor, and then navigate to HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > NetworkProvider > Order. Confirm that the ProviderOrder value includes LanmanWorkstation. If not, add LanmanWorkstation.

  If the preceding methods do not resolve the issue, check if Windows Defender Firewall is blocking SMB-related network requests.

  

  

How do I check for and resolve system error 58 when mounting an SMB file system on a Windows server?

• Error message

  The specified server cannot perform the requested operation.

• Cause

  The client SMB protocol version is not compatible.

• Solution

  Confirm that the Windows system version is Windows Server 2008 R2 or later (but not Windows Server 2008).

How do I check for and resolve system error 64 when mounting an SMB file system on a Windows server?

• Error message

  The specified network name is no longer available.

• Cause

  • The NAS permission group does not allow access from the target ECS instance.

  • The private IP address or VPC IP address of the target ECS instance is not correctly configured in the NAS permission group.

  • The service has an overdue payment.

  • When you mount a file system in a classic network, the ECS instance and the NAS file system do not belong to the same Alibaba Cloud account.

  • The file system type is not SMB.

• Solution

  You do not have permission to access the NAS file system resource. Troubleshoot the issue from the following aspects.

  1. Confirm that the permission group of the file system mount target includes the private IP address or VPC IP address of the machine.

  2. Confirm that the Alibaba Cloud account has no overdue payments.

  3. When you mount a file system in a classic network, confirm that the ECS instance and the NAS file system belong to the same Alibaba Cloud account.

  4. Confirm that the file system type is SMB.

How do I check for and resolve system error 67 when mounting an SMB file system on a Windows server?

• Error message

  The network name cannot be found.

• Causes

  Key network services are not started.

• Solution

  Start the following services. For more information, see Mount an SMB file system.

  1. Enable the Workstation service.

  2. Enable the TCP/IP NetBIOS Helper service.

How do I check for and resolve system error 85 when mounting an SMB file system on a Windows server?

• Error message

  The local device name is already in use.

• Cause

  The target drive letter is already in use.

• Solution

  Change the target drive letter and mount the file system again.

How do I check for and resolve system error 1231 when mounting an SMB file system on a Windows server?

• Error message

  The network location cannot be reached.

• Cause

  • Client for Microsoft Networks is not installed or enabled on the system.

  • File and Printer Sharing for Microsoft Networks is not installed or enabled on the system.

• Solution

  Install and enable Client for Microsoft Networks or File and Printer Sharing for Microsoft Networks.

  If Client for Microsoft Networks or File and Printer Sharing for Microsoft Networks is installed but not enabled, select the corresponding option. You can install and enable the options as follows.

  

  1. Open the Network and Sharing Center and click the active network connection.

  2. Click Properties.

  3. In the WLAN Properties dialog box, click Install.

     • Install Client for Microsoft Networks.

       1. In the Select Network Feature Type dialog box, select Client and click Add.

       2. Select Client for Microsoft Networks and click OK.

     • Install File and Printer Sharing for Microsoft Networks.

       1. In the Select Network Feature Type dialog box, select Service and click Add.

       2. Select Microsoft > File and Printer Sharing for Microsoft > OK

How do I check for and resolve system error 1272 when mounting an SMB file system on a Windows server?

• Error message

  System prompt: You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.

• Causes

  The security policy of the Windows system blocks users from accessing the SMB file system with guest access permissions (Guest Auth).

• Solution

  If your system version is later than Windows Server 2016 (but not Windows Server 2016), modify the following registry item to allow guest access permissions (Guest Auth).

  1. Log on to the ECS server where the file system is mounted.

  2. Open Command Prompt and run the regedit command to open Registry Editor.

  3. In the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters path, confirm that the value of the AllowInsecureGuestAuth registry key is 1.

     1. If the value of the AllowInsecureGuestAuth registry key is 0, right-click AllowInsecureGuestAuth and change the value in Value data (V) to 1.

     2. If the AllowInsecureGuestAuth registry key is not found, switch to PowerShell and run the following command to add the AllowInsecureGuestAuth registry key.

        New-ItemProperty -Path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters -Name AllowInsecureGuestAuth -PropertyType DWORD -Value 1

  4. Mount the SMB file system again.

     net use Z: \\file-system-id.region.nas.aliyuncs.com\myshare

     If error 1272 is returned again, the value of the RequireSecuritySignature registry key may be 1. Change this value to 0 and then mount the SMB file system again.

     Path of the RequireSecuritySignature registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.

  For more information, see Guest access in SMB2 disabled by default in Windows and Overview of Server Message Block signing.

How do I check for and resolve system error 3227320323 when mounting an SMB file system on a Windows server?

• Error message

  System error 3227320323 has occurred.

• Cause

  The Microsoft network client: Digitally sign communications (always) policy is enabled in Windows. Anonymous mounts cannot be signed because they do not provide identity information.

• Solution

  Disable the Microsoft network client: Digitally sign communications (always) policy and mount the file system again. To disable this policy, perform the following steps.

  1. Use the Win+R keyboard shortcut, enter gpedit.msc, and open the Local Group Policy Editor.

  2. Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Double-click Microsoft network client: Digitally sign communications (always), select Disabled, and click OK.

     

How do I check for and resolve system error 1312 when mounting an SMB file system on a Windows server?

• Error message

  Windows System Error 1312.

• Cause

  When you use the New-SmbGlobalMapping PowerShell command to mount the file system, the username or workgroup is incorrect.

• Solution

  Check the correct workgroup name in your computer's properties. Then, in the dialog box that appears when you run the mount command, enter the correct username or workgroup. For example, the username is workgroup\administrator and the password is ECSadministrator.

How do I resolve the failure to automatically mount an NFS file system on server startup?

Problem

The server is configured to automatically mount an NFS file system after a restart, but the automatic mount fails on restart.

Cause

The server's system may be CentOS 7.0. By default, CentOS 7.0 does not process non-local file systems in fstab, and the `remote-fs.target` service is in the `disabled` state. This causes the automatic mount of the NFS file system to fail after the cloud server is restarted.

Solution

Choose one of the following solutions to enable automatic mounting of the NFS file system on server startup. Then, open the `/etc/fstab` configuration file and add the mount configuration. For information about how to add a mount configuration, see Mount an NFS file system.

• Solution 1: Permanent fix

  Run the following commands in sequence to enable the `remote-fs.target` service. This allows the NFS file system to be automatically mounted on server startup.

  systemctl start remote-fs.target

  systemctl enable remote-fs.target

• Solution 2: Temporary fix

  Run the following command in the system's `rc.local` file to enable the `remote-fs.target` service. This allows the NFS file system to be automatically mounted on server startup.

  [ ! -f /etc/rc.local ] && echo '#!/bin/bash' > /etc/rc.local; echo "mount -a -t nfs" >> /etc/rc.local; chmod +x /etc/rc.local

Why can't IIS on Windows Server 2016 load files from an SMB volume?

For the solution to the issue where Internet Information Services (IIS) on Windows Server 2016 cannot load files from an SMB volume, see Install and configure an AD domain.

How do I check for and resolve issues with soft mounting an NFS file system on a Windows server?

• Problem description

  When you use an NFS file system on a Windows system, the default mount mode is `soft`. In the following scenarios, the soft mode affects data consistency and can cause applications to exit unexpectedly.

  • Data consistency: When you use a soft mount, if a request times out, an error is returned. For the application, this operation is incomplete. For the server, this request may have already been executed, which can cause data inconsistency.

  • Unexpected application exit: When you use a soft mount, if a request times out, a timeout error is returned. In some languages, an exception is thrown. If the application does not handle the exception, it exits unexpectedly.

• Solution

  In a Windows system, using a hard mount for an NFS file system can avoid the preceding problems.

  1. Run the mount command to check the current mount mode.

     • If mount=soft is displayed, follow these steps to make corrections.

     • If mount=hard is displayed, no correction is needed.

  2. Stop the application that is currently using this NFS file system.

  3. Unmount the NFS file system.

     umount H:

     Replace the drive letter H: in the unmount command with your actual drive letter.

  4. Mount the NFS file system again.

     mount -o nolock -o mtype=hard -o timeout=60 \\xxxxxx.cn-hangzhou.nas.aliyuncs.com\! h:

     Replace the mount target address xxxxxx.cn-hangzhou.nas.aliyuncs.com and the drive letter h: with your actual values.

  5. Run the mount command to verify the mount result.

     If the returned information includes `mount=hard`, `locking=no`, and a `timeout` parameter with a value greater than or equal to 10, the mount is successful.

How do I resolve errors when mounting an NFS file system on a Windows server?

• Problem description: Invalid file handle

  Solution: Follow the correct steps and parameter settings to mount the file system again. For more information, see Mount an NFS file system (General-purpose NAS).

• Problem description: Network error - 53

  Solution: Follow the correct steps and parameter settings to mount the file system again. For more information, see Mount an NFS file system (General-purpose NAS).

• Problem description: Network error - 1222

  Solution: Install the NFS client and then perform the mount operation again. For more information, see Step 1: Install an NFS client.

Error when you mount a NAS file system on a container: access denied by server while mounting <mount path>

Symptoms

When you mount a NAS file system for a container, the error access denied by server while mounting <mount_address> is returned.

Cause

Possible causes include the following:

1. The mount directory does not exist.

2. The host role used to start the container does not have permission to modify the NAS file system.

3. The permission group configured for the mount target does not grant access to the container.

Solution

1. Confirm that the mount directory exists.

   Run the cd <mount_directory> command to verify that the mount directory exists.

2. Confirm that the user who starts the container has root permissions.

   If the user who starts the container does not have root permissions, you must log on to the NAS file system as the root user, change the permission attributes, and then mount the file system. This keeps the container user's permissions consistent with the permissions of the mount target's file system. When you mount a file system within a container, you must run the container in privileged mode.

3. Confirm that the permission group configured for the mount target includes the container's IP address.

   1. Log on to the NAS console.

   2. In the left navigation pane, select File System > File System List.

   3. In the top menu bar, select a region.

   4. On the File System List page, click Manage in the Actions column for the target file system.

   5. On the file system details page, click Mount Targets.

   6. In the Permission Group column of the mount target list, click a permission group name to open its Rules page.

   7. Confirm that the target container's IP address has been added to the permission group rule.

      If the target container's IP address is not in the permission group rule, add it. For more information, see Add a rule to a permission group.

What do I do if I fail to use Cloud Assistant to mount, unmount, or query the status of file systems in batches?

First, confirm that the entered mount parameters meet the conditions. Next, observe the error code in the command result and proceed based on the error message. For more information, see Error messages. Finally, use the one-click mount feature to try the operation on a single ECS instance first. If it fails, examine the relevant error message to resolve the issue.

You can also use the NAS console to first mount a file system on one ECS instance. If the mount fails, proceed based on the message that appears.

What are the possible reasons for a file system mount failure in the console?

To resolve the mount failure, troubleshoot the issue based on the following possible causes.