Lost access to sites/servers and known good backups won't boot...

I am unable to access some of my servers/sites. When I restore from a known good backup to the existing droplet or new droplets, I see the same error/warning:

DIGITALOCEAN Droplet Recovery System [17.10.1 (Artful Albacore)]

This system was placed into recovery mode by DigitalOcean support or because the droplet cannot boot due a missing kernel.

  • Network access and SSH have been enabled automatically *
  • SSH Host keys will NOT match while using this rescue system *

Root Password has been randomly set to: 7459-bc92-d2c4-1056 You are strongly encouraged to use SSH keys.

Select One of the options below:

  1. Check Filesystem
  2. Reset Droplet Root Password
  3. Configure Keyboard
  4. Attempt to ‘chroot’ into installed system
  5. Interactive Shell [/bin/bash]
  6. Install a DigitalOcean provided Ubuntu 16.04 LTS kernel
  7. Install/update kernel on disk

Choose (1-7) and press Enter to continue.

I attempted to restore several times using snapshots that have previously worked.

The IP refuses an SSH connection so I used the console and observed a red “fail” message briefly displayed on the screen followed by the message posted above.

I tried the following options with no success at restoring normal use and access.

  1. Check Filesystem - passes
  2. I am able to chroot into the system and see no issues.
  3. Install a DigitalOcean provided Ubuntu 16.04 LTS kernel does not solve it
  4. Updating the Kernel does not work.

Why am I unable to use my legacy servers as they were configured?

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

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.

I’m getting the same problem and I found the solution!

Short Answer:

  1. Go to your Dashboard and Power Off your droplet.
  2. Go to Kernel tab and change your kernel to use: DigitalOcean GrubLoader v0.2
  3. Go to Access tab and click Launch Console
  4. You should see the console screen with some options to choose (hit Enter key if you don’t see any)
  5. Choose the interactive bash command option
  6. Type “reboot” and wait, don’t close the window
  7. You’ll be prompted to select from 3 options. Choose option #2 (boot kernel from GrubLoader)
  8. Done

Your droplet should start correctly again (at least in my case)

Long Answer:

My droplet went down and unable to boot (always in recovery mode) after the NYC1 Hypervisor Reboots maintenance completed by DO:

Looking further into their post:

The most important information: * If your distribution is not included in the list of patched versions below, we highly recommend you move your data to a new Droplet running a version that is receiving security updates. To simplify the act of patching, we have recently updated Droplets to utilize a GrubLoader, which allows Droplets that use our in-control panel legacy system to boot into internally installed kernels. On certain legacy Droplets, this may cause issues if the kernel is not upgraded.*

My short answer above is based on the above information from DO.

Hello, I am facing same problrm now, but the secound step “2) Go to Kernel tab and change your kernel to use: DigitalOcean GrubLoader v0.2” there is no options. only “The kernel for this Droplet is not managed within the control panel. Instead, you can upgrade the kernel from within the Droplet.” what i have to do ?

May I know the end result and whether you use or are happy with the service and whether this has happened again in the lat six months? I am considering DO but all these posts are scaring me to other options. Would like some honest responses.