Mounting a General-Purpose File System Timed Out

Symptom

When a general-purpose file system was mounted to a cloud server using the mount command, message timed out was returned.

Possible Causes

• Cause 1: The network is not stable.
• Cause 2: The network connection is abnormal.
• Cause 3: No VPC endpoint is purchased.
• Cause 4: The DNS configuration on the server is incorrect. As a result, the domain name of the general-purpose file system cannot be resolved, and the mount fails.
• 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 remount is successful, no further action is required.
  • If the problem persists, see the solution for cause 3.
• Cause 3: No VPC endpoint is purchased.

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

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

       nslookup <domain-name-of-the-general-purpose-file-system>

       If the resolved IP address is in the 100.x.x.x network range, the DNS configuration is correct. If the IP address is in another network range, 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. For details about DNS server IP addresses, see What Are Huawei Cloud Private DNS Server 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 File locked
       

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

  3. Press Esc, enter :wq, and press Enter to save and exit.
  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. Remount the file system.
     • If the remount 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 the DNS by referring to Configuring a DNS Server for Domain Name Resolution.
  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 based on the original public image server. For details, see Creating an Image.
     2. Use the private image created in 3.a to re-create an ECS or change to private image for the original ECS by changing the OS.
  4. Log in to the server and remount the file system.