Troubleshooting guide
How to fix the problem
"grub rescue" means that GRUB could not access the required boot files or partition. This can happen after a disk move, partition change, or disk failure. First, check if the drive is visible at all.
Possible solutions
Choose the method that matches your situation. Start with the simplest suitable option and check the result. If the problem is fixed, you do not need to continue with the other methods.
Checking disk and boot order
Determine if the bootloader is trying to load the correct drive.
Steps to follow
- Turn off and disconnect any unnecessary USB devices that should not be loading the system.
- BIOS check that the system disk is visible and that the correct boot order is selected.
- Make a note of recently moved, shrunk, or deleted partitions. Don't change UEFI to Legacy just by guessing.
- If the drive is missing or making unusual noises, stop the bootloader commands and check the hardware.
Data backup and charger repair
Use the official recovery environment of the distribution.
Steps to follow
- Run the official test media of the same distribution in the same UEFI or Legacy mode that the system was installed with.
- Just scan the partitions with Disk Utility and copy the accessible important files first.
- Set the actual system and EFI partitions, if available, according to the official GRUB recovery instructions. /dev/sda from a foreign sample does not necessarily match your drive.
- If the purpose of partitions is unclear, stop and transfer their scheme to a specialist. Formatting the EFI or data partition is not a necessary initial fix.
If the problem persists
If BIOS does not see the drive or it shows read errors, try to resolve the drive and data issue first. If the data is healthy, the GRUB recovery should match the distro, UEFI / Legacy mode and real partitions; there is no universal safe copy-paste set.
Request a repair