Recently called in to work on new customers snap server 4200. The server is in a raid 5 configuration and has only one volume. The server will not mount the volume. Customer does not know what happened just stopped working 3 weeks ago. I suspected power outage. After going through step by step from snap support of :
When the Snap Server with a GuardianOS version running on it abruptly shuts down due to a loss of power, this is called an "ungraceful shutdown". The web interface shows the recovery console and users are unable to access the files and folders on the Snap Server shares.
The first thing to check here is to have customer go to the following site on the Snap Server:
"Snap Server Name" or "Snap Server IP Address"/debug.html
This will get the customer to the Debug Console window. From there, enter "df -h" in the "Command" field and press "OK" button to execute. Check the root file system.
At this point, ask customer if they have backed up their data from this Snap Server recently. Advise them that the next few steps may affect the data on this server, if not outright lose it. Also ask customer if they have Putty.exe installed on their workstation. If not they will need it for the tasks outlined below. If they choose to proceed with the repair attempt, then perform the following steps:
1.) Enter "cat /etc/fstab" in the "Command" field and press "OK" to execute. Verify that the fstab file is complete.
2.) Enter "cp /etc/fstab /etc/fstab.bak" in the "Command" field and execute it. This will copy the fstab file over to fstab.bak in the /etc directory.
3.) Enter "rm /etc/fstab" in the "Command" field and execute it. This will delete the fstab file from the Snap Server--remember, there is another one saved in fstab.bak for later use in these tasks.
3.) Reboot the Snap Server.
4.) After the reboot, see if the Home page of the Server can be accessed and enable SSH.
5.) Have customer run Putty.exe from their workstation and try to access the Snap Server through a SSH session. This will access the Linux part of the GuardianOS.
6.) Have customer log in as "admin" on the SSH session and then su over to "root user" on the SSH session. This will be indicated by a hashmark ("#") for the prompt.
7.) Enter "xfs_repair /dev/volgr(v)/lvol(n)"--wh
ere (v) is the number of the problem volume group and (n) is the number of the problem logical volume--at the prompt and execute. This command will go through 7 phases until it is complete.
8.) Have customer the enter "cp /etc/fstab.bak /etc/fstab" and execute it. This will put the fstab file back in its original place.
9.) Close Putty.exe.
10.) Reboot the Snap Server from the Web Interface.
11.) Check and see if the volume is mounted after the reboot and see if customer can access data.
The volume continues to not mount?