真是人生难免有今日。前天晚上手机GMAIL上收到DO的邮件:
Droplet xxx rebooted due to physical node issue
We've had to unfortunately reboot your Droplet xxx due to an issue on the underlying physical node where the Droplet runs.
We are investigating the health of the physical node to determine whether this was a single incident or systemic.
If you have any questions related to this issue, please send us a ticket. https://cloud.digitalocean.com/support
Happy coding,
DigitalOcean
还以为重启过就没事了,加上昨天有事一天都在外面就没理它,昨天晚上回来发现VPS根本无法登录,就给他们开了个票就去睡觉了。早上起来看回票,提供了两个方案:
https://www.digitalocean.com/community/articles/how-to-recover-from-file-system-corruption-using-fsck-and-a-recovery-iso
试了一下第一个方案根本不行,仍然进不了console,估计第二个方案也是浪费时间,只能重装系统了…还好大部分东西我都有做rsync备份,只是感觉很不爽,显然DO的SSD相当不靠谱。
各位使用DO的同学还是自己做好备份吧,以防万一。
Droplet xxx rebooted due to physical node issue
We've had to unfortunately reboot your Droplet xxx due to an issue on the underlying physical node where the Droplet runs.
We are investigating the health of the physical node to determine whether this was a single incident or systemic.
If you have any questions related to this issue, please send us a ticket. https://cloud.digitalocean.com/support
Happy coding,
DigitalOcean
还以为重启过就没事了,加上昨天有事一天都在外面就没理它,昨天晚上回来发现VPS根本无法登录,就给他们开了个票就去睡觉了。早上起来看回票,提供了两个方案:
https://www.digitalocean.com/community/articles/how-to-recover-from-file-system-corruption-using-fsck-and-a-recovery-iso
试了一下第一个方案根本不行,仍然进不了console,估计第二个方案也是浪费时间,只能重装系统了…还好大部分东西我都有做rsync备份,只是感觉很不爽,显然DO的SSD相当不靠谱。
各位使用DO的同学还是自己做好备份吧,以防万一。