Around 7:30sm this morning we noticed some services on the server was unresponsive and decided the best action was to reboot the server.
Unfortunately due to the high uptime of the server and having not been rebooted for over a year, the system went into efsck during the booting process.
The server has a 2T RAID 10 storage space and it took longer than usual for this process to complete.
Just like your home PC, a server has many processes and will eventually require a reboot due to memory leaks and other problems.
We try out best to keep the server running as smoothly and with as little downtime as possible.
To prevent this from happening again, we will be doing planned rebooting of servers and do them at time which will cause the least disruption.
ANS Support Team
Tuesday, June 28, 2016