Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why does fresh Debian 10 image fail apt update Question Question
Why is the DNS in the Debian 10 image broken after a brand new rebuild? Question Question

Question

Debian 10 is slow to boot, or won't boot at all

Posted November 16, 2019 3.7k views
Debian 10

I chose a Debian 10 droplet, installed some packages, added a firewall, and updated the packages on the system. Now when I reboot, I’ve waited 25 minutes, and it still is stuck in the boot process.

I booted from a recovery USB, and uninstalled the firewall in case that was interfering with configuration of the droplet during the boot process, but that didn’t help.

I tested out a Debian 9 droplet and didn’t run into this issue. A new and upgraded Debian 10 droplet took a while to boot the first and second time, but now takes about a minute to reboot. Note that SSH is unavailable until a message about the crng prints to the screen, even though all SSH keys should be generated by now.

I’d rather not restart from scratch on a Debian 10 image, because I’ve already configured this one quite a bit. Is there any way I can save this image?

Thanks

Add a comment
sudoman
By:
sudoman

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
Why does fresh Debian 10 image fail apt update Question Question
Why is the DNS in the Debian 10 image broken after a brand new rebuild? Question Question

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.

×
Submit an Answer
1 answer
ServerEnthusiast November 18, 2019

Hi @sudoman, I would recommend opening your console and checking the boot process. It is probably getting stuck somewhere due to a service or something else. This should give you more information on what exactly is going on.

Reply Report
  • sudoman November 19, 2019

    Thanks for your help. I didn’t see anything on the boot screen that was concerning, so there may have been no output for this, or it was off the screen. Unfortunately, when I booted into a recovery image, there were no recent boot logs in the file system.

    I decided to move on from that system, but I still have a snapshot if it’s needed for debugging in the future.

    Reply Report

Related

Looking for something else?

Ask a new question Search for more help