From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) Description of problem: Created ks.cfg from up machine at console (no X) using mkkickstart. used mcopy to place on floppy. Went to install on on another box (same config) by booting from CD1 and entering linux ks=floppy. Load begins and information is read from floppy then warning comes up asking to report the bug and write the problem to floppy.... which I did. (See attachment). Tried kickstaart 3 times with same result. Wrote a new kickstart file -no joy. How reproducible: Always Steps to Reproduce: 1.See Description Actual Results: See Description Expected Results: Should have been able to complete a kickstart load. Additional info: If this is occuring to others... they may not be happy if kickstart does this to them and they are relying on it to deploy.
Created attachment 21203 [details] anaconda dump from kickstart attempt
AMEN The exact very same thing happened to me!
please also attach your ks.cfg file(s)
Please see attached cfg file.
Created attachment 22612 [details] cfg file requested by RH from ptyler see comments
humpty5.cfg file was originally called ks.cfg. Name changed for history purpose and to prevent overwite. Sorry for the multiple entries. Had a hard time submitting .kfg attachment. Hey... how about a knarly RH hat for this? Just thought I would try!
Created attachment 23452 [details] Same problem with kickstart from floppy - anaconda.dump
Created attachment 23453 [details] Here is kickstart cfg file on floppy used (goes with prev attached anaconda dump)
I ran into the same problem using a manually created ks.cfg file but the file was very similar to the ones attached here. I was able to get it to install properly by changing my ks.cfg file as follows: I changed the lines: clearpart --all part swap --size 256 install to read: clearpart --all part / --size 2000 --grow part swap --size 256 part /boot --size 30 install These parameters for the root and boot partitions were suggested in a response to bug #40556.
Yep, this is due to to missing a declaration for the root partition in the kickstart config. I'd recommend using ksconfig instead of mkkickstart to create a kickstart config (it gives you a bit more control over the generated config) and have added some sanity checking to anaconda so that at least you'll get a more graceful failure in the future if partitions are missing.