this post was submitted on 23 May 2023
28 points (100.0% liked)
Beehaw Support
2796 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I can add what the Digital Ocean support team told me. Namely, the server suffered from some type of "kernel panic" that is very rare. The Digital Ocean support team do not have access to our back-end user interface nor can they access our server otherwise.
They guided me, step by step, through several attempts to restore the server from this "kernel panic". We made eight different attempts which all failed and we don't know what caused this issue in the first place.
Luckily, we have server backups enabled and this was the last resort.
A kernel panic may prevent a VM from booting but shouldn't prevent accessing the disk image for recovery purpose.
Maybe the kernel panic corrupted the disk image, or maybe Digital Ocean doesn't have a recovery mechanism that work when the VM doesn't boot.
More than likely, this is what happened.
Was the filesystem corrupted?
More than likely.