CentOS Stream 10 – Common Problem 242 – 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

Boot fails after kernel rebuild because the initramfs lacks required storage or NIC drivers.

Environment & Reproduction

Happens when dracut auto-detection misses controllers used for boot or PXE provisioning.

Root Cause Analysis

Default hostonly mode excludes drivers not visible at build time, leading to early-boot panics.

Quick Triage

Boot fallback kernel, mount /boot, and audit lsinitrd output for missing modules.

Step-by-Step Diagnosis

Run: lsinitrd /boot/initramfs-$(uname -r).img | grep -E ‘megaraid|nvme|mlx5’.

Solution – Primary Fix

Add force-drivers in /etc/dracut.conf.d/00-storage.conf and run sudo dracut -f –regenerate-all.

Solution – Alternative Approaches

Disable hostonly mode globally via hostonly=no for image builds destined for diverse hardware.

Verification & Acceptance Criteria

initramfs contains the required drivers and the new kernel boots without panic.

Rollback Plan

Reboot using the previous kernel and remove the new initramfs file to roll back.

Prevention & Hardening

Document required drivers per platform and add dracut verification to build pipelines.

Related Errors & Cross-Refs

Related to multipath, FCoE, and PXE driver omissions.

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

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

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

dracut(8) and dracut.conf(5).