Bug 5041 - Kickstart dynamic partition assignment leaves /boot out of range
Kickstart dynamic partition assignment leaves /boot out of range
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
sparc Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
Depends On:
  Show dependency treegraph
Reported: 1999-09-10 04:30 EDT by Andrew Macpherson
Modified: 2015-01-07 18:38 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-08 08:06:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Macpherson 1999-09-10 04:30:15 EDT
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

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 08:06:59 EST
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.

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