Timeline for Disable maintenance mode from within recovery (Debian)
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2020 at 6:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 19, 2020 at 18:57 | answer | added | Kaviarasu G | timeline score: 0 | |
| Jun 29, 2020 at 23:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 28, 2020 at 14:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 31, 2019 at 5:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 23, 2017 at 12:17 | answer | added | Daniel W. | timeline score: 1 | |
| Jun 23, 2017 at 9:53 | comment | added | Daniel W. |
@GeraldSchneider When I do this, it sais Running in chroot, ignoring request.
|
|
| Jun 23, 2017 at 9:39 | comment | added | Gerald Schneider | Yes, as I said, it should work from within chroot. | |
| Jun 23, 2017 at 9:37 | comment | added | Daniel W. |
@GeraldSchneider the command is useless when I can only boot from the rescue cd. Or maybe chroot then systemctl ?
|
|
| Jun 23, 2017 at 9:21 | comment | added | Gerald Schneider |
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.
|
|
| Jun 23, 2017 at 9:14 | answer | added | P0pR0cK5 | timeline score: -1 | |
| Jun 23, 2017 at 8:41 | comment | added | Daniel W. | @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-- | |
| Jun 23, 2017 at 8:40 | history | edited | Daniel W. | CC BY-SA 3.0 |
added 146 characters in body
|
| Jun 23, 2017 at 7:42 | comment | added | Daniel W. |
No success yet. Is there a file where I can set boot_in_emergecy_mode=false or something?
|
|
| Jun 23, 2017 at 3:14 | comment | added | Pablo |
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.
|
|
| Jun 22, 2017 at 19:31 | comment | added | Tollef Fog Heen | 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? | |
| Jun 22, 2017 at 18:15 | history | asked | Daniel W. | CC BY-SA 3.0 |