CentOS Stream 9 – Common Problem 125 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Kickstart install hangs at ‘Starting installer, one moment…’ with no network.

Environment & Reproduction

network –device line uses an interface name not present on hardware.

Root Cause Analysis

Stream 9 uses predictable names (enp1s0) that differ from VM templates.

Quick Triage

Inspect /tmp/anaconda.log and /tmp/syslog on the install console.

Step-by-Step Diagnosis

Check ip link inside the installer shell (Ctrl+Alt+F2).

Solution – Primary Fix

Use ‘network –device=link –bootproto=dhcp’ or match by MAC in Kickstart.

Solution – Alternative Approaches

Pass ip=dhcp on the kernel cmdline as a one-shot override.

Verification & Acceptance Criteria

Installer reaches package download phase and progress bar advances.

Rollback Plan

Boot the previous image and re-run the original Kickstart.

Prevention & Hardening

Template-test Kickstarts against each hardware profile.

Related Errors & Cross-Refs

Related: dracut network args and PXE boot DHCP options.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Anaconda Kickstart docs and Red Hat install guide.