Access lost in Rescue mode. Can multi-User mode be restored without rebooting?
Environment
- Red Hat Enterprise Linux
Issue
- When executing systemctl rescue, the user is unable to access any services or interfaces. A full system reboot is required to regain system access.
Resolution
-
This behavior of not being able to access any services or interfaces is expected when switching to rescue.target.
-
To regain access without rebooting, On the console or terminal access, manually switch to the normal operating state:
# systemctl isolate multi-user.target -
This brings the system back to a multi-user state with networking and full CLI access.
Root Cause
-
The systemctl rescue command transitions the system into the rescue target, which is designed for minimal, single-user mode operations. This is by design and not a malfunction.
-
In this mode:
- Network services are not started.
- Only the root filesystem is mounted.
- A root shell is provided.
- GUI and most system services are not available.
-
Systemd Target Hierarchy Overview:
+------------------+ | poweroff.target | (System shutdown) +------------------+ ^ +------------------+ | reboot.target | (System reboot) +------------------+ ^ +------------------+ | graphical.target | (Full desktop GUI) +------------------+ ^ +------------------+ | multi-user.target| (Networking + Multi-user CLI) +------------------+ ^ +------------------+ | rescue.target | (Single-user recovery shell) +------------------+ ^ +------------------+ | emergency.target | (Minimal shell, root FS only) +------------------+ -
Rescue mode is intended for administrative recovery, not regular operation. It's best used for troubleshooting or repairing broken configurations in isolation.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments