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

/var remounted read-only after host crash on CentOS Stream 10.

Environment & Reproduction

Hosts using XFS root or data volumes without UPS protection.

cat /etc/os-release
uname -r
rpm -qa | grep 

Root Cause Analysis

Log corruption forced XFS to remount ro to protect data.

Quick Triage

Confirm package, network, SELinux and firewall state.

dmesg | tail -n 60
mount | grep xfs
xfs_info /var

Step-by-Step Diagnosis

Drill into storage/xfs-repair state and recent journal entries to isolate the failure.

journalctl -k -b -1 -n 200
xfs_db -r /dev/mapper/vg0-var

Solution – Primary Fix

Apply the standard remediation for storage/xfs-repair on CentOS Stream 10.

sudo umount /var
sudo xfs_repair /dev/mapper/vg0-var
sudo mount /var

Solution – Alternative Approaches

Boot from rescue image and use xfs_repair -L if log is unrecoverable.

Verification & Acceptance Criteria

Validate the fix with positive functional checks before closing.

mount | grep /var
ls /var

Rollback Plan

Revert to the previous known-good configuration if the fix regresses.

Restore from latest snapshot or backup.

Prevention & Hardening

Codify the fix in configuration management and add monitoring.

Snapshot before xfs_repair runs; monitor SMART data.

Related Errors & Cross-Refs

EXT4 vs XFS recovery comparisons.

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

xfs_repair(8) and Red Hat storage admin guide.