I just installed quite a lot of 12.10 updates, was prompted to reboot, and then found that I couldn't boot.
Use Boot Repair to fix your bootloader.
- Boot Ubuntu from a LiveCD or Live USB
- Connect to the internet
Open a terminal, and add the Boot Repair PPA
sudo add-apt-repository ppa:yannubuntu/boot-repair && sudo apt-get update
Install Boot Repair
sudo apt-get install -y boot-repair && boot-repair
Launch and use, see https://help.ubuntu.com/community/Boot-Repair#Using_Boot-Repair for more details
lsto get a list of partitions
set prefix=(hd0,msdos6)/boot/grub[you will almost certainly have to enter a different drive/partition in the brackets, you may just have to try all of those listed by
lsuntil you find the one that works.
normaland you will get your boot prompt back!
See also: The helpful place where I found this. I doubt this will work for everyone encountering this error, but I've put it here in the hope it helps someone.
Once you've loaded Ubuntu, run
sudo grub-install /dev/sda and
sudo update-grub as soon as possible. This means you won't have to do that tedious process above every time you boot your machine.
I had the exact same issue -
normal.mod not found,
ls of the boot partition would produce a blank line. After a week of troubleshooting to get the system to boot properly here are the steps I went through.
Got a copy of SuperGrub and created a boot cd. I could now get logged back on to my system. Got a copy of BootRepair and had not luck getting the system to boot directly from the hard disk and had to keep using the CD. BootRepair did act a little strange since the Grub location and Grub options were grayed out. It did report a successful install.
Hard drive was originally set up:
sda1 ext4 root with boot
sda2 linux swap
sda3 ext4 used as a spare drive(holds VMs for Virtual box).
Used a copy of Ubuntu 10.10 live cd. Ran gparted to shrink the
sda1partition and created
sda4ext4 boot partition at the front of the drive and set mount point to
/bootafter deleting the boot directory from
/. BootRepair now has options available. Installed on boot partition and can now boot from hard drive.
Being curious I decided to investigate further. The boot repair log had a peculiar entry for my
sda1ext4 partition, it was reported as
DOSand had a short 8 character UUID instead of the UUID reported by blkid.
grub-probereported the file system as vfat.
After many other trials I cleared the first 440 bytes of
Grub-probenow reports file system as ext2. Ran
update-gruband the correct UUID for the
The issue seems to be two-fold:
1. It seem to affect installations where the partition record has references to msdos.
grub-probe does not try to resolve mismatch issues between fs type and contents in the partition record.
Another thing to check is the boot order in your BIOS. I apparently had installed grub installed on all my disks (perhaps after following 8128's answer), but this broke when updating my Linux distro (Debian). Changing the first boot disk as my Linux OS fixed it.
I ran across this error upgrading to Kubuntu 13.10. I had a memory stick plugged into the USB port during the dist-upgrade. After rebooting I went straight to Grub Rescue. Unplugging the USB drive and rebooting fixed the problem.
In my case, I had downgraded to GRUBv1 and after the upgrade to 12.10 grub2 couldn't find his files (*.mod, etc...), although the grub.cfg was there.
I found a more comprehensive manual on grub rescue: https://help.ubuntu.com/community/Grub2/Troubleshooting#grub_rescue.3E-1
See also the command list at the begining of the page. Thx flute flute.
protected by Community♦ Dec 18 '18 at 8:32
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?