How to Fix Slow systemd Startup on Linux

What Causes This?

Slow systemd startup on Linux usually happens when one or more services take too long to initialize during boot. Common causes include failed services waiting on timeouts, slow disk checks, network-related units hanging, or too many unnecessary startup services loading at once. In some cases, old temporary files, logs, or low disk space can also make boot-related tasks slower than they should be.

Common Symptoms

• The system sits on the boot screen longer than usual
• systemd-analyze shows a high startup time
• Specific services show long delays or timeout errors
• The desktop or login screen appears much later than expected
• Boot performance gets worse over time

How to Fix It Manually

1. Check how long boot is taking.

   • Open a terminal.
   • Run:

     systemd-analyze

   • This shows total kernel and userspace startup time.

2. Find which services are slowing startup.

   • In the same terminal, run:

     systemd-analyze blame

   • Look for services with unusually high times at the top of the list.
   • Then run:

     systemd-analyze critical-chain

   • This helps you see which units are delaying the boot sequence.

3. Check for failed services.

   • Run:

     systemctl --failed

   • If any services are listed, inspect them with:

     systemctl status service-name

   • Replace service-name with the actual unit name.
   • Read the error messages and decide whether the service should be fixed, restarted, or disabled.

4. Disable unnecessary startup services.

   • If you find services you do not need, disable them:

     sudo systemctl disable service-name

   • To stop one immediately without rebooting:

     sudo systemctl stop service-name

   • Be careful not to disable essential services like display manager, networking, or storage-related units unless you know what they do.

5. Review disk space and temporary clutter.

   • Check free space:

     df -h

   • If the root partition is nearly full, boot tasks may slow down.
   • Clean package cache and old temporary files using your distro’s package manager and safe cleanup tools.
   • You can also review large logs in:

     /var/log

6. Check the journal for boot errors.

   • Run:

     journalctl -b -p warning

   • This shows warnings from the current boot.
   • If you want to see errors only:

     journalctl -b -p err

   • Focus on repeated timeout, mount, network, or hardware-related messages.

7. Reboot and test again.

   • Restart the system:

     sudo reboot

   • After booting back in, run:

     systemd-analyze

   • Compare the new time to confirm whether startup improved.

Fix It Automatically with Kudu

If slow startup is being made worse by temporary clutter, leftover files, or a generally bloated system, Kudu can help clean it up automatically and keep the system leaner. It gives you a simpler way to reduce junk and improve overall responsiveness without digging through cleanup tasks by hand.

Download Kudu Free →