First, the log file indicates that Boot Repair has completed, but your question alludes to manually editing /boot/grub/grub.cfg
, and it's not clear if you did this before or after running Boot Repair. If after, please run Boot Repair again but do not edit /boot/grub/grub.cfg
manually.
If the system is dropping to a grub>
prompt as you describe after you run Boot Repair, then that tool is obviously not up for the job. Your Boot Repair seems reasonable, although it's not showing a grub.cfg
file on your hard disk, which it normally does. Thus, you may want to try a different approach:
- Disable Secure Boot in your firmware, if it's currently enabled.
- Download the CD-R or USB flash drive version of my rEFInd boot manager.
- Prepare a boot medium from the files you download.
- Boot the rEFInd boot medium. It should show you at least one option to boot Ubuntu.
- Try the Ubuntu option(s) in rEFInd. If one fails and there's more than one, try the other(s).
- If you can get into Ubuntu from rEFInd, you have two options:
- You can install the Debian package or PPA of rEFInd, which will then take over you boot manager duties and get you booting without GRUB.
- You can attempt to re-install and repair GRUB from your working Ubuntu installation. Given that Boot Repair has already failed at this task, I'm not sure what to suggest, except perhaps
sudo grub-install
followed by sudo update-grub
.
- If desired, you can re-enable Secure Boot at this point.
The point of this procedure is simply that rEFInd is not GRUB, and therefore whatever is going wrong with GRUB will not affect rEFInd -- at least, not if the problem is GRUB-specific. It's conceivable that there's something more wrong with your installation. For instance, if you no longer have Linux kernels in /boot
, you'll have to re-install your kernel packages using an emergency system.