Ubuntu installer installed grub-efi (instead of grub-pc) on non-GPT disk --> does not boot

[Robert Sander]

A standard installation of ubuntu-desktop on a HP Compaq 6200 PC installs grub-efi and is not able to boot after first restart.

Grub complains about "no such partition". It is not able to load its own modules to continue with the boot process.

After booting into a rescue system and manually replacing the grub-efi package with grub-pc and re-installing grub to the MBR the computer boots fine.

Why is grub-efi installed automatically?

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: grub-efi (not installed)
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 15 12:01:19 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallCmdLine: BOOT_IMAGE=/install/vmlinuz file=/cdrom/preseed/ubuntu.seed priority=low --
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
NonfreeKernelModules: nvidia
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Tags: precise
Uname: Linux 3.2.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[YannUbuntu (yannubuntu)]

Here Ubiquity (the Ubuntu installer) incorrectly installed Ubuntu in EFI mode when it should have installed in in Legacy mode.

Probably because the BIOS is setup to boot the liveCD in EFI mode, but is also setup to boot the HDD in Legacy mode.

@Robert: please could you indicate if you installed Ubuntu alone, or in dualboot with Windows ?
please could you also indicate your Boot-Info URL ( https://help.ubuntu.com/community/Boot-Info ) ?

[Robert Sander (gurubert)]

Hi Yann,

I have installed Ubuntu as the only OS on that machine, Windows was not even pre-installed.

[YannUbuntu (yannubuntu)]

Thanks Robert
please could you also indicate your Boot-Info URL ( https://help.ubuntu.com/community/Boot-Info ) ?

[Robert Sander (gurubert)]

Boot-Info from booting via EFI: http://paste.ubuntu.com/1214279/

[Robert Sander (gurubert)]

Boot-Info from booting via SATA-BIOS: http://paste.ubuntu.com/1214291/

[YannUbuntu (yannubuntu)]

You disk is not GPT, so Ubiquity (the Ubuntu installer) shouldn't have installed grub-efi.

Please:
1) boot into your installed Ubuntu,
2) then login to your Launchpad account
3) then open a terminal (Ctrl+Alt+T) and type the following command:
apport-collect -p ubiquity 1013595

[Robert Sander (gurubert)]

apport information

[Robert Sander (gurubert)]

apport information

[Robert Sander (gurubert)]

apport information

[YannUbuntu (yannubuntu)]

Thanks.

Maybe duplicate of Bug #1026616

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael (mimuelle)]

I had the same problem with a fresh installation of Ubuntu 12.04.3 from a USB stick on a brand new Fujitsu Lifebook E782 with preinstalled Windows 7 64bit with classic BIOS and MBR partition scheme.

[TJ (tj)]

A note to clarify expectations on an UEFI system.

If the installer boots in UEFI mode the installer detects this through the presence of the EFI variables node in the sysfs at /sys/firmware/efi/vars. In this case the grub-efi package and its dependencies is selected, installed, and configured.

The installation target disk-label (MBR or GPT) has *no* place in the choice of grub-efi or grub-pc. The UEFI standard mandates support for UEFI boot from GPT (with an EFI System Partition [0xEF00 in gdisk tools]) or MBR (with partition type 0xEF) partitioned devices.

On UEFI systems to ensure an installation for CSM (Compatibility Support Module)/Legacy BIOS + grub-pc boot the *installer* must be booted using the CSM/Legacy mode.

To fix this after the installer has completed (only in Try .. mode on Live images) the user needs to manually change the installation via terminal commands and a 'chroot'. Satisfy yourself the installation is correct and successful before rebooting. If unclear ask for help on IRC channel #ubuntu on the Freenode network; mention the phrase "bug #1013595" in your request.

( lines beginning with # are only comments and should not be typed)
E.g:

sudo -i

[ -d /target/etc ] || echo "Root file-system is not mounted at /target/, please fix that and retry this command before continuing"

# mount the kernel file-systems in the target
for n in proc sys run dev dev/pts etc/resolv.conf; do mount --bind /$n /target/$n; done

chroot /target
# now operating in the installed environment; should have network access and DNS

mount -a
umount /boot/efi

# remove the EFI file-system from the auto-mount table
sed -i '/boot\/efi/ d' /etc/fstab

apt-get remove 'grub-efi*'
apt-get install grub-pc
lsblk -f
grub-install /dev/sdX # replace X with the correct disk id
update-grub

# check the installation is correct

exit

# back in the installer environment
reboot

[Phillip Susi (psusi)]

I'm not able to reproduce this. Installing to a DOS partitioned disk that does not already have an OS on it and choosing the option to use the entire disk causes it to be formatted using GPT and the install proceeds normally. Choosing manual partitioning and designating an ESP tags it with the proper dos EF partition ID and UEFI boots it. Is anyone able to reproduce this still?

[Launchpad Janitor (janitor)]

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]