Red Hat Bugzilla – Bug 55806
Will not create partitions based on what is in ks.cfg file
Last modified: 2005-10-31 17:00:50 EST
From Bugzilla Helper: User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i686) Description of problem: anaconda will not create partitions on redhat 7.1 alpha server based on what is defined in the ks.cfg file. It will drop you to manual partitioning using fdisk or disk druid. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. create ks.cfg 2. start this on alpha system Expected Results: auto partitioning of hard drives Additional info: ks.cfg file attached lang en_US keyboard us mouse none timezone --utc America/Los_Angeles cdrom network --bootproto static --ip 192.168.2.250 --netmask 255.255.255.0 --gateway 192.168.2.1 --nameserver 192.168.2.5 auth --useshadow --enablemd5 firewall --disabled zerombr no clearpart --all part / --size 4000 part swap --size 1000 part /var --size 10 --grow install %packages @Base @Mail/WWW/News Tools @Networked Workstation @NFS Server @IPX/Netware(tm) Connectivity @SMB (Samba) Server
*** Bug 55805 has been marked as a duplicate of this bug. ***
SRM can only boot from BSD partitions. Therefore, you need to make a /boot partition of a BSD type in your kickstart file. So, your partitioning section of the kickstart file needs to look something like: clearpart --all part /boot --size 40 --type=9f part / --size 4000 part swap --size 1000 part /var --size 10 --grow Does this solve the problem?
Now when I start the kickstart install, with the added line to the ks.cfg file, I get a invalid literal for int(): 9f. Then reboots the machine.
No, the problem is much worse. I get a python traceback just after anaconda reads the config file, then the machine reboots.
You need to use the integer form as opposed to 9f (so 159). Does this work better?
Thanks that fixed the problem. anaconda now kickstart without prompting the installer Kelly