Bug 1026085

Summary: Unknown error halting live install on UEFI hardware at bootloader install
Product: [Fedora] Fedora Reporter: Don Church <donchurch>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, bugzilla, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-04 17:26:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Don Church 2013-11-03 14:26:30 UTC 
Quote from bug 986431:
************************
 Don Church 2013-11-02 21:33:25 EDT

Live install on new Panasonic FZ-G1 tablet with hd4000 graphics in vesa mode on extended paritition having win8 gpt ssd.  All seemed normal util unknown error but I see it stopped at bootloader installation.  I did created the requested bios boot partition along with home, root and swap.  I have the bios set to where I have installed several distros successfully.  My problem has been video though and only the latest Opensuse and Ubuntu have had the driver needed to install without special methods.

cmdline:        /usr/bin/python  /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 --xdriver=vesa
cmdline_file:   initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-19-1 rootfstype=auto ro rd.live.image quiet  rhgb rd.luks=0 rd.md=0 rd.dm=0 xdriver=vesa nomodeset BOOT_IMAGE=vmlinuz0 
hashmarkername: anaconda
kernel:         3.9.5-301.fc19.x86_64
other involved packages: python-libs-2.7.5-1.fc19.x86_64
package:        anaconda-19.30.13-1.fc19.x86_64
product:        Fedora
reason:         BootLoaderError: bootloader install failed
release:        Fedora release 19 (Schrödinger’s Cat)
version:        19

 Chris Murphy 2013-11-02 23:50:07 EDT

(In reply to Don Church from comment #56)
> Live install on new Panasonic FZ-G1 tablet with hd4000 graphics in vesa mode
> on extended paritition having win8 gpt ssd...[snip] ... I did created the
> requested bios boot partition along with home, root and swap.

Since this is Windows and a GPT disk that means the hardware is UEFI, thus there is an EFI System partition. The Fedora installer requesting BIOS boot partition, means the Fedora live desktop media is booted with a CSM to emulate BIOS. This bug relates to MBR disks, so there must be some anaconda/libreport confusion sending you to this bug.

Could you file a new bug report against component anaconda and cite the new bug number in this bug? And include in the new report as separate plaintext attachments the anaconda-tb*, program.log, and storage.log from /tmp from the live system? Thanks.
***********************************

My apologies, as I have since temporarily removed Win8 partitions in order to get a working Fedora system.  I'd like to dual boot so I may be able to again duplicate this bug and attach the requested files.
Comment 1 Brian Lane 2013-11-04 17:26:29 UTC 
Sorry, but without the logs there isn't anything we can do. I'd like to see why the Fedora install thought it wasn't using UEFI mode. Having win8 on there shouldn't affect how the Fedora installer boots.

Please re-open when you have logs. Attach them as individual text/plain files, and also describe how you created your boot media.

If you could do it with F20 it would be more helpful, since we don't update the installer after a Fedora release.