Bug 1136123 - Anaconda freezes during bootloader install - fails to set new efi boot target
Summary: Anaconda freezes during bootloader install - fails to set new efi boot target
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-01 23:15 UTC by David B
Modified: 2023-09-14 02:46 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-15 18:52:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda program output (3.31 MB, text/plain)
2014-09-01 23:15 UTC, David B
no flags Details

Description David B 2014-09-01 23:15:38 UTC
Created attachment 933564 [details]
anaconda program output

Description of problem:
Anaconda fails to set new efi boot target

Version-Release number of selected component (if applicable):
anaconda 20.25.15-1

How reproducible:
always

Steps to Reproduce:
1. Choose Language: English
2. Select Installation Destination: Custom Partitioning
   a. Delete all filesystems on disk
   b. Automatically create partitions
3. Begin Installation
4. Set Root Password
5. Create User

Actual results:
Install proceeds until bootloader installation, then freezes and produces error message.

Expected results:
Anaconda Completes Fedora installation

Additional info:
Booting from Sandisk Extreme 16 GB USB Flash Drive SDCZ80-016-X46
Live CD iso downladed on 9/1/14 from: http://fedora.mirrors.pair.com/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso

System information:
Asus U52F laptop

00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
02:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 [Kilmer Peak] (rev 5f)
03:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)

Comment 1 Brian Lane 2014-09-03 01:52:34 UTC
When this happens can you try running this from the shell?

strace -o efibootmgr.strace efibootmgr -c -w -L Fedora -d /dev/sda -p 1 -l \EFI\fedora\shim.efi

And attach efibootmgr.strace to this bug.

Comment 2 Red Hat Bugzilla 2023-09-14 02:46:46 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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