Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 98921 - failed to partition with --onpart and cd images on HD
failed to partition with --onpart and cd images on HD
Status: CLOSED DUPLICATE of bug 90090
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-07-10 09:52 EDT by Michael E Brown
Modified: 2007-04-18 12:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:57:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael E Brown 2003-07-10 09:52:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:

When installing from hard drive with ISO images on the hard drive, the
"--onpart" directive cannot be used to use the partition containing the ISO
files as another partition. 

For example:
   /dev/sda1 -- contains ISO images.

part /home --onpart sda1 --noformat

This will give an error "Cannot allocate requested partition". I would like
/dev/sda1 to become /home and to contain the ISO images when the installation is

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

How reproducible:

Steps to Reproduce:
1. Copy ISO images to HD
2. In ks.cfg, use the partition containing the ISO images in a "part" directive.
3. See helpful error message

Actual Results:  error message

Expected Results:  install should have used partition containing ISO images 

Additional info:
Comment 1 Michael Fulbright 2003-07-11 11:38:24 EDT

*** This bug has been marked as a duplicate of 90090 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:57:00 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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