Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 1
    Slightly above what's on the screen it should say something about what caused it to enter the emergency shell. Can you get a new screenshot after having the hoster press shift-pageup to scroll back? Commented Jun 22, 2017 at 19:31
  • That maintenance mode usually has to do with filesystems not found, or were unmounted improperly (which may be your case, since the server lost power suddenly). As @TollefFogHeen said, I would try to guess the error from output that came before what you are showing. Also, check if you have a chroot utility on that rescue image you are booting. For instance, Hetzner has chroot_prepare (which mounts /dev, /sys, et. al.) and chroot, which allow to "get into" your server after you mounted its root filesystem. There you can perpaps run the recommended journalctl -xb and gather info.
    – Pablo
    Commented Jun 23, 2017 at 3:14
  • No success yet. Is there a file where I can set boot_in_emergecy_mode=false or something?
    – Daniel W.
    Commented Jun 23, 2017 at 7:42
  • @TollefFogHeen They sent me a screenshot but I don't know how this error did not come up earlier or don't know how to solve it--
    – Daniel W.
    Commented Jun 23, 2017 at 8:41
  • It's right in your screenshot. Type "systemctl default" to try again to boot into default mode". Before doing this in your chroot environment you should run fdisk on your disks, check logs etc. Commented Jun 23, 2017 at 9:21