Troubleshooting·LPIC-2
Boot order, and what actually delayed it
Topic 202 is system startup, and its most useful skill is reading a boot the way systemd measures it. This guide separates the phases, shows why the slowest service is usually not the reason a machine was slow to start, and finishes with the one-line health check worth running on every machine you inherit.
201: System Startup Guide 11 of 29 Intermediate
- OSUbuntu 26.04 LTS
- Kernel7.0.0-30-generic
- systemd259
- Block devicesone 50 GB disk
- TimeAbout 17 min
| Server Name | IP Address | OS | Roles | CPU | RAM | HDD |
|---|---|---|---|---|---|---|
| LPIC2-A01 | 192.168.0.78 | Ubuntu 26.04 LTS | Primary service host - BIND, Apache, Samba, Postfix. Topic 204 RAID runs on loop devices; this machine has no spare disk | 2 Core | 4 GB | 50 GB |
This guide includes
Use this for the system startup topic. This matters because blame and critical-chain answer different questions - the slowest unit is often not the one that delayed the boot.
- reading the three phases, and the chain that actually caused the wait
- seeing that targets are sets rather than modes, with several active at once
- running the one-line health check, for this boot only
Before you start
- load-memory-and-what-the-numbers-mean
-
Three phases, and the chain that caused the wait
-
Targets are sets, not modes
-
The one-line health check