Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757072 If you have a problem in your configuration (like a broken fstab entry) which triggers emergency.service and you try to boot the "rescue" mode via the kernel command line, you get two conflicting rescue shells: Welcome to rescue mode! Type "systemctl default" or ^D to enter default mode. Welcome to emergency mode! After logging in, type "journalctl -xd" to view Type "journalctl -xb" to view system logs. Type "systemctl reboot" to reboot. system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance Give root password for maintenance (or type Control-D to continue): (or type Control-D o continue): Both rescue and emergency mode seem to fight over stdin and one is constantly kicked out of the rescue shell.
To reproduce the issue, add something like /dev/nonexistent /mnt/foo auto auto 0 0 to your fstab Then choose the rescue mode in grub (which adds single to the kernel command line).
I've reproduced that with v215 and v208. Should we make emergency.service and rescue.service conflict with each other?
(In reply to comment #2) > Should we make emergency.service and rescue.service conflict with each other? http://cgit.freedesktop.org/systemd/systemd/commit/?id=87502e5868 does that.
Hi, FYI, I just raise the same bug today with debian Stretch. systemd --version return : systemd 232 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.