Bug 17989

Summary:	"/" put on wrong part of disk, lilo/boot fails
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <mrovner>
Component:	anaconda	Assignee:	Michael Fulbright <msf>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.2	CC:	strobert
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-03-05 23:17:17 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 Need Real Name 2000-10-01 03:56:40 UTC

Relevant part of the kickstart config file:

	clearpart --all
	zerombr yes
	part / --size=256 --ondisk=sda
	part swap --size=1024 --ondisk=sda
	part /usr --size=2024 --ondisk=sda
	part /var --size=1024 --ondisk=sda
	part /tmp --size=512 --ondisk=sda
	part /home --size=1024 --ondisk=sda
	part /opt --size=1024 --ondisk=sda --grow
	part /opt/content --ondisk=sdb --grow

What I get is an sda ordered by what looks like reverse size order.  /usr
appears first,
and so on, down to / on sda8, which is also at the very end of the disk. 
lilo complains about
this and RHL fails to boot.

Harware in question:
	VA Linux box
	On-board Adaptec controller
	Two 18G UltraSCSI drives.

What gives?

						- Marc David Rovner
						  [ ] ( ) / \ . com

Comment 1 Michael Fulbright 2000-10-02 22:37:47 UTC

Brock please verify.

Comment 2 Brock Organ 2000-11-03 16:13:29 UTC

verified this behavior in both 6.2 & 7 ... thanks for your report!

Comment 3 Steven Roberts 2001-02-05 07:25:43 UTC

Based on some readin via Deja, it appears anaconda uses a reverse disk size sorting (takes biggest parition first and lays it down).

the deja article that talks about how to get around this using --grow and --maxsize:
http://x66.deja.com/getdoc.xp?AN=607131878&CONTEXT=981352670.1271201875&hitnum=1

Still haven't found a way to get around the problem reported in bugs 11698/20221

Comment 4 Michael Fulbright 2001-03-05 23:17:13 UTC

I believe I have fixed this - a quick test showed that '/' is now put first.