Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support, Network & Infrastructure Services Let’s talk

ปุ่มแปลไทยจะเปิดบทความผ่าน Google Translate เพื่อแปลอัตโนมัติ โดยคงโค้ดและคำสั่งไว้ตามต้นฉบับ

Linux Server / Boot, systemd & Service Recovery

Investigate slow Linux boot using systemd timing context

A long boot can reflect a blocking mount, device wait or service initialization. Inspect the critical chain before disabling services.

Compiled for Sorlavit Kim · Published · Updated · 1 min read

Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.

Start with this check

Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.

systemd-analyze critical-chain

Read the result

The command shows a time-critical activation chain for the current boot. It does not attribute every delay or measure all parallel work exactly.

Resolve and verify

Compare timestamps with the relevant unit journals and device or network waits. Repair the demonstrated dependency and measure a later planned boot under comparable conditions.

Before changing production

Do not disable storage, security or recovery services merely because their activation time looks large.

Source & further reading

systemd manual — systemd-analyze

Independently written summary reviewed on 2026-11-01. The example illustrates a possible application; it is not a client case study.

Share this article

Back to results