Red Hat Bugzilla – Bug 531745
Anaconda changes boot flag to invalid partition, will not boot successfully
Last modified: 2009-12-15 10:16:43 EST
Description of problem:
Version-Release number of selected component (if applicable):
Fedora 12 beta, anaconda 12.37 i think
Steps to Reproduce:
1. Choose /boot to install to extended partition
2. Select boot manager installing to target partition (/dev/sda9 in my case)
3. After installer finished first pahse, reboots
4. mbr/BIOS will refuse to boot, because no partition of first 4 have boot flag present.
Previous /dev/sda3 is unmarked, and only marked is /dev/sda9.
Warning at install time, that it is not guaranteed to be able to boot. Give user choice to to keep original boot flag where it is, in case of booting new system using grub from other partition, as i do. I dont know if some loaders are able to boot from extended partitions as well, if no primary is marked, but i dont expect it common.
I know it is not typical installation, but also i think not that uncommon. It does not warn me or does boot, i think some change would be nice.
Created attachment 366602 [details]
fdisk of my layout
Created attachment 366603 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Thanks for the report, this should be fixed in rawhide/F13 with commit 0c0559f6f187815521364cb6d5118ad9faf24cc9.
*** This bug has been marked as a duplicate of bug 533658 ***