Shared Server 26 Reboot
-
Monday, 5th June, 2017
-
17:27pm
8.40pm
The server is back on line. We're deeply sorry that what should have been a 30 minute reboot and forced file system check (as the server had 500 days uptime) turned into a prolonged outage. We'll be monitoring the server for the next few hours intensely.
8.20pm
The server is booting now. We're just waiting for our admins to take the server out of recovery mode (where there is no external networking). We're extremely sorry for the delay here. Once the server is back on line we'll update this announcement.
8.00pm
This is slow going unfortunately. We're going to have to do another hard reboot here. We're working on this server with top priority.
7.30pm
We've got our recovery session working and our senior admin is working on this now. We'll have some information shortly.
6.30pm
We're just converting our KVM session to a recovery session so we can attempt to fix the grub issue that is causing the server to fail to boot. We're working on this with priority.
6.05pm
We're connected to the server now via a KVM unit and we see the server is 'stuck' at the boot screen. Our admins are working on this now. We'll have an update in 20 minutes.
5.30pm
We're aware that Shared Server 26 is currently down. About 15 minutes ago the server became unresponsive and we had to reboot the server. The server has had 18 months continuous uptime so the file system will be performing a file system check right now. This is a standard linux check and it will take a little time to complete. We're currently getting our admins in the data centre to connect a Console to the server so we can see what is going on and we'll update you as soon as possible. We estimate the console unit will be connected to the server in about 20 minutes time. Next update after the KVM Console is connected and we have logged into the server.
