Mounting a File System Failed

When a file system was mounted to a cloud server using the mount command, message access denied was displayed on the server.

Take troubleshooting measures based on possible causes.

Cause 1: The file system has been deleted.
Log in to the console and check whether the file system has been deleted.
- If yes, create a file system or select an existing file system to mount. Ensure that the server and the file system are in the same VPC.
- If no, go to Cause 2.
Cause 2: The server and the file system are not in the same VPC.
Log in to the console and check whether the server and the file system are in the same VPC.
- If yes, go to Cause 3.
- If no, select a file system that is in the same VPC as the server.
Cause 3: The shared path specified in the mount command is incorrect.
1. Log in to the console and check whether the shared path specified in the mount command is the same as that shown on the console.
2. If the shared path specified in the mount command is incorrect, correct it and run the command again.
Cause 4: The DNS configuration of the server is incorrect.
Run the following command to check whether the DNS is correct:

nslookup <File system domain name>

Check whether the resolved IP address is in the 100.x.x.x network range.
- If yes, the DNS configuration is correct. Check other possible causes.
- If no, the DNS configuration is incorrect. Reconfigure DNS by referring to Configuring DNS.
Cause 5: The subdirectory used for mounting is not found.
Mount the file system root directory. Then, create a subdirectory, unmount the file system, and mount the file system using the created subdirectory.