Bug 75552 - No free primary
No free primary
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
7.1
All Linux
high Severity high
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-09 17:08 EDT by Need Real Name
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-09 17:15:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Current configuration of my hard drive. (1.24 KB, patch)
2002-10-09 17:15 EDT, Need Real Name
no flags Details | Diff

  None (edit)
Description Need Real Name 2002-10-09 17:08:31 EDT
Description of Problem:

I partitioned my 80GB Seagate with PartitionMagic
(under Windows Me), leaving 16GB of free space
at the end of my secondary partition.
I began my instillation of Linux 7.1, booting off of
CD #1 from the package. When I got to Disk Druid,
I clicked on the "add" button, added the swap partition (128MB).
I then clicked on the "add" button again to add the boot
partition, allocating 32MB. When I did this, I got
an error message for the swap partition ---> "No free primary."

WTF?????

I KNOW there is at least 16GB of free space available.
------------------------------------------------------

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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
Comment 1 Need Real Name 2002-10-09 17:15:23 EDT
Created attachment 79708 [details]
Current configuration of my hard drive.
Comment 2 Jeremy Katz 2002-10-14 12:22:35 EDT
Red Hat Linux 7.1 enforced the constraint that /boot had to be on a primary
partition and you have no free primary partitions.  Newer releases do not
require this.

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