Troubleshoot mount issues

Available in Classic and VPC

You may encounter the following issues while using the NAS service. View the causes and solutions of problems and take proper action.

Mounted server not responding

• After you returned a NAS volume, there was no response from the server you mounted it on.
• The server where you mounted the NAS volume is in a hang state after you returned it.

Cause

• If you delete a volume without umounting it on the server, the server might go into a hang state.
• A server with NAS volume that has been forcibly returned will not umount if there is I/O on a specific file.

Solution

End all processes that have the I/O of a specific file before you unmount it.

umount -l /(mount point)

Mounting a VPC Server on a NAS created in a Classic

• You cannot mount a NAS created in a Classic to a VPC server instance.
• You cannot add a VPC private IP when you set NFS for a NAS created in the Classic.

Cause

• Unable to connect if platforms are different.
• You cannot mount a NAS created in a Classic to a VPC server.

Solution

Replicate the NAS created in the Classic to the VPC. For more information on replicating a NAS, see Replicate NAS volumes.

Errors when the NFS volume is mounted on a Windows server

You mounted an NFS volume on a Windows server for shared use on Linux and Windows, but it is not working properly.

Cause

The Windows series is optimized for CIFS volumes, and the Linux series is optimized for NFS volumes. NFS volumes cannot be mounted on a Windows server.

Solution

Providing technical support for issues caused by using NFS or CIFS volumes together on heterogeneous OSes is difficult. For Windows series, use CIFS volumes, and for Linux series, use NFS volumes.

Errors when the CIFS volume is mounted on a Linux server

The CIFS volume is not mounted on the Linux server.

Cause

NAS services provide volumes optimized for CIFS on Windows and NFS on Linux systems. While mounting and using CIFS volumes on Linux servers is unlimited, you may encounter issues with permission errors and security vulnerabilities.

Solution

• Use CIFS volumes by mounting them on Windows servers.

• When you enter the CIFS mount information on a Linux server, replace the backslash (\) with a forward slash (/).

  $ sudo yum install -y   cifs-utils
  $ sudo mount -t cifs -o user='CIFS authentication ID',password='CIFS authentication PW' //{NAS IP}/{NAS point} {mount point}
  

  Examples are as follows:

  sudo mount -t cifs -o user='CIFS authentication ID',password='CIFS authentication PW',sec=ntlm,vers=1.0 //10.x.x.x/nxxxx_xxxx /mnt/nas/*