Bug 497390 - autopart puts PReP and '/boot' on different disks
Summary: autopart puts PReP and '/boot' on different disks
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11AnacondaBlocker
TreeView+ depends on / blocked
 
Reported: 2009-04-23 17:06 UTC by James Laska
Modified: 2013-09-02 06:35 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-05-06 21:24:44 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description James Laska 2009-04-23 17:06:42 UTC 
Description of problem:
On an IBM power5 system, autopart puts the PReP and '/boot' partitions on different disk.  Due to a yaboot limitation (I think), these partitions must exist on the same disk.

Version-Release number of selected component (if applicable):
anaconda-11.5.0.47

How reproducible:
every autopart install

Steps to Reproduce:
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_install
  
Actual results:
While partitioning will work, yaboot is unable to boot in such a scenario.

Expected results:
In F10 and RHEL5, PReP and '/boot' are always on the same disk (typically sda1 and sda2).

Additional info:
Comment 1 Chris Lumens 2009-05-05 19:30:00 UTC 
This should be fixed in the next build of anaconda.  Thanks for the bug report.
Comment 2 Chris Lumens 2009-05-06 21:24:44 UTC 
Actually, I tested this on ppc as well, so moving to CLOSED.
Note You need to log in before you can comment on or make changes to this bug.