Debian 11 Swap Not Activating at Boot

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

System runs without swap, increasing OOM risk under burst memory workloads.

Environment & Reproduction

Common after disk cloning, UUID changes, or manual swap file recreation without fstab updates.

Root Cause Analysis

Boot-time swapon fails due to invalid UUID/path or permission issues on swap file.

Quick Triage

Check swapon –show and free -m to confirm swap absence and immediate memory headroom.

Step-by-Step Diagnosis

Inspect /etc/fstab entries, run blkid for UUID comparison, and review systemd mount logs for swap activation errors.

Solution – Primary Fix

Correct fstab to valid UUID or swapfile path, set required permissions, and activate with swapon -a.

Solution – Alternative Approaches

Resize or recreate swapfile with mkswap when partition-based swap is unavailable.

Verification & Acceptance Criteria

Swap is active after reboot and memory pressure tests no longer trigger premature OOM events.

Rollback Plan

Restore old fstab and disable problematic swap entry if boot process degrades.

Prevention & Hardening

Automate post-clone UUID audits and include swap verification in baseline host validation.

Related Errors & Cross-Refs

Logs may include “Failed to activate swap” and missing UUID device references.

Related tutorial: View the step-by-step tutorial for debian-11.

View all debian-11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Consult Debian swap management documentation and Linux memory tuning references.