Red Hat Bugzilla – Bug 1467754
boot-code installation failure
Last modified: 2017-07-24 21:21:45 EDT
Description of problem: Installer fails with unspecified fatal error trying to write boot-sector grub2 code, in performing a network install on existing but clean Linux partitions (and partition table) occupying entire disk.
Version-Release number of selected component (if applicable): I found this error on Beta 26 and release 25. Release 24 reported failure to write grub2 boot code.
How reproducible: always
Steps to Reproduce:
1. Boot net installer disk and follow steps to initialize installation
2. Download and install the requested software
3. Tell the installer to install the boot code to the boot sector of disk
Actual results: Installer successfully downloads and installs requested software and then fails to write boot code to boot sector of disk though the sector is writable according to the BIOS and previous distro installations.
Expected results: I expected the installer to write the grub2 boot code to the disk to make a bootable system.
Additional info: The hardware is an old P4 (32-bit) HP Compaq with 1 gb of main memory and 40 gb of disk, good enough for testing. Not a UEFI system, not 64-bit. I tried Beta 26, Release 25 and Release 24---all have installation problems. Release 23 worked for me. So the bug arose from installer changes after Release 23.
Trying to install a current non-Fedora distro immediately gave a specific error, a partition table that was said to be unreadable by the UEFI-compatible partition-reading code of that installer. This suggests to me that different parts of some installers may not be on the same page re UEFI vs legacy partitions, 32-bit vs 64-bit, partitioning and formatting, etc. It also makes me think that legacy code may have been wrongly deleted from installers.
What exactly do you mean by 'unspecified fatal error'? We can't do a lot about this without much more detailed information. For a start, it would help to see /tmp/anaconda.log and /tmp/program.log from the installer environment after the 'fatal error' has occurred.
You tell me. The error reporting by the installer was exactly that vague.
I, uh, asked you to attach some specific log files.