The partitioning scheme that anaconda is giving me, doesn't match the one
that I provided in the kickstart config. No matter what I've used to keep the
contents of the second drive intact, the drive is always repartitioned with a
swap drive. We're planning to upgrade a large number of RH7.3 boxes to RH9,
but until we can get the installer not to touch the second drive, we can't go
ahead. Is this due to a bug in anaconda or a problem in the ks.cfg?
Provided partitions in ks.cfg
clearpart --drives hda --initlabel
part /boot --fstype ext3 --size 64 --asprimary --ondisk hda
part / --fstype ext3 --size 4096 --grow --asprimary --ondisk hda
part swap --size 2048 --asprimary --ondisk hda
part /scratch --onpart hdb1 --grow --noformat #Also tried not mentioning this
#drive in the ks.cfg, but still have problems
Resulting partitions (from anaconda-ks.cfg)
#part /boot --fstype ext3 --size=64 --ondisk=hda --asprimary
#part swap --noformat --onpart hdb1
#part / --fstype ext3 --size=4096 --grow --ondisk=hda --asprimary
#part swap --size=2048 --ondisk=hda --asprimary
--
~Erik Volkman
Systems Administrator Assistant
