5

I was dual booting winodws 8.1 and ubuntu 13.10. I have updated my windows BIOS. After that i am always getting into windows. GRUB menu is not displayed.

So, Using UBUNTU 12.10 live CD (But i have 13.10 in my lap), i have repaired the boot to fix this issue.

When i clicked Boot repair, it says "UEFI is detected" I have choosen the recommended repair and it ends up with some commands 

sudo chroot "/mnt/boot-sav/sda7" dpkg --configure -a
sudo chroot "/mnt/boot-sav/sda7" apt-get install -fy
sudo chroot "/mnt/boot-sav/sda7" apt-get purge -y --force-yes grub*shim-signed linux-signed*

After that, On clicking forward in the boot repair, got some error message like "GRUB is still present. Please try again"

PASTEBIN Ref: http://paste.ubuntu.com/7164372/

BIOS Settings: Secured Boot: Disabled OS Type: UEFI

Kindly help guys.

Thanks

Cyborgz
  • 229

4 Answers4

8

Not sure if this is even still an issue for you at this point but I was having the same trouble using boot-repair to purge and reinstall grub on ubuntu 14.04. So just in case someone else is having this issue here is what I did.

After I ran the last command (sudo chroot "/mnt/boot-sav/sda7" apt-get purge -y --force-yes grubshim-signed linux-signed) and attempted to click the forward button I got the message GRUB is still present. Please try again.

So I looked over the terminal output for that command and it turns out that the command was uninstalling grub*-common but was also installing grub-common:i386, which was then detected by boot-repair. So I uninstalled grub-common:i386, which then reinstalled grub-common, grub-pc etc. Rather annoying that apt-get is this stubborn when it comes to grub imo.

So in order completely uninstall grub I had to modify the command to sudo chroot "/mnt/boot-sav/sda7" apt-get purge -y --force-yes grub*shim-signed linux-signed* grub-common:i386 and once finished I was able to proceed with the boot repair.

elitechief21
  • 181
1

When trying to update 16.4 grub while using 21.04 I got this error. Copy pasted the command it was trying to run in a separate terminal and ran it:

sudo chroot "/mnt/boot-sav/sda1" apt-get purge -y --force-yes grub*shim-signed linux-signed* grub-common:i386

Then boot-repair asked to copy paste another command to install grub. There in I chose /dev/sda and installed grub. Then was able to remove the usb drive (live cd) and reboot to see grub smiling back at me.

All this because I installed windows after installing ubuntu. MS is starting to show some respect to Linux with native subsystem for Linux but it's ridiculous that it still ignores ubuntu at the boot/grub level.

AEM
  • 1,156
  • 2
  • 14
  • 19
norootsquash
  • 11
1

In my case I run the same commands but with the sda4 partition (so don't just copy and paste):

sudo chroot "/mnt/boot-sav/sda4" dpkg --configure -a
sudo chroot "/mnt/boot-sav/sda4" apt-get install -fy
sudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub*-common shim-signed

But when I run the last one I got this:

Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'grub2-common' for glob 'grub-common' Note, selecting 'grub-common' for glob 'grub-common' Package 'grub-common' is not installed, so not removed. Did you mean 'grub-common:i386'? Package 'grub2-common' is not installed, so not removed. Did you mean 'grub2-common:i386'? Package 'shim-signed' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.

Note that the command was trying to remove grub-common but there was installed grub-common:i386. So I run the same command adding that version to the end:

sudo chroot "/mnt/boot-sav/sda4" apt-get purge --allow-remove-essential -y grub*-common shim-signed grub-common:i386

The output said that the package had been removed successfully and I could continue with boot-repair

Genarito
  • 123
0

I ran into this problem today, and it turns out the last line sudo chroot "/mnt/boot-sav/sda7" apt-get purge -y --force-yes grub*shim-signed didn't run. So I pressed enter again and everything worked.

user806098
  • 1