From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-12smp i686; en-US; rv:0.9.1) Gecko/20010622 Description of problem: I am trying to create a kickstart that creates very specific partitions as far as size,location and partition type. I have set up my ks.cfg (will attatch this after) noting the documentation error from bugzilla bug #39966; but no dice.. I really have no choice in the matter, the partitions are being done for a specific reason. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Create boot disk using included ks.cfg 2. Attempt install from floppy 3. Watch it bail when creating partitions on VC_3 Actual Results: VC_3 indicates that it is unable to create the requested partitions, but the drive is empty, having had all partitions erased before attempting an install Expected Results: Well... It should create the partitions as indicated, and continue with the install. Additional info:
Created attachment 31034 [details] Here is the ks.cfg I am using (or rather trying to use)
if you remove the --asprimary specifications, does the partitioning work?
No. it still dies.. I tried the following as well (w/ just /boot with an --asprimary) but it still didn't work part swap --size 126 part /var --size 2784 part /boot --size 24 --asprimary part / --size 1569 part /services --size 3059 part /home --size 1184
can you try changing: part /services --size 3059 to: part /services --size 1 --grow ?
Okay after changing the line as indicated, it doesn't get anywhere.. It asks me for Language, then Keyboard, Install source, etc. So basically it is not working AT ALL now.
Generally, the asking for more information means a DHCP reply was not received -- maybe just try again? Also, how big is the drive on this machine? Note that anaconda will force the partitions to be aligned on cylinder boundaries, so the numbers given may or may not end up being exactly what's used.
>>Generally, the asking for more information means a DHCP reply was not received >>-- maybe just try again? Did that, still no dice. >>Also, how big is the drive on this machine? Note that anaconda will force the >>partitions to be aligned on cylinder boundaries, so the numbers given may >>or may not end up being exactly what's used. Well I understand that it matches the cylinder boundaries, but even when I had one of the partitions to (--size 1 --grow) it still bailed. This is a 9GB Drive, and the partition layout has been used (albeit manually) before trying the Kickstart Install.
Does this work any better with newer releases than 7.0? 7.0's partitioning was completely different from 7.2's and there isn't really any effort into fixing problems with the 7.0 stuff
Well this bug still exists in 7.2, and the additional (cylinder based) partitioning functionality added to 7.2 is broken as well.. (see bug #55138)... I would like to upgrade to 7.2, but the partitioning issue must be dealt with first as it will take a considerable amount of time to deploy without it.
Exactly what does the kickstart config you are using look like? I can't reproduce the problem here making a similar kickstart config, although I obviously have different sized drives. But the getting asked about network info and install location generally means that your kickstart config is not complete.
Closing due to inactivity, please reopen if you contine to have problems.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.