Bug 858355 - you have not created a bootloader stage1 target device
Summary: you have not created a bootloader stage1 target device
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: ppc64
OS: Linux
high
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-18 18:52 UTC by Mark Hamzy
Modified: 2012-10-10 20:10 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-10 20:10:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (27.94 KB, application/octet-stream)
2012-09-18 18:52 UTC, Mark Hamzy
no flags Details
program.log (32.61 KB, application/octet-stream)
2012-09-18 18:53 UTC, Mark Hamzy
no flags Details
storage.log (223.56 KB, application/octet-stream)
2012-09-18 18:53 UTC, Mark Hamzy
no flags Details

Description Mark Hamzy 2012-09-18 18:52:23 UTC
Created attachment 614102 [details]
anaconda.log

Description of problem:

Running anconda from git version commit 9899fc7a2f3340a0ecf2107000be3510e5a40960.

How reproducible:
Occasionally.

Steps to Reproduce:

Check for manual partitioning when selecting a disk.
Delete previous installation.
Make the following partitions:
1) PReP boot partition
2) /boot partition
3) swap partition
4) / partition

which looks like this: http://hamzy.fedorapeople.org/ManualPartitioning3.png
  
Actual results:
When finished, I receive the following error:

you have not created a bootloader stage1 target device

Expected results:
No error.

Comment 1 Mark Hamzy 2012-09-18 18:53:13 UTC
Created attachment 614103 [details]
program.log

Comment 2 Mark Hamzy 2012-09-18 18:53:32 UTC
Created attachment 614104 [details]
storage.log

Comment 3 Chris Lumens 2012-10-09 14:30:36 UTC
Are you still seeing this error?

Comment 4 Mark Hamzy 2012-10-10 20:10:07 UTC
I am not seeing this on anaconda-18.14-1.


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