Bug 8567

Summary:	New partitions are always created on 2.HD
Product:	[Retired] Red Hat Linux	Reporter:	Karsten Hopp <karsten.hopp>
Component:	installer	Assignee:	Michael Fulbright <msf>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-02-15 16:35:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karsten Hopp 2000-01-18 12:56:00 UTC

During a graphical install on a new system with 2 new, blank harddrives
diskdruid  installed new partitions always on the second drive, it doesn't
matter which drive is selected for partitioning. The swap partition could
be created on the first disk.

Comment 1 Jay Turner 2000-02-03 22:37:59 UTC

First, were you selecting the specific drive to create the partition on in the
"Add" dialog?  If you were, was Disk Druid still putting them on another drive?
There is a new feature in the installer which will put partitions on the drive
with the most free space, so if you are not specifying which drive to place the
partitions on, they can land on the second drive only if it is significantly
larger than the first drive.

Comment 2 Jay Turner 2000-02-05 16:27:59 UTC

In the lab today, we had a situation where no matter what we told the installer,
it would place the root partition on the second driver no matter what.  This was
becuase there was more space on the second drive.  We are going to fix this
problem and hopefully that will fix yours as well.  Unfortunately this change
will not make it into beta3.

Comment 3 Jay Turner 2000-02-15 16:35:59 UTC

Issue is resolved in the next cut of the beta.