Description of problem: Install with 20060214 rawhide fails to partition the disk. ks below and anaconda.log attached. install text nfs --server=saga --dir=/export/data1/fedora/core/development/i386 lang en_US keyboard us network --bootproto=dhcp rootpw --iscrypted CwU/lYtazWt7E firewall --disabled authconfig --enableshadow --enablenis --nisdomain=yp.colorado-research.com timezone America/Denver xconfig --startxonboot --defaultdesktop=KDE --resolution=1600x1200 --depth=24 bootloader --location=mbr clearpart --linux --drives=hda part /boot --fstype ext3 --size=50 part pv.1 --size 4800 --grow volgroup rootvg pv.1 logvol / --vgname=rootvg --size=512 --name=root logvol swap --fstype=swap --vgname=rootvg --recommended --name=swap logvol /usr --vgname=rootvg --size=4000 --name=usr logvol /var --vgname=rootvg --size=256 --name=var logvol /export/data1 --vgname=rootvg --size=1 --name=data1 --grow reboot
Created attachment 124651 [details] anaconda log
Screen shows: Error partitioning Could not allocate requested partitions: Partitioning failed: Could not allocate partitions. Press 'OK' to reboot your system. Single IDE disk with empty partition table.
What happens if you make your /var partition at least 384 megs and your /boot partition at least 75 megs?
No effect. FYI - this kickstart file has worked for me for a long time.
Hm, I'm unable to reproduce your bug on a machine here with the same ks partitioning information and one IDE disk I wiped the partition table from. Can you think of anything that might help me to reproduce this one?
Crap! I am so sorry - I'm using a 4GB disk and it doesn't fit. Perhaps a better error message (there is not enough space to allocate the requested partions) to help idiots like me?
Better error messages for this partitioning stuff would be very helpful, but it's too late for FC5 to do anything about that (after freeze for translations, etc). Moving to FC6Target so we can try to get it done for then.
We can now do a better job on this particular error message. The partitioning code is kind of a maze, though, so I'm not going to be able to track down every bad error message. If you run into another one that makes no sense, please file another bug.