we were planning on updating php and wanted to create a snapshot of the droplet first as a backup. We powered off the droploet via ssh, created the snapshot, turned it back on (via DO account) and we now can’t access the server anymore (http, ftp, ssh). Everything gives a “timeout error”.
We contacted DO support and they said: “This issue is related to the grub configuration being invalid on the Droplet when being picked up by the grub loader kernel the Droplet is currently set to.”.
They then suggested the following: “The best solution where feasible is to re-deploy with a modern image and update any snapshots based on these. (…) if this still fails to boot, we will need to use the recovery environment to verify the situation on the Disk and see if we can work from there.”
This is pretty much all gibberish to us as our only plan for today was to create a backup and update php, but we’re now in a situation where we’re dealing with >4hrs of downtime and have a growing number of frustrated paying subscribers not being able to access our websites.
So our questions is - what exactly do we do to resolve this? Any help is appreciated! Thanks in advance.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $100 of credit to try our products over 60 days!