Created attachment 344215 [details] anaconda-logs.tgz (ks.cfg, /tmp/*log*) Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install F11 using clearpart + autopart with more than 1 disk 2. Reinstall F11 using the anaconda-ks.cfg generated #clearpart --all --initlabel #volgroup vg_ibmsf2blp1 --pesize=4.0 pv.Uh3uOT-WMyK-tf5d-6nhh-lm5e-P3cO-CsfPwO pp v.e3k1N8-llW7-Opoo-hcq0-RRe3-Jhk0-iRFav1 #logvol / --fstype=ext4 --name=lv_root --vgname=vg_ibmsf2blp1 --grow --size=1024 #logvol swap --name=lv_swap --vgname=vg_ibmsf2blp1 --grow --size=1000 --maxsize== 9728 #part prepboot --fstype=prepboot --size=4 #part /boot --fstype=ext3 --size=200 #part pv.Uh3uOT-WMyK-tf5d-6nhh-lm5e-P3cO-CsfPwO --grow --size=1 #part pv.e3k1N8-llW7-Opoo-hcq0-RRe3-Jhk0-iRFav1 --grow --size=1 Actual results: Dialog stating: ============================== Error Parsing Kickstart Config ============================== The following error was found while parsing your kickstart configuration: The following problem occurred on line 19 of the kickstart file: Tried to use undefined partition pv.Nlog0D-xM7K-qNiy-5b0F-t2aU-AKOh-6HUYzP in Volume Group specification ============================== Expected results: * Successful install Additional info: * see attached ks.cfg and /tmp/*log* files
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm not sure what's going on with the pv.WHATEVER in the error message not matching up with anything in the kickstart file. However, it looks at least like the order is incorrect. What happens if you reorder the kickstart file to have part lines, then volgroup, then logvol?