Shared Server 120
-
Saturday, 4th October, 2014
-
06:56am
Sunday 19 October 2014
Unfortunately this server has failed again with a read only array after having 2 weeks of continuous uptime following the previous issues. We are currenty going to reject this brand new server in our data centre as being faulty and at present we are in the process of restoring the data to our spare hardware.
Please refresh for more information.
6.00am: New Server being configured ready for the backups being copied over.
6.32am: The old server is back on line and working
7.00pm: We are still proceeding with the restore to the spare server and 35GB data is copied over so far
Saturday 4 October 2014
Server 120 has been showing some hardware issues which are most regrettable on a server that is less than a month old. Please keep an eye here for updates and we are sorry for this outage.
4.00am - Data Centre asked to check the server as it would not come back on line after reboot
4.08am - Data Centre replied telling us they were passing the ticket to the noc team
4.21am - Data Centre replied asking us if we wished for a KVM to be attached
4.37am - KVM attached to the server
4.57am - Machine diagnoed as being read only and booted into recovery mode
5.47am - Error with drives not showing in Debian Live rescue environment resolved
6.00am - Manual file system check started.
7.29am - Server back on line
8.38am - System read only again and another file system check being performed
9.04am - Server back up again and we are urgently looking into this
9.54am - Server has failed again and is not booting back up.
9.57am - We are asking the data centre to replace the RAM
9.57am - As a precaution we are prepping our spare server and starting a precautionary restore from backup
10.03am - Server up after another fsck. We are still doing a precautionary restore to save time later if needed
10.03am - RAM shows segmentation faults, ext3 aborts and general unexpected behavior - we have asked for emergency replacement
10.11am - A spare server is ready and we are starting restores as a precaution to save time later if this issue persists
11.25am - Server is down for an emergency RAM swap
11.35am - Server is back up and we are monitoring.
12.35pm - Server has remained stable since the RAM replacement
4.20pm - Server has remained stable since the RAM replacement
7.00pm - Server has remained stable since the RAM replacement
9.25pm - Server has remained stable since the RAM replacement
Sunday 5 October 2014
8.35am - Server has remained stable since the RAM replacement
