Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Upgrading from Ubuntu 13.10 to Ubuntu 14.04 has resulted in a system that is not bootable.

The system consists of two disks: One with Windows 8 (/dev/sdaX) and one with Ubuntu 14.04 (/dev/sdbX). I was previously booting using an EFI partition /dev/sda2, but the Ubuntu upgrade installer has rendered this inoperative: it fails to a gparted fallback screen. /dev/sdb was originally a legacy MBR/BIOS-based system. I have attempted to create an EFI partition on /dev/sdb1, but I am not sure if I did it right. Boot-repair fails to fix either EFI partition.

Both Windows and Ubuntu are bootable with the assistance of super grub disk, but that is only the way I can get either system to boot.

Secure boot is not enabled.

Boot information is here:

Do you have any recommendations for me? This looks like the bug given in , but there is no clear resolution available.

share|improve this question
up vote 1 down vote accepted

I recommend you try my rEFInd boot manager. (It looks like you may have tried it at some point in the past but I see no evidence that it's currently installed.) Use the CD-R or USB flash drive version from the rEFInd downloads page for testing. If that doesn't work, you'll have done no more harm and you can move on to some other approach; but if it does work to boot both Linux and Windows, you can install the Debian package (either single-shot using the package from the downloads page or by using the PPA referenced at the bottom of the downloads page).

share|improve this answer
Would you recommend installing it on my sda or sdb? – Colin Jun 10 '14 at 12:59
It shouldn't matter; use whichever one is currently mounted as /boot/efi. – Rod Smith Jun 11 '14 at 0:15

The rEFInd bootloader did the trick. My system's EFI firmware does not remember the symbolic "refind" name, however: it only remembers devices, and it will always try and boot the device default. To get around this, I had to install refind from the script with

./ --usedefault /dev/sdXX

Read the install guide before using this option. If you use the wrong /dev entry, you could wipe out all your data.

It might be useful if the PPA version of refind had some dpkg-reconfigure style option to that extent.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.