I am trying to write a kickstart configuration file for a small cluster of servers that I am building. Each machine has a 20G Maxtor hard drive which has a translated CHS of 2491/255/63 I set the partitions up in ks.cfg as follows part / --size 1536 part swap --size 2048 part /usr3 --size 7969 part /usr2 --size 7969 However the partition table on the disk had the partitions in reverse order with the result that the root partition was well above the 1024 cylinder limit and the installation wouldn't boot. It is somewhat counter-intuitive that the partition order on the disk does not follow the order given in the configuration file (in fact changing the file order doesn't have any effect on the on-disk layout) and placing the partition containing the kernel above cylinder 1024 is a definate bug. In the end I use the %post script to create the two 8G partitions. Even then the swap partition ended up as /dev/hda1 (and had the LILO boot sector installed) although / was listed first in the config file. The 1024 cylinder problem should "go away" with new versions of lilo but the fact that one cannot control the order in which partitions are created seems to be something of a problem. The --onpart switch is not much use to me as the install needs to work on a new machine which has no partition table.
Brock please try to verify, and if this is a problem please test against latest internal version to see if it is corrected.
Verified problem against 6.2 & Winston RC-1 ...
Will address in code rewrite.
How is our status on this Jeremy?
Shouldn't be able to happen with the new code base. We always place the "boot" partition as much at the start of the drive as we can (either /boot or /, depending on if /boot exists as a separate partition or not)