Bug 5041

Summary:	Kickstart dynamic partition assignment leaves /boot out of range
Product:	[Retired] Red Hat Linux	Reporter:	Andrew Macpherson <andrew>
Component:	installer	Assignee:	Jay Turner <jturner>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	andrew, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	sparc
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-02-08 13:06:33 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 Andrew Macpherson 1999-09-10 08:30:15 UTC

Built a kickstart file, relevent portion
=====================================
zerombr no
clearpart --linux
part / --size 60
part swap --size 127
part /usr --size 600
part /usr/local --size 200
part /var --size 105
part /home --size 1 --grow
install
=================================================

And ran this on a 2G scsi disk (on a SparcStation 2)

This built partitions:

sda1 /var
sda2 swap
sda3 -- Whole disk -- untouched
sda4 /usr               \ Might have the order of these 2
sda5 /usr/local         / transposed
sda6 /
sda7 /home

/ on sda6 unfortunately starts more than 1024 M into the
disk so SILO fails, and when one switches Alt-F2 to try to
run by hand, "silo -r /mnt" one gets a rather obscure error
about /boot/second.b

Workaround was of course to leave /usr/local for the %post
phase, dividing a larger /home

Comment 1 Jay Turner 2000-02-08 13:06:59 UTC

We have introduced new arguments to kickstart which allow you to specify the
partition on which to create a certain mount point.  This will solve the problem
you are seeing in this report.