How to reboot a system not started with systemd

To reboot a system not started with systemd, you must use the initialization tools native to that specific init system. For systems using SysVinit, the shutdown or reboot commands are standard. If the system is unresponsive or lacks these utilities, invoking GRUB directly allows for a hard reset. Understanding your boot loader and init daemon is crucial before attempting any restart procedures to avoid data corruption.

Identifying Your Init System

Before executing any reboot commands, it is vital to confirm which initialization system manages your running kernel. Modern Linux distributions typically use systemd, but legacy systems, embedded devices, or minimal installations may rely on sysvinit, openrc, or other alternatives. You can verify this by checking the process ID 1. Run the following command in your terminal:

ps -p 1 -o comm=

If the output is systemd, the instructions below do not apply, as systemd has its own distinct shutdown mechanisms. If the output is init, sysvinit, or similar, you are dealing with a non-systemd environment. This distinction is critical because sending signals intended for systemd (like systemctl reboot) will fail or behave unpredictably on older init systems.

Rebooting via SysVinit Commands

For systems booted with traditional SysVinit, the standard way to initiate a clean reboot is through the shutdown command. This command ensures that services are stopped in the correct order, preventing file system corruption. The most common usage involves specifying the time and action. To reboot immediately, you can use:

sudo shutdown -r now

The -r flag tells the system to reboot after shutting down, and now specifies immediate execution. Alternatively, if your system provides a dedicated reboot binary in your PATH, you can simply run:

sudo reboot

Both methods trigger the standard runlevel changes defined in your /etc/inittab or equivalent configuration files. They ensure that scripts in /etc/rc.d/ or /etc/init.d/ are executed properly. This is the preferred method for maintaining system integrity.

Using GRUB to Reboot

In some scenarios, the userland may be partially broken, or the init system may be frozen. In such cases, you can bypass the operating system's software entirely and use the GRUB boot loader to restart the machine. This is particularly useful if you have physical access to the machine or remote console access that allows interaction with the boot menu. First, ensure that GRUB is configured to allow manual intervention. If you are already inside the OS, you cannot easily jump to GRUB without crashing the kernel. However, if the system is hanging at boot, you can interrupt the GRUB timeout. Hold Shift during startup for BIOS systems or press Esc for UEFI systems to access the GRUB menu. Once in the GRUB menu, select your default entry and press e to edit. While editing, you generally cannot "reboot" from within the menu interface directly without exiting. Instead, a more practical approach for a stuck system is to use the power button or a hardware reset if available. If you need to reboot cleanly from within a frozen environment where shutdown fails, you might try pressing Ctrl+Alt+Del. On many SysVinit systems, this key combination is mapped to trigger a reboot sequence via /etc/acpi/events/ or direct signal handling.

Ctrl + Alt + Del

This method is less graceful than shutdown -r now but often effective when the init daemon is unresponsive. It sends a signal to the init process to begin the reboot sequence defined in its configuration.

Handling Service Shutdown Orders

When rebooting non-systemd systems, the order in which services stop matters significantly. Unlike systemd, which uses dependency graphs to manage start and stop orders, SysVinit relies on symbolic links in runlevel directories. If you are experiencing issues where certain services fail to stop correctly during reboot, you should review the service dependencies. For more detailed guidance on managing the order of closing services while shutting down Linux, refer to our article on Preserve Order of Closing Services While Shutting Down Linux. Ensuring that network services stop before storage mounts are unmounted prevents data loss. Always verify your runlevel configurations if you notice inconsistent behavior during reboots.

Alternative Methods and Troubleshooting

If standard methods fail, consider checking the /etc/inittab file to see how the Ctrl+Alt+Del sequence is handled. You can also check if the magic-sysrq key is enabled. Pressing Alt+SysRq+b forces an immediate reboot without syncing disks, which is dangerous but effective in emergencies. Use this only when the system is completely locked up. Additionally, ensure that your GRUB configuration does not have a password set that blocks access to the boot menu. If you need to troubleshoot why a system fails to boot after a reboot attempt, consult resources on Keyboard not working in Windows or Fedora 37 but works in Grub to rule out input device issues that might prevent you from interacting with the boot process.

Frequently Asked Questions

What happens if I pull the power plug instead of rebooting?

Pulling the power plug bypasses all shutdown scripts, leading to a high risk of file system corruption. It also prevents databases and cached data from being flushed to disk safely. Always prefer a software-initiated reboot unless the system is permanently frozen.

Can I use systemctl on a non-systemd system?

No, systemctl is specifically designed to communicate with the systemd init daemon. On SysVinit systems, it will return an error or fail silently. You must use the native commands like shutdown or service instead.

Why does Ctrl+Alt+Del sometimes not work?

The Ctrl+Alt+Del sequence depends on the init system's configuration. In SysVinit, it is mapped via /etc/inittab. If this mapping is missing or overridden by a desktop environment, the key combination may do nothing. Check your init configuration to ensure it is enabled.

How do I force a reboot if the shell is unresponsive?

If the shell is unresponsive, you can try using the magic SysRq key. Press Alt+SysRq+b to force a reboot. This requires the kernel to have SysRq support enabled, which is standard on most distributions. It bypasses the userland entirely.

Is it safe to edit GRUB entries to reboot?

Editing GRUB entries is primarily for boot parameters, not for triggering a reboot from within the OS. You cannot execute a reboot command from the GRUB editor interface. To reboot, you must exit GRUB and let the system continue booting, or use hardware buttons.