Q: After a kernel upgrade, the server boots into the old kernel instead of the new one. How do you fix this?
The GRUB bootloader controls which kernel is loaded at boot. After a kernel upgrade, the default boot entry may still point to the old kernel.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "In an interview, I explain my systematic Linux troubleshooting methodology using Brendan Gregg's USE method. The interviewer is testing: GRUB bootloader configuration, default kernel selection.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
The GRUB bootloader controls which kernel is loaded at boot. After a kernel upgrade, the default boot entry may still point to the old kernel.
- List installed kernels:
- Set the new kernel as default:
- Regenerate GRUB config (if needed):
Remediation & Permanent Safeguards
To fix: Or by menu index: After reboot, confirm with uname -r that the new kernel is running.
grubby --default-kernel # Shows current default
awk -F\' '/menuentry/ {print $2}' /boot/grub2/grub.cfg # Lists all entries
- Verify and reboot:
- List installed kernels:
- Set the new kernel as default:
- Regenerate GRUB config (if needed):
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring kernel upgrade server SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring kernel upgrade server
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring kernel upgrade server Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring kernel upgrade server
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).