Bug 1024169 – "Bootloader has not verified loaded image" after F20 beta install

Bug 1024169 - "Bootloader has not verified loaded image" after F20 beta install

Summary:	"Bootloader has not verified loaded image" after F20 beta install

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	shim (Show other bugs)
Sub Component:
Version:	20
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Matthew Garrett
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-10-29 00:19 EDT by Andrew Schultz
Modified:	2014-01-17 21:12 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-01-17 21:12:00 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Schultz 2013-10-29 00:19:03 EDT

Description of problem:
After installing F20 beta TC6 to a Toshiba laptop (Satellite P50-A) via live image, grub comes up offers to boot the linux kernel.  However, after selecting the kernel, it says

Bootloader has not verified loaded image.
System is compromised. halting.

and then it powers down.

The one strange bit during the install was that it did not automatically recognize the system's existing EFI partition (/dev/sda2, used by windows), and instead wanted to create a new one.  I manually directed it to use sda2 (deleted the one it wanted to create and told it to mount /dev/sda2 as /boot/efi, but to not format it).

The install recognized windows being already installed and added that as another boot option in grub.  Selecting that allows windows to boot happily.

Comment 1 Andrew Schultz 2014-01-17 21:12:00 EST

After a BIOS update and installing F20, the system boots fine.

Note You need to log in before you can comment on or make changes to this bug.