I just ran into this issue with Bento Box's 64-bit image for 16.04. We were trying to boot into recovery mode in order to run `zerofree` prior to packaging up a custom box for internal use (per steps from https://snippets.khromov.se/shrinking-a-virtualbox-linux-image-with- zerofree/).
I can confirm this is a systemd-specific issue. We booted normally, followed instructions under "Permanent switch back to upstart" in https://wiki.ubuntu.com/SystemdForUpstartUsers, and rebooted, which successfully removed systemd. We then booted into Recovery Mode and had no interruptions or strange boot behavior (though there was an error about not being able to start "User Service" on the boot after installing Upstart). Prior to removing systemd, the behavior @b-candler described is exactly what we were seeing -- after about 1 to 2 mins, it seems like systemd gets impatient and starts booting the system normally, bringing up networking, etc, AND THEN starts the recovery menu and recovery shell on top of an existing session. After another few minutes, you actually get a third one on top of that. If you can actually brave the storm and get to a prompt, running `init 1` will cause a system hang. Looks like Ubuntu is not alone here: - https://www.reddit.com/r/linuxquestions/comments/5dug3e/linux_mint_recovery_mode_crashingtiming_out/ - https://forums.linuxmint.com/viewtopic.php?t=232329 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609475 Title: Recovery mode won't allow recovery after manually installing the OS incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1609475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
