|Summary:||you have not created a bootloader stage1 target device|
|Product:||Red Hat Enterprise Linux 7||Reporter:||Chris Roberts <chrobert>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Release Test Team <release-test-team>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2014-08-11 13:34:37 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Chris Roberts 2014-07-31 16:31:10 UTC
Description of problem: when trying to select manual partitioning during RHEL7 install, the error "you have not created a bootloader stage 1 target device" while the /boot/ and /boot/efi are present How reproducible: Steps to Reproduce: when trying to select manual partitioning during RHEL7 install, the error "you have not created a bootloader stage 1 target device" while the /boot/ and /boot/efi are present Actual results: you have not created a bootloader stage1 target device Expected results: it to complete install Additional info: The OS loading interface for RH has a lot of things that I do not know about and are not very plane. I tried to build the machine using the automatic partitioning. When I did it came back asking if I wanted to get rid of the current disk partitions. In the interface it does not show or say anything about the current partitions except a closed list that means nothing to the unexperienced user. When it said that where was something already there I expanded the partitions and saw them. The interface should expand the partition list and ask the user if any of the old partitions need to be preserved. That error message I was getting was incorrect. It should have said that there are old partitions that are messing up the new load.
Comment 1 David Shea 2014-07-31 16:33:08 UTC
Please attach the log files from /tmp to this bug as individual, text/plain attachments.