GRUB Rescue After Disk UUID Change

📖 ~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 drops to `grub rescue>` and cannot boot the installed operating system.

Environment & Reproduction

Ubuntu 20.04 hosts after disk cloning, partition edits, or storage migration changing UUIDs.

Root Cause Analysis

GRUB and/or `fstab` references stale UUIDs that no longer map to current root partition.

Quick Triage

Boot via recovery/live media and enumerate block device UUID mappings.

Step-by-Step Diagnosis

Compare UUID references across GRUB configs, `fstab`, and actual partition metadata.

Solution – Primary Fix

Update UUID references, chroot if needed, regenerate GRUB config, and reinstall bootloader.

Solution – Alternative Approaches

Use filesystem labels temporarily or revert storage layout to prior known-good mapping.

Verification & Acceptance Criteria

System boots without rescue prompt and mounts expected filesystems at startup.

Rollback Plan

Restore previous disk snapshot or boot configuration backup if boot chain remains unstable.

Prevention & Hardening

Include post-migration boot validation and UUID reconciliation in storage change runbooks.

Related Errors & Cross-Refs

`unknown filesystem`, `no such device`, and initramfs root mount failures.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu GRUB recovery and filesystem UUID management documentation.