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

RE: Kickstart problem



See below...

>  -----Original Message-----
>  From: redhat-list-bounces redhat com 
>  [mailto:redhat-list-bounces redhat com] On Behalf Of Ezra Taylor
>  Sent: Monday, January 12, 2009 1:10 PM
>  To: General Red Hat Linux discussion list
>  Subject: Re: Kickstart problem
>  
>  Hello all:
>                     I followed all of your suggestions and 
>  I'm still not able
>  to download the kickstart file.  Just to let you know, while 
>  receiving the
>  above messages, the keyboard is disabled.  I'm not even able 
>  to modify the
>  the line that shows the the location of the ks.cfg file.  
>  Also, I tried
>  downloading the file using http.  Using http still produces the error
>  message "Error downloading kickstart file".  I'm starting to 
>  think this is a
>  network issue.
>  
>  On Fri, Jan 9, 2009 at 4:44 PM, Ahmed Sharif 
>  <ahmed sharif bd gmail com>wrote:
>  
>  > Ezra Taylor,
>  >
>  > Check the file permission of ks.cfg. Most probably you have already
>  > did that, but it came to my mind first. You should also run the
>  > "ksvalidator" command each time you modify the kickstart file. The
>  > syntax is,
>  >
>  > #ksvalidator <kickstart-file-name>
>  >
>  > Please inform us about your result.
>  >
>  > Thanks and Regards,
>  >
>  > Ahmed Sharif
>  >
>  >
>  > On 1/9/09, chaim rieger gmail com <chaim rieger gmail com> wrote:
>  > > Try removing all white lines in ks.cfg
>  > >
>  > > Other than that nothing jumped out at me, will look some 
>  more though
>  > >
>  > >
>  > > Sent via BlackBerry from T-Mobile
>  > >
>  > > -----Original Message-----
>  > > From: "Ezra Taylor" <ezra taylor gmail com>
>  > >
>  > > Date: Thu, 8 Jan 2009 22:19:40
>  > > To: <chaim rieger gmail com>; General Red Hat Linux discussion
>  > > list<redhat-list redhat com>
>  > > Subject: Re: Kickstart problem
>  > >
>  > >
>  > > Thanks for your quick response.
>  > > *
>  > >
>  > > ks.cfg*
>  > >
>  > > text
>  > > install
>  > >
>  > > nfs --server=192.168.0.2 --dir=/opt/apps/install/centos/5-2/i386
>  > >
>  > > lang en_US.UTF-8
>  > > keyboard us
>  > > mouse none
>  > > timezone America/New_York
>  > > rootpw --iscrypted $1$UD.SyMgz$PFb6a0vs2lCJxWWtEO.sE1
>  > > network --device eth0 --bootproto dhcp --noipv6
>  > >
>  > > firewall --disabled
>  > > selinux --disabled
>  > > authconfig --enableshadow --enablemd5
>  > >
>  > > bootloader --location=mbr
>  > > clearpart --all
>  > > zerombr yes
>  > >
>  > > part /boot --fstype ext3 --asprimary --size 500
>  > > part swap --fstype swap --asprimary --size 2048
>  > > part /    --fstype reiserfs --asprimary --size 4096 --grow
>  > >
>  > > skipx
>  > >
>  > > %packages
>  > > @base
>  > > @development-libs
>  > > @editors
>  > >
>  > 
>  _____________________________________________________________
>  __________________
>  > >
>  > >
>  > > /tftpboot/boot/pxelinux.cfg/default
>  > >
>  > > default a
>  > > timeout 500
>  > > prompt 1
>  > > display pxelinux.msg
>  > >
>  > >
>  > >
>  > > label a #Centos 5.2 - 32 bit(reiserfs)
>  > >         kernel vmlinuz-centos-5.2-32bit
>  > >         append text ksdevice=eth0 
>  eth0_ethtool="autoneg=off speed=100
>  > > duplex=half" console=tty0 load_ramdisk=1 ramdisk_size=8192
>  > > initrd=initrd.img  ks=nfs:192.168.0.2:
>  > > /opt/apps/install/centos/5-2/i386/ks/ks.cfg
>  > >
>  > >
>  > 
>  _____________________________________________________________
>  _____________________________________________________________
>  ___________
>  > >
>  > > */etc/exports*
>  > >
>  > > /opt/apps/install       *(ro,no_root_squash)
>  > >
>  > >
>  > 
>  _____________________________________________________________
>  ____________________________________________
>  > >
>  > > */etc/dhcpd.conf*
>  > >
>  > >
>  > > ddns-update-style interim;
>  > > next-server 192.168.0.2;
>  > >
>  > >         subnet 192.168.0.0       netmask 255.255.255.0 {
>  > > #       option routers           192.168.0.1;
>  > >         option subnet-mask       255.255.255.0;
>  > >         option broadcast-address 192.168.0.255;
>  > >         range                    192.168.0.3 192.168.0.130;
>  > >         default-lease-time       51000;
>  > >         max-lease-time           51000;
>  > >         filename                 "/boot/pxelinux.0";
>  > >         allow booting;
>  > >         allow bootp;
>  > >
>  > >
>  > > }
>  > >
>  > >
>  > > On Thu, Jan 8, 2009 at 9:47 PM, <chaim rieger gmail com> wrote:
>  > >
>  > >> Please post ks.cfg
>  > >>
>  > >>
>  > >> Sent via BlackBerry from T-Mobile
>  > >>
>  > >> -----Original Message-----
>  > >> From: "Ezra Taylor" <ezra taylor gmail com>
>  > >>
>  > >> Date: Thu, 8 Jan 2009 21:42:37
>  > >> To: <redhat-list redhat com>
>  > >> Subject: Kickstart problem
>  > >>
>  > >>
>  > >> Hello all:
>  > >>
>  > >>                 I'm getting the error below when trying 
>  to kickstart my
>  > >> box.  The kickstart server is running RHEL 5.2 and the 
>  client is 5.2.
>  > >> Any
>  > >> suggestions?
>  > >>
>  > >>
>  > >> Error downloading kickstart file
>  > >>
>  > >>
>  > >> --
>  > >> Ezra Taylor
>  > >> --
>  > >> redhat-list mailing list
>  > >> unsubscribe 
>  mailto:redhat-list-request redhat com?subject=unsubscribe
>  > >> https://www.redhat.com/mailman/listinfo/redhat-list
>  > >> --
>  > >> redhat-list mailing list
>  > >> unsubscribe 
>  mailto:redhat-list-request redhat com?subject=unsubscribe
>  > >> https://www.redhat.com/mailman/listinfo/redhat-list
>  > > --
>  > > Ezra Taylor
>  > --
>  > redhat-list mailing list
>  > unsubscribe 
>  mailto:redhat-list-request redhat com?subject=unsubscribe
>  > https://www.redhat.com/mailman/listinfo/redhat-list
>  -- 
>  Ezra Taylor
>  -- 
>  redhat-list mailing list
>  unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
>  https://www.redhat.com/mailman/listinfo/redhat-list
>  

Several questions:
	- Are you sure that the OS is seeing eth0 as the interface you
expect?  I know that on RHEL4 and RHEL5 certain hardware is probed PCI
slots first and then motherboard so the first onboard interface is
something other than eth0.

	- Can you see the server connecting to the dhcp server to get
it's network information?

	- Are the NFS exports set up correctly to allow your server to
mount and read the directory?

Maarten Broekman
Email: maarten broekman fmr com

 



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