6 Jun 2017
11:02 UTC
Paul Cammish
All affected Legacy VMs are now back up and working normally and have been checked that they booted successfully.
If you are still experiencing any issues, please don't hesitate to contact us via the methods at https://bytemark.co.uk/help.
6 Jun 2017
10:25 UTC
Paul Cammish
All but one Legacy VM are now back working normally, and the last one is being checked now, so we expect it to be back up shortly.
If you are still experiencing any issues, please don't hesitate to contact us via the methods at https://bytemark.co.uk/help.
6 Jun 2017
10:05 UTC
Paul Cammish
At around 9:30 this morning we were alerted to a problem with the Legacy Virtual Server host "host03.vmh", and the virtual machines on it were found to be down.
Investigation has shown that the problem was a failed disk which has now been replaced, and the server is back up now as of 10:32, and the majority of the virtual machines have started on it now.
A few VMs are still doing their filesystem checks or may need manual intervention, so we now expect this to be fully resolved by 11:30.
(Note that does not affect servers on the Cloud Server platform, other Dedicated Servers, or Legacy Virtual Machines on other hosts.)
6 Jun 2017
09:39 UTC
Paul Cammish
At around 9:30 this morning we were alerted to a problem with the Legacy Virtual Server host "host03.vmh", and the virtual machines on it were found to be down.
Investigation has shown that the problem was a failed disk which has now been replaced, and the server is back up now as of 10:32, and virtual machines are starting on it again.
Each of the virtual machines running on it will likely need to do their own disk checks, so we're expecting all of the virtual servers on this host to be back up by 11:00 at present, and will monitor each of them individually to ensure they come up fully.
We will update this post again if this estimate changes, and once all the virtual servers are back up.
(Note that does not affect servers on the Cloud Server platform, other Dedicated Servers, or Legacy Virtual Machines on other hosts.)
6 Jun 2017
08:52 UTC
Paul Cammish
At around 9:30 this morning we were alerted to a problem with the Legacy Virtual Server host "host03.vmh", and the virtual machines on it were found to be down.
Investigation has shown that the problem was a failed disk which has now been replaced, and the server is coming back up now, however it is doing a filesystem check which will take a little while longer.
Once host03.vmh to be back up, some of the virtual machines running on it will likely need to do their own disk checks, so we're expecting everything to be back up by 11:00 at the latest.
We will update this post again if this estimate changes, and once all the virtual servers are back up.
Note that does not affect servers on the Cloud Server platform, other Dedicated Servers, or Legacy Virtual Machines on other hosts.
6 Jun 2017
08:37 UTC
Paul Cammish
We've been alerted to a problem with the Legacy Virtual Server host "host03.vmh", and are currently investigating and will update this post as soon as we have any information.
This will not affect servers on the Cloud Server platform, or other Dedicated Servers.