How to Troubleshoot the Fault that the File System Cannot be Mounted

Publication Date:  2012-07-18 Views:  231 Downloads:  0
Issue Description
In an office, after a disk enclosure of the N8300 is recovered after powered off, the relevant file systems cannot be mounted. The scanbus operation hangs. As a result, follow-up configurations cannot be performed.
Alarm Information
Handling Process
Step 1  Power on the disk enclosure.
Step 2  Wait until the disk enclosure is completely powered on.
Step 3  Log in to the master node as user support and run the ps -ef|grep scanbus command.
N8300_01:/ # ps -ef |grep scanbus
root     30525 14067 20 23:51 pts/2    00:00:00 /bin/bash /opt/VRTSnasgw/scripts/
root     30884 30525 39 23:51 pts/2    00:00:00 /bin/bash /opt/VRTSnasgw/scripts/ N8300_01
root     31152 20952  0 23:51 pts/8    00:00:00 grep scanbus
root     31155 30884  0 23:51 pts/2    00:00:00 /bin/bash /opt/VRTSnasgw/scripts/ N8300_01
Check whether the scanbus process always exists. If yes, the scanbus operation hangs.
Run the reboot command to restart the master node. The cluster automatically chooses another node as the master node.
Step 4  Log in to the new master node as user support and run the ps -ef |grep scanbus command. If the scanbus process does not exist, the hang fault is rectified.
Step 5  Run the vxdisk list command to check whether the correct disk information is correct. Check the disk information. If not all disks is displayed, log in as user master and enter the Storage interface. Run the scanbus command to scan disks.
Step 6  When disks are normal, run the fs online filename command to get file systems online.
Step 7  Check whether the NFS and CIFS services are online. If no, manually get them online.
Root Cause
If a disk enclosure is powered off, the disk information and file system information in the cluster are affected. The cluster automatically sets the relevant resource group status to offline to guarantee data consistency.
Enhance routine check to avoid abnormal power-off of the devices.