Tuesday 27 March 2012 - 12.33pm
The server is now booting on the old Kernel. It appears the server was set to update the kernel automatically which should not have happened. This was a slight misconfiguration which we have now corrected. This explains why the issue only came to light when a reboot was needed. The server is now back on line.
Tuesday 27 March 2012 - 12.14pm
Our technicians have discovered the issue causing the server not to reboot is a bug in the current Kernel. It looks like for some reason the Kernel was updated automatically at some point and as this was the first server reboot since this happened so the kernel is having problems loading. We are working on switching to the older kernel and will have an update soon.
Tuesday 27 March 2012 - 11.28am
We are aware of an issue and actively working on a resolution to a problem affecting Server 21. Server 21 is brand new hardware in our Maidenhead data centre and the server this morning became unresponsive.
For those technical amounst you the server reboot stalls at this stage: 'request module: runaway loop modprobe binfmt-464c'
We are actively seeking a resolution to this issue. It is most unfortunate and the worst luck this server was the one that had so many issues last month. We had hoped a move to the new data centre (the same data centre we base all our Uk servers in) would bring a permanent resolution.
Please open a support ticket by emailing support@bigwetfish.co.uk and we will be pleased to update you. Please do not be upset if replies at this time are short - we will give anyone who requests a full explanation once the issue is fully resolved.
***No other shared servers are affected as incorrectly posted earlier***
