Mounting a File System Times Out

Symptom

When a file system is mounted to a cloud server using the mount command, message timed out is returned.

Possible Causes

• Cause 1: The network is not stable.
• Cause 2: The network connection is abnormal.
• Cause 3: A VPC endpoint is not purchased.
• Cause 4: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails. This issue will not occur on SFS Turbo file systems.
• Cause 5: The server that mounts the file system runs Ubuntu18 or later.

Fault Diagnosis

Rectify network faults and mount the file system again.

Solution

• Cause 1 and Cause 2: The network is not stable or the network connection is abnormal.

  Remount the file system after the network issue is addressed.

  • If the mount is successful, no further action is required.
  • If the problem persists, see the solution for cause 3.
• Cause 3: A VPC endpoint is not purchased.

  Buy a VPC endpoint and then remount the file system. For details, see Configure a VPC Endpoint.

  • If the mount is successful, no further action is required.
  • If the problem persists, see the solution for cause 4.
• Cause 4: The DNS configuration of the server is incorrect. As a result, the domain name of the file system cannot be resolved, and the mounting fails.
  1. Check the DNS configuration of the tenant and run the cat /etc/resolv.conf command.
     • If the DNS has not been configured, configure it by referring to Configuring DNS.
     • If the DNS has been configured, run the following command to check whether the configuration is correct:

       nslookup File system domain name

       If the resolved IP address is in network segment 100, the DNS configuration is correct. If the IP address is in another network segment, the DNS configuration is incorrect. In this case, go to 2.

  2. Modify the /etc/resolv.conf configuration file to configure the correct tenant DNS. Specifically, run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. To obtain DNS server IP addresses, see What Are Private DNS Servers and What Are Their Addresses?
     Figure 1 Configuring DNS
     
     The format is as follows:

     nameserver 100.125.1.250

     • If the configuration succeeds, go to 3.
     • If the configuration fails, run the lsattr /etc/resolv.conf command. If the information shown in Figure 2 is displayed, the file is locked.
       Figure 2 A locked file
       

       Run the chattr -i/etc/resolv.conf command to unlock the file. Then, re-configure the DNS and go to 3.

  3. Press Esc, input :wq, and press Enter to save the changes and exit the vi editor.
  4. Set the correct tenant DNS for the subnet of the VPC where the server belongs. By default, the server inherits the DNS configuration of the VPC every time the server restarts. Changing only the server DNS configuration does not resolve the issue completely.

  5. (Optional) Restart the server.
  6. Run the mount command again.
     • If the mount is successful, no further action is required.
     • If the problem persists, see the solution for cause 5.
• Cause 5: The server that mounts the file system runs Ubuntu18 or later.
  1. Reconfigure DNS by referring to Configuring DNS.
  2. Check whether the server running Ubuntu18 or later was created from a private image.
     • If yes, go to 4.
     • If no, go to 3.
  3. Convert the public image server to a private image server.
     1. Create a private image for the server by referring to section "Creating an Image" in the Elastic Cloud Server User Guide.
     2. Use the private image obtained in 3.a to create a server or change the server OS to the created private image by referring to section "Changing the OS" in the Elastic Cloud Server User Guide.
  4. Log in to the server and remount the file system.