[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Problems with Network-Based Install

Hi Philip,

Thanks for the hints. The initrd & vmlinuz were pulled from the same distro CDs as the install being done. The NFS server is a Windows box (I know I know) but I can check the logs for anything interesting. I will also try ksdevice=link in the morning and report back. Thanks again. 

-----Original Message-----
From: Philip Rowlands <phr doc ic ac uk>
Date: Thu, 10 Mar 2005 23:21:47 
To:Discussion list about Kickstart <kickstart-list redhat com>
Subject: Re: Problems with Network-Based Install

On Thu, 10 Mar 2005, Kurt Bishop wrote:

>We have been having some problems getting a Kickstart install to be
>100% automated.  We are PXE booting the system which then fetches the
>Kickstart file from a remote NFS share.  However, the system we're
>installing to has 2 network devices and the installer always pops up
>and asks us which device it should use before fetching the Kickstart
>file. Manually selecting a device moves the install along just fine but
>we need this to be automated.  I have tried adding the following:
>network ksdevice=eth0 ip=dhcp
>to the kernel parameters but the installer simply hangs at the
>"running /sbin/loader" line.

What about ksdevice=link ? Other things to consider:
- Do you have consistent parts of anaconda, i.e. do the initrd and
vmlinuz files come from the same minor distro (RHEL3U4) as the
NFS-shared second stage?
- Does syslog (/var/log/messages) on the NFS server say anything useful?


Kickstart-list mailing list
Kickstart-list redhat com

Kurt Bishop
Systems Analyst/Consultant

Net Direct Inc.
12-564 Weber Street North
Waterloo, ON N2L 5C6
Ph: 519-883-1172 x5104
Fx: 519-883-8533

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]