On Fri, 2 Aug 2002, Taylor, ForrestX wrote:
> Carl Riches wrote:
> > Well, it seems to default to "cdrom", but it fails in the same way for
> > both "cdrom" and "nfs".
> >
> > Carl
>
> Where did you put your ks.cfg file?
> What are you booting from (floppy or cdrom)?
> What errors does [ctrl]+[alt]+F3, F4, etc. show?
>
I'm kickstarting from a floppy, using this install screen command:
linux ks=floppy
I believe that this problem of kickstart ignoring the kickstart file is
caused when the install media aren't found. I've been able to duplicate
the problem under "cdrom" and "nfs" install methods, for each of the
boot.img and bootnet.img disks. In fact, it happens before the
installation program starts up the shell prompt on vt2. You should be
able to duplicate this as well:
- with the boot.img disk, kickstart but don't put the CDs in the drive
- with the boot.img disk, kickstart and use the "cdrom" installation
method
- with the boot.img disk, kickstart and use the "nfs" installation
method and take the kickstart client out of the server's exports file
My underlying problem is that the bootnet.img is not mounting the NFS
export of the installation CDs. This used to Just Work. Now vt3 has
repeated messages of:
mount failed, retrying after 3 second sleep
For each one of these messages, there is a matching RPC log message on the
server (a portmap dump() call). I originally thought that the NFS problem
was separate from the ignored ks.cfg file problem. It's not--the former
causes the latter.
Could this be an NFS v2 versus NFS v3 problem? Can I force v2 or v3? If
so, how?
Thanks,
Carl
