Red Hat Bugzilla – Full Text Bug Listing
|Summary:||bootloader error during initial install|
|Product:||[Fedora] Fedora||Reporter:||Thom Carlin <tcarlin>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||NEW ---||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||26||CC:||anaconda-maint-list, g.kaviyarasu, jkonecny, jonathan, mkolman, tcarlin, vanmeeuwen+fedora, vponcova|
|Fixed In Version:||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Thom Carlin 2017-07-27 20:38:18 EDT
Description of problem: Unexpected bootloader error during initial install of Fedora 26 on HP Envy machine Version-Release number of selected component (if applicable): 26 How reproducible: 100% with specific configuration Steps to Reproduce: 1. Attempt to install Fedora 26 on brand new HP Envy machine Actual results: Anaconda errors out with bootloader error Expected results: Successful install Additional info: Background/workaround (from my memory): I had used blivet to create a custom partition layout. Without any real additional information, I booted into rescue mode. Once there, I tried: grub2-install /dev/sda Grub reported a problem with no BIOS boot being set in the GPT. This led to a superuser.com article which mentioned gdisk. gdisk /dev/sda On startup, it mentioned something about a "protective MBR" Selecting "r" brought up the "recovery and transformation options (experts only)" Selecting "x" brought up the "extra functionality (experts only)" Selecting "z" led to "zap (destroy) GPT data structures and exit" Selecting "w" wrote the table to disk and exit After that, grub2-install worked After that, I reran anaconda with the same options. It completed successfully and the system rebooted correctly into Fedora 26.
Comment 1 Jiri Konecny 2017-07-28 04:07:54 EDT
Hi Thom, Could you please provides logs from the failed installation?
Comment 2 Thom Carlin 2017-07-30 15:03:25 EDT
The logs are no longer available.
Comment 3 Thom Carlin 2017-07-31 09:36:17 EDT
It would be useful if there was a way to easily do Abrt or even retrace on these types of errors. There was network connectivity at the time of the issue. As I recall, the only visible option was Debug to a Python debug shell.