Notification Type
Emergency Maintenance
Service Affecting
Yes
Message
Summary: This machine is down, an engineer is looking into what the issue is.VPS affected:
78.153.208.024
78.153.208.183
78.153.209.035
78.153.209.104
78.153.209.186
78.153.209.221
78.153.210.019
78.153.210.059
78.153.210.102
78.153.208.061
78.153.210.208
78.153.210.131
78.153.211.022
78.153.209.236
78.153.208.055
78.153.211.045
78.153.211.050
78.153.209.220
78.153.208.253
78.153.211.176
78.153.209.171
78.153.211.036
78.153.208.227
78.153.209.101
78.153.210.013
78.153.210.252
78.153.211.026
78.153.211.058
78.153.211.124
78.153.211.129
Update: 08:50: It looks like a drive failure caused the raid array to go offline on this host. The machine is backup now and we'll replace the drive today.
All the VPS are booting now, quite a number are already back online.
Update: 09:30: There are 9 VMs left to boot right now. Their VEIDs are:
2279
2258
2254
3073
2484
3062
2877
2221
2311
The reason for this is that a quota check / fsck equivalent is required to boot the VMs after the node went offline.
Update: 10:25: There are 2 containers still running disk checks, they are:
2484
2877
We believe they should be back at the latest 11am.
Update 11:45 All containers have now started.
Leave a comment