grub_efi_secure_boot symbol not found after update to grub 1.99-21ubuntu3.7

[Bruce R. Copeland]

On a working HP ENVY m4-1015dx system using UEFI without secure boot, the system is unable to boot into Ubuntu 12.04 from OS Boot Manager following update to grub 1.99-21ubuntu3.7. The grub 1.99-21ubuntu3.7 menu appears correctly. However, selecting any ubuntu kernel generates the error:

symbol not found: `grub_efi_secure_boot'.

The system will boot successfully into Windows 8 from the same grub menu. The system also boots successfully to ubuntu from other BIOS boot options: Ubuntu (WDC ...) or Boot from EFI File and then selection of the file EFI/ubuntu/grubx64.efi. Either of these latter successful boot options produce a grub menu that appears identical to the earlier-mentioned grub menu, but these boot successfully. At least two other individuals using different hardware have reported analogous problems on the forums (ie. systems using UEFI but NOT secure boot). These problems may depend to some extent on the BIOS, but they do not appear to be unique to this particular hardware.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: grub-efi 1.99-21ubuntu3.7
ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
Uname: Linux 3.2.0-35-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Sat Jan 12 12:05:57 2013
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

[Colin Watson (cjwatson)]

This generally indicates that GRUB's core image and modules are out of sync. That's more usual on BIOS installations, but it's possible on UEFI too. Perhaps you didn't have your EFI System Partition properly mounted on /boot/efi when upgrading grub-efi-amd64?

[Bruce R. Copeland (runningmtns)]

It seems unlikely that the EFI System Partitition was not properly mounted. I booted successfully a couple dozen times before the grub 1.99-21ubuntu3.7 update. Moreover the EFI System Partition contains an EFI/ubuntu/grubx64.efi file that shows a timestamp corresponding to the grub 1.99-21ubuntu3.7 update. That would have been difficult to achieve if the EFI System Partition was not properly mounted at the time of the update.

This appers more likely to be some kind of path problem, since the system WILL boot successfully when the grubx64.efi is explicitly chosen.

[Colin Watson (cjwatson)]

A path problem is only possible if there is some other GRUB installation on the system. Could you look for other .efi and .mod files?

[Launchpad Janitor (janitor)]

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