Bug 44801

Summary: kickstart load from floppy failed
Product: [Retired] Red Hat Linux Reporter: Pharis Tyler <ptyler>
Component: mkkickstartAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-07-18 17:37:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda dump from kickstart attempt
none
cfg file requested by RH from ptyler see comments
none
Same problem with kickstart from floppy - anaconda.dump
none
Here is kickstart cfg file on floppy used (goes with prev attached anaconda dump) none

Description Pharis Tyler 2001-06-17 00:47:02 UTC 
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.
Comment 1 Pharis Tyler 2001-06-17 00:48:37 UTC 
Created attachment 21203 [details]
anaconda dump from kickstart attempt
Comment 2 Gary 2001-07-02 20:08:59 UTC 
AMEN The exact very same thing happened to me!
Comment 3 Matt Wilson 2001-07-02 20:12:19 UTC 
please also attach your ks.cfg file(s)
Comment 4 Pharis Tyler 2001-07-03 20:14:55 UTC 
Please see attached cfg file.
Comment 5 Pharis Tyler 2001-07-03 20:27:44 UTC 
Created attachment 22612 [details]
cfg file requested by RH from ptyler see comments
Comment 6 Pharis Tyler 2001-07-03 20:32:50 UTC 
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!
Comment 7 Chris Eggleston 2001-07-12 21:14:10 UTC 
Created attachment 23452 [details]
Same problem with kickstart from floppy - anaconda.dump
Comment 8 Chris Eggleston 2001-07-12 21:16:53 UTC 
Created attachment 23453 [details]
Here is kickstart cfg file on floppy used (goes with prev attached anaconda dump)
Comment 9 Need Real Name 2001-07-18 17:37:50 UTC 
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.
Comment 10 Jeremy Katz 2001-07-27 20:08:00 UTC 
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.