RHEL 7 swap not activated at boot due to incorrect UUID in fstab

📖 ~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

Systems under memory pressure begin aggressive OOM behavior because swap is unavailable. Background services are killed and performance degrades sharply during peak workload periods.

Environment & Reproduction

Common after disk cloning, partition recreation, or VM template drift where swap UUID changes but fstab is not updated. Reproduce by setting stale UUID in fstab and rebooting.

Root Cause Analysis

Boot sequence cannot locate swap device referenced in fstab, so swapon fails silently or logs warnings. Memory pressure later exposes the missing swap configuration.

Quick Triage

Check swapon –show, free -m, and blkid output. Inspect journalctl -b for fstab and mount warnings. Confirm no conflicting LVM swap configuration is present.

Step-by-Step Diagnosis

Map expected swap device to current UUID, validate fstab syntax, and test swapon manually. Determine whether partition, LV, or encrypted swap path changed during maintenance.

Solution – Primary Fix

Update /etc/fstab with correct UUID, run swapon -a, verify active swap, and reboot for confirmation. Ensure related monitoring services restart cleanly through systemctl where needed.

Solution – Alternative Approaches

Create new swapfile/LV if missing, tune vm.swappiness for workload profile, or migrate memory-heavy jobs while resizing host memory and swap strategy.

Verification & Acceptance Criteria

swapon must list expected device after reboot, memory pressure tests should avoid premature OOM, and journalctl should show no swap activation errors.

Rollback Plan

Revert fstab changes if boot issues occur and temporarily disable broken swap entry with nofail while preparing corrected configuration under change control.

Prevention & Hardening

Automate fstab validation, include swap checks in post-clone workflows, and alert on missing swap state. Keep SELinux labels and permissions consistent for swapfile implementations.

Related Errors & Cross-Refs

Related incidents include random OOM kills after reboot and slow recovery from memory spikes. Cross-reference kernel tuning, cgroup limits, and service restart policies.

Related tutorial: View the step-by-step tutorial for rhel-7.

View all rhel-7 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Review fstab, swapon, and Red Hat memory tuning documentation. Capture standard swap remediation procedures in platform runbooks.