Q: How do you persistently mount a new EBS/block volume so it survives reboots?
First, I verify the block device name (lsblk), format it (mkfs.ext4 /dev/nvmeXn1), and mount it temporarily to verify (mount /dev/nvmeXn1...
#Linux #Linux / SRE — Scenario-Based Interview Questions #L1 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""Never reboot a server blindly; always capture top process telemetry, lsof descriptors, and thread dumps first. The interviewer is testing: `/etc/fstab` configuration, UUIDs vs device names.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Initial Diagnostics & Root Cause Analysis
First, I verify the block device name (lsblk), format it (mkfs.ext4 /dev/nvmeXn1), and mount it temporarily to verify (mount /dev/nvmeXn1 /data).
- Find the UUID:
blkid /dev/nvmeXn1 - Add an entry to
/etc/fstab: - Test the entry without rebooting:
umount /datathenmount -a. If no errors are thrown, the system will safely mount it on the next boot. (Thenofailoption ensures the server still boots if the volume is detached).
2️⃣
Remediation & Permanent Safeguards
To make it persistent: I should never use the device name (like /dev/nvmeXn1) in /etc/fstab because cloud providers do not guarantee device name ordering across reboots. Instead, I use the UUID. UUID=123-abc-456 /data ext4 defaults,nofail 0 2
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Find the UUID: blkid /dev/nvmeXn1."
⚡ 60-Second Elevator Pitch Talking Points
- Find the UUID: blkid /dev/nvmeXn1
- Add an entry to /etc/fstab:
- Test the entry without rebooting: umount /data then mount -a. If no errors are thrown, the system...
Advertisement