Fix EC2 NVMe Mount Issues After Reboot Using UUIDs (AWS EBS Guide)
Fix EC2 NVMe Mount Mismatch After Reboot — The UUID Way When working with multiple EBS volumes on an EC2 instance—especially NVMe-backed ones—you might notice that after a reboot, your mount points suddenly don't match the volumes you expected. This guide explains the root cause, shows how to fix it using UUIDs, and shares some patterns and pro tips around volume device names. The Problem After rebooting, your mount points might look correct on the surface but are actually pointing to the wrong disks. Before reboot: /dev/nvme1n1 → 300G → /opt/puppetlabs /dev/nvme2n1 → 50G → /var/log/puppetlabs /dev/nvme3n1 → 30G → /etc/puppetlabs After reboot: /dev/nvme1n1 → 30G → /opt/puppetlabs ❌ /dev/nvme2n1 → 50G → /var/log/puppetlabs ✅ /dev/nvme3n1 → 300G → /etc/puppetlabs ❌ This can cause services to fail or logs to be written in the wrong location. Root Cause: NVMe Device Name Reordering Device names like /dev/nvme1n1 are assigned dynamically by the Linux kern...