Bug 10568

Summary:	Creating /boot on RAID-1 over > 2 drives has issues.
Product:	[Retired] Red Hat Linux	Reporter:	Michael Fulbright <msf>
Component:	installer	Assignee:	Brock Organ <borgan>
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-06-20 22:13:57 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 Michael Fulbright 2000-04-03 22:06:14 UTC

Go into disk druid with 5 empty SCSI drives.

Create a 31 meg RAID partition on each drive - you will now have
sda1, sdb1, sdc1, sdd1, sde1

Make a RAID filesystem using disk druid using these 5 partitions as a
RAID-1 /boot.

Create another partition of any type, now the 5 RAID partitions will be
forced onto the first 2 drives because of the /boot constraint of being
on the first two drives. Did not impose this until another partition
existed.

Workaround: Create RAID partitions with fdisk before entering the disk
druid screen.

Comment 1 Jay Turner 2000-04-12 11:57:59 UTC

This issue has been forwarded to a developer for further action.

Comment 2 Michael Fulbright 2000-06-12 18:43:16 UTC

Should be fixed in latest internal release - please verify.

Comment 3 Brock Organ 2000-06-20 22:13:46 UTC

disk druid now prevents using more partitions from more than 2 drives... this
will show up in the next release ...