Hi guys,
Hopefully somebody will be able to point out the obvious step I've missed
here, or the well-known bug I have failed to find!
I have a custom Kickstart CD that I built and have successfully used for a
number of months now. Apart from a recent change to remove the
kernel-enterprise package (RH didn't update this after RHSA-2002-205, but
that's a seperate story I guess) the build has worked perfectly.
This afternoon I ran the build on a Compaq server with 53GB of RAID storage,
and everything appeared to go OK during the build.
However, when I actually booted up the machine, only about 30GB of disk space
had actually been used - there was another 20GB that had simply not been
allocated by the install scripts.
The relevant section of the ks.cfg is as follows:
[...]
zerombr yes
clearpart --all
part /boot --size 8 --maxsize 35 --grow
part swap --size 128 --maxsize 256 --grow
part / --size 100 --maxsize 1024 --grow
part /usr --size 512 --grow
part /tmp --size 100 --maxsize 512 --grow
part /var --size 128 --maxsize 512 --grow
lilo --location mbr
[...]
and when the machine was built, I got:
# fdisk -l /dev/ida/c0d0
Disk /dev/ida/c0d0: 255 heads, 32 sectors, 13071 cylinders
Units = cylinders of 8160 * 512 bytes
Device Boot Start End Blocks Id System
/dev/ida/c0d0p1 * 1 9 36704 83 Linux
/dev/ida/c0d0p2 10 13071 53292960 5 Extended
/dev/ida/c0d0p5 10 6755 27523664 83 Linux
/dev/ida/c0d0p6 6756 6820 265184 82 Linux swap
/dev/ida/c0d0p7 6821 6949 526304 83 Linux
/dev/ida/c0d0p8 6950 7078 526304 83 Linux
/dev/ida/c0d0p9 7079 7336 1052624 83 Linux
(notice the discrepancy in size between the entire disk and the allocated
space!!)
Thanks for any tips or pointers you may think of..
Regards,
Jonathan
