Red Hat Bugzilla – Bug 47652
Install stops when trying to do kickstart from ftp
Last modified: 2007-04-18 12:34:31 EDT
Description of Problem:
I made a kickstart file with url set to our own ftp server, and I made a
bootnet.img disk, where I modified the ks entry to point to my kickstart
When booting from the modified bootnet.img floppy, it finds the network
(DHCP), it finds the kickstart file (on an nfs drive), and I think it also
finds the ftp server. But very short after start, it crashes. The anaconda
error message says I should please eport the bug as soon as possible, so,
you've asked for it.
This is the file it saved on a floppy for me:
My kickstart file: http://www.it-c.dk/~hm/tmp/kickstart.ks
My syslinux.cfg from bootnet.img: http://www.it-c.dk/~hm/tmp/syslinux.cfg
Sorry if I'm beeing stupid, I have no previous experience with kickstart.
I don't understand why you needed to modify the bootnet.img.
I modify syslinux.cfg to tell it where on the net to find my kickstart file.
According to the RedHat Linux KickStart HOWTO I need to do either this, or make
room for the kickstart file on the floppy itself by deleting some unneccesary
No, you should be able to make a boot floppy with the standard bootnet.img.
Then, mount that floppy and copy your kickstart file to it. Then, boot off the
floppy and then type 'linux ks=floppy' at the syslinux bootup screen. It is
possible to pass the options to syslinux at the bootup screen...you should not
have to modify the syslinux.cfg file at all.
If you can point me in the direction of the HOWTO that you read, I'll try to get
No it does not say I have to modify the boot disk. It says
a) If there is not enough space on the floppy, I have to. There is not. So I
b) If I want to make it easy for myself, I can make ks the default.
Why are we discusing this? Do you think that is the problem? I do not. To me
this is a minor detail, I understand what I've done to the syslinux.cfg and why.
Unless you can convince me that modifying syslinux.cfg on a bootdisk makes
anaconda die, because it is supposed to have a specific size, ot whatever, (and
that would be a stupid thing to do with a clear text configuration file) then I
do _not_ believe this is a problem.
I included that file for completeness.
Anyway, I'll solve my own problem, I didn't expect any help here. I just send
that bug report because the error screen specifically said you would appreciate
it, ok? Thank you very much for you time.
I think what you need is to put an "=" sign between the "--location" and the
"mbr" in the kickstart file, so that the line says:
The docs are not very clear about what needs '=' signs and what doesn't
I asked about what you modified on the boot disk because we get a fair number of
bug reports that are caused by people doing customized tasks (such as modifying
the comps file and replacing the packages that we shipped with newer ones).
Sometimes they do things wrong, which creates a bug that looks like it's the
installer's fault. I was just trying to figure out the level of modification
that you had done. From your first post, it is not clear that you modified only
the syslinux.cfg file, which is a minor change. I was wondering if you had
modified the loader itself to have the location of the kickstart file hard coded
(which would be a major change).
I found the error. It was in the kickstart config file. I needed a "part /
--size 1000 --grow" or something like that - mkkickstart had only made a "part"
entry for the swap partition.
So - the installer crashes in the above situation. I've solved my problem. Up to
you if you want the installer to have more meaningful behaviour in the above
sitution, and if maybe mkkickstart should be fixed to include the root partition
and not only the swap partition.