From Joe_Wulf at yahoo.com Tue Oct 2 14:10:14 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Tue, 2 Oct 2007 10:10:14 -0400 Subject: kickstart builds one system but not another Message-ID: Ok, here is a weird one. I've got two physical systems running VMware workstation 6, the first is a 64bit desktop with 2 Quad-core CPUs and 4GB of system memory with the only thing running on it is VMware. The other is a Dell XPS laptop, dual-core Pentium (T2600) with 3GB of RAM. I can build an RHEL AS4u5 x32, via kickstart on this one. I go back to the kickstart server (running Fedora 7) modify the MAC address in DHCP (then restart it) and then link the modified MAC address for the tftpboot/linux_install/pxeconfig.cfg to the new one. These correspond to the MAC address on the VM on the 64bit system. The initial tftpboot goes fine, but when it comes time to NFS mount the kickstart directory, it simply fails over to doing a completely interactive install. Any clues why the better box can't seem to 'get it up'? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com (410) 772-7969 office (410) 772-7967 fax (443) 801-5597 personal cell -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: From lfarkas at bppiac.hu Tue Oct 9 09:58:02 2007 From: lfarkas at bppiac.hu (Farkas Levente) Date: Tue, 09 Oct 2007 11:58:02 +0200 Subject: anaconda kernel parameter to load module Message-ID: <470B50AA.6050301@bppiac.hu> hi, how can i add kernel parameters to anaconda to load a module? in a normal booting initrd contains an init script so i can modify it load a given module (after i put it into the initrd). but in case of installer the initrd contains a binary init so i can't modify it. in this case how can i define kernel param (eg: through isolinux.cfg) to load additional modules? suppose i've got an xfs partition on which the installer reside and i use lilo to load the kernel and initrd, but after that the kernel can't read anything from the partition since it's not load xfs. is there any way to load kernel modules in this case trough kernel params (ie. append)? thanks. -- Levente "Si vis pacem para bellum!" From steven.hajducko at digitalinsight.com Thu Oct 11 22:46:33 2007 From: steven.hajducko at digitalinsight.com (Hajducko, Steven) Date: Thu, 11 Oct 2007 15:46:33 -0700 Subject: RHEL5 kickstart overwrites USB Message-ID: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Hi, So we're running into a strange issue where a kickstart from a USB/CDROM combo on an HP DL385 G5 system is actually installing and reformatting the USB stick. We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: linux ks=hd:sda1:/hostname.cfg The installation goes fine and our packages are installed, but upon reboot and examining the USB stick, it has been reformatted to ext3 FS and contains : stha3155 at ghost:/media/usb$ ls config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 Upon reboot of the system, it crashes with a bunch of OPCODE errors. The relevant part of our kickstart looks like this ( we don't do anything tricky in our packages or post install, just touch a few config files.. ) install cdrom lang en_US langsupport --default=en_US en_US keyboard us skipx text ignoredisk --drives=sda1,sdb1,sdc1 network --device eth0 --bootproto static --ip 192.168.27.17 --netmask 255.255.255.0 --hostname hostname.domain.com network --device eth1 --onboot no rootpw --iscrypted ##### firewall --disabled authconfig --enableshadow --enablemd5 timezone America/Los_Angeles selinux --disabled zerombr yes bootloader --location=mbr --append="rhgb quiet" reboot clearpart --all part /boot --fstype ext3 --size=128 --asprimary part swap --size=6912 --asprimary part pv.01 --size=100 --grow volgroup rootvg pv.01 logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv %packages Tried putting the 'ignoredisk' option in order to ignore the sda1 disk that the USB shows up as, but no luck. As a side note, the disks on the HP show up as /dev/cciss/c0d0. Any input would be appreciated. Thanks. -- sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From Chip.Shabazian at bankofamerica.com Thu Oct 11 22:52:40 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Thu, 11 Oct 2007 15:52:40 -0700 Subject: RHEL5 kickstart overwrites USB In-Reply-To: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: Are you sure the system is seeing the USB as sd(a,b,c)1? Add a sleep to your %pre, get a shell, and take a look. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Hajducko, Steven Sent: Thursday, October 11, 2007 3:47 PM To: kickstart-list at redhat.com Subject: RHEL5 kickstart overwrites USB Hi, So we're running into a strange issue where a kickstart from a USB/CDROM combo on an HP DL385 G5 system is actually installing and reformatting the USB stick. We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: linux ks=hd:sda1:/hostname.cfg The installation goes fine and our packages are installed, but upon reboot and examining the USB stick, it has been reformatted to ext3 FS and contains : stha3155 at ghost:/media/usb$ ls config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 Upon reboot of the system, it crashes with a bunch of OPCODE errors. The relevant part of our kickstart looks like this ( we don't do anything tricky in our packages or post install, just touch a few config files.. ) install cdrom lang en_US langsupport --default=en_US en_US keyboard us skipx text ignoredisk --drives=sda1,sdb1,sdc1 network --device eth0 --bootproto static --ip 192.168.27.17 --netmask 255.255.255.0 --hostname hostname.domain.com network --device eth1 --onboot no rootpw --iscrypted ##### firewall --disabled authconfig --enableshadow --enablemd5 timezone America/Los_Angeles selinux --disabled zerombr yes bootloader --location=mbr --append="rhgb quiet" reboot clearpart --all part /boot --fstype ext3 --size=128 --asprimary part swap --size=6912 --asprimary part pv.01 --size=100 --grow volgroup rootvg pv.01 logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv %packages Tried putting the 'ignoredisk' option in order to ignore the sda1 disk that the USB shows up as, but no luck. As a side note, the disks on the HP show up as /dev/cciss/c0d0. Any input would be appreciated. Thanks. -- sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhoffman at ip-solutions.net Thu Oct 11 22:53:59 2007 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Thu, 11 Oct 2007 18:53:59 -0400 Subject: RHEL5 kickstart overwrites USB In-Reply-To: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: <470EA987.3060505@ip-solutions.net> hmm, it looks like it's sticking /boot on the usb drive. If you switch to console f2 can you find out what device the usb drive is during install? My guess is that the usb/cd combo has something like /dev/sda1 == cdrom /dev/sda2 == rest of disk and so when you say clearpart --all it repartitions the drive and then the /boot partition is placed on there. I've not used the ignoredisk option before so I don't know if it's not working. HTH, Harry Hajducko, Steven wrote: > Hi, > > So we're running into a strange issue where a kickstart from a USB/CDROM > combo on an HP DL385 G5 system is actually installing and reformatting > the USB stick. > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: > > linux ks=hd:sda1:/hostname.cfg > > The installation goes fine and our packages are installed, but upon > reboot and examining the USB stick, it has been reformatted to ext3 FS > and contains : > > stha3155 at ghost:/media/usb$ ls > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > The relevant part of our kickstart looks like this ( we don't do > anything tricky in our packages or post install, just touch a few config > files.. ) > > install > cdrom > lang en_US > langsupport --default=en_US en_US > keyboard us > skipx > text > ignoredisk --drives=sda1,sdb1,sdc1 > network --device eth0 --bootproto static --ip 192.168.27.17 --netmask > 255.255.255.0 --hostname hostname.domain.com > network --device eth1 --onboot no > rootpw --iscrypted ##### > firewall --disabled > authconfig --enableshadow --enablemd5 > timezone America/Los_Angeles > selinux --disabled > zerombr yes > bootloader --location=mbr --append="rhgb quiet" > reboot > clearpart --all > part /boot --fstype ext3 --size=128 --asprimary > part swap --size=6912 --asprimary > part pv.01 --size=100 --grow > volgroup rootvg pv.01 > logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv > logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv > logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv > logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv > logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv > logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv > logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv > > %packages > > Tried putting the 'ignoredisk' option in order to ignore the sda1 disk > that the USB shows up as, but no luck. As a side note, the disks on the > HP show up as /dev/cciss/c0d0. > > Any input would be appreciated. > > Thanks. > > -- > sh > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From jason at rampaginggeek.com Thu Oct 11 22:55:13 2007 From: jason at rampaginggeek.com (Jason Edgecombe) Date: Thu, 11 Oct 2007 18:55:13 -0400 Subject: RHEL5 kickstart overwrites USB In-Reply-To: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: <470EA9D1.5080902@rampaginggeek.com> Hi There, I use the following snippet in my kickstart files: ====== %include /tmp/part-include %pre #----- partitioning logic below-------------- # pick the first drive that is not removable and is over MINSIZE DIR="/sys/block" # minimum size of hard drive needed specified in GIGABYTES MINSIZE=23 ROOTDRIVE="" # /sys/block/*/size is in 512 byte chunks for DEV in sda sdb hda hdb; do if [ -d $DIR/$DEV ]; then REMOVABLE=`cat $DIR/$DEV/removable` if (( $REMOVABLE == 0 )); then echo $DEV SIZE=`cat $DIR/$DEV/size` GB=$(($SIZE/2**21)) if [ $GB -gt $MINSIZE ]; then echo "$(($SIZE/2**21))" if [ -z $ROOTDRIVE ]; then ROOTDRIVE=$DEV fi fi fi fi done echo "ROOTDRIVE=$ROOTDRIVE" cat << EOF >> /tmp/part-include bootloader --location=mbr --driveorder=$ROOTDRIVE clearpart --all --drives=$ROOTDRIVE --initlabel part /boot --fstype ext3 --size=300 --asprimary --ondisk=$ROOTDRIVE part /tmp --fstype ext3 --size=5000 --ondisk=$ROOTDRIVE part swap --size=2000 --asprimary --ondisk=$ROOTDRIVE part /usr/vice/cache --fstype ext3 --size=1500 --ondisk=$ROOTDRIVE part /home --fstype ext3 --size=100 --grow --ondisk=$ROOTDRIVE part / --fstype ext3 --size=20000 --grow --maxsize=30000 --asprimary --ondisk=$ROOTDRIVE EOF ======== The script in %pre avoids removable drives such as USB. I hope that helps. Jason Hajducko, Steven wrote: > > Hi, > > So we're running into a strange issue where a kickstart from a > USB/CDROM combo on an HP DL385 G5 system is actually installing and > reformatting the USB stick. > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD and > run: > > linux ks=hd:sda1:/hostname.cfg > > The installation goes fine and our packages are installed, but upon > reboot and examining the USB stick, it has been reformatted to ext3 FS > and contains : > > stha3155 at ghost:/media/usb$ ls > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > The relevant part of our kickstart looks like this ( we don't do > anything tricky in our packages or post install, just touch a few > config files.. ) > > install > cdrom > lang en_US > langsupport --default=en_US en_US > keyboard us > skipx > text > ignoredisk --drives=sda1,sdb1,sdc1 > network --device eth0 --bootproto static --ip 192.168.27.17 --netmask > 255.255.255.0 --hostname hostname.domain.com > network --device eth1 --onboot no > rootpw --iscrypted ##### > firewall --disabled > authconfig --enableshadow --enablemd5 > timezone America/Los_Angeles > selinux --disabled > zerombr yes > bootloader --location=mbr --append="rhgb quiet" > reboot > clearpart --all > part /boot --fstype ext3 --size=128 --asprimary > part swap --size=6912 --asprimary > part pv.01 --size=100 --grow > volgroup rootvg pv.01 > logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv > logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv > logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv > logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv > logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv > logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv > logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 > --name=locallv > > %packages > > Tried putting the 'ignoredisk' option in order to ignore the sda1 disk > that the USB shows up as, but no luck. As a side note, the disks on > the HP show up as /dev/cciss/c0d0. > > Any input would be appreciated. > > Thanks. > > -- > sh > > ------------------------------------------------------------------------ > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From steven.hajducko at digitalinsight.com Thu Oct 11 22:56:55 2007 From: steven.hajducko at digitalinsight.com (Hajducko, Steven) Date: Thu, 11 Oct 2007 15:56:55 -0700 Subject: RHEL5 kickstart overwrites USB In-Reply-To: References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E91@WLVEXM01.corp.ad.diginsite.com> Yeah, we're sure. The only thing on the USB drive is the kickstart file and you can see the kickstart successfully locate and pick up the configuration file off the USB stick. I'll add the sleep to the %pre and see if there is anything else I can watch but I'm positive that anaconda is picking up the configuration file from sda1. -- sh ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Thursday, October 11, 2007 3:53 PM To: Discussion list about Kickstart Subject: RE: RHEL5 kickstart overwrites USB Are you sure the system is seeing the USB as sd(a,b,c)1? Add a sleep to your %pre, get a shell, and take a look. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Hajducko, Steven Sent: Thursday, October 11, 2007 3:47 PM To: kickstart-list at redhat.com Subject: RHEL5 kickstart overwrites USB Hi, So we're running into a strange issue where a kickstart from a USB/CDROM combo on an HP DL385 G5 system is actually installing and reformatting the USB stick. We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: linux ks=hd:sda1:/hostname.cfg The installation goes fine and our packages are installed, but upon reboot and examining the USB stick, it has been reformatted to ext3 FS and contains : stha3155 at ghost:/media/usb$ ls config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 Upon reboot of the system, it crashes with a bunch of OPCODE errors. The relevant part of our kickstart looks like this ( we don't do anything tricky in our packages or post install, just touch a few config files.. ) install cdrom lang en_US langsupport --default=en_US en_US keyboard us skipx text ignoredisk --drives=sda1,sdb1,sdc1 network --device eth0 --bootproto static --ip 192.168.27.17 --netmask 255.255.255.0 --hostname hostname.domain.com network --device eth1 --onboot no rootpw --iscrypted ##### firewall --disabled authconfig --enableshadow --enablemd5 timezone America/Los_Angeles selinux --disabled zerombr yes bootloader --location=mbr --append="rhgb quiet" reboot clearpart --all part /boot --fstype ext3 --size=128 --asprimary part swap --size=6912 --asprimary part pv.01 --size=100 --grow volgroup rootvg pv.01 logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv %packages Tried putting the 'ignoredisk' option in order to ignore the sda1 disk that the USB shows up as, but no luck. As a side note, the disks on the HP show up as /dev/cciss/c0d0. Any input would be appreciated. Thanks. -- sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From steven.hajducko at digitalinsight.com Thu Oct 11 23:54:44 2007 From: steven.hajducko at digitalinsight.com (Hajducko, Steven) Date: Thu, 11 Oct 2007 16:54:44 -0700 Subject: RHEL5 kickstart overwrites USB In-Reply-To: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E91@WLVEXM01.corp.ad.diginsite.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> <21F8C5D33731F44BB9DCC396A12F9F2105AC9E91@WLVEXM01.corp.ad.diginsite.com> Message-ID: <21F8C5D33731F44BB9DCC396A12F9F2105AC9EAE@WLVEXM01.corp.ad.diginsite.com> Excuse the spam, this is just bizarre. Here's the snippet of the anaconda.log showing that on first pass, anaconda cannot find sda1:/gremlin1b.cfg, but once I hit enter again, without changing the path, it finds it successfully. 18:49:25 INFO : modules to insert bnx2 cciss 18:49:25 INFO : loaded bnx2 from /modules/modules.cgz 18:49:25 INFO : loaded cciss from /modules/modules.cgz 18:49:25 INFO : going to rmmod usb-storage 18:49:25 INFO : inserted /tmp/bnx2.ko 18:49:26 INFO : inserted /tmp/cciss.ko 18:49:26 INFO : modules to insert usb-storage 18:49:26 INFO : loaded usb-storage from /modules/modules.cgz 18:49:27 INFO : inserted /tmp/usb-storage.ko 18:49:27 INFO : removed usb-storage from modprobe.conf 18:49:27 INFO : load module set done 18:49:34 INFO : load module set done 18:49:34 INFO : getting kickstart file 18:49:34 INFO : getting kickstart file from harddrive 18:49:34 INFO : Loading ks from device sda1 on path /gremlin1b.cfg 18:49:34 INFO : getFileFromBlockDevice(sda1, /gremlin1b.cfg) 18:49:34 ERROR : failed to mount /dev/sda1: No such device or address 18:49:40 INFO : getting kickstart file from harddrive 18:49:40 INFO : Loading ks from device sda1 on path /gremlin1b.cfg 18:49:40 INFO : getFileFromBlockDevice(sda1, /gremlin1b.cfg) 18:49:40 INFO : Searching for file on path /tmp/mnt//gremlin1b.cfg 18:49:40 INFO : file copied to /tmp/ks.cfg 18:49:40 INFO : setting up kickstart 18:49:40 INFO : kickstartFromCD -- sh ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Hajducko, Steven Sent: Thursday, October 11, 2007 3:57 PM To: Discussion list about Kickstart Subject: RE: RHEL5 kickstart overwrites USB Yeah, we're sure. The only thing on the USB drive is the kickstart file and you can see the kickstart successfully locate and pick up the configuration file off the USB stick. I'll add the sleep to the %pre and see if there is anything else I can watch but I'm positive that anaconda is picking up the configuration file from sda1. -- sh ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Shabazian, Chip Sent: Thursday, October 11, 2007 3:53 PM To: Discussion list about Kickstart Subject: RE: RHEL5 kickstart overwrites USB Are you sure the system is seeing the USB as sd(a,b,c)1? Add a sleep to your %pre, get a shell, and take a look. ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Hajducko, Steven Sent: Thursday, October 11, 2007 3:47 PM To: kickstart-list at redhat.com Subject: RHEL5 kickstart overwrites USB Hi, So we're running into a strange issue where a kickstart from a USB/CDROM combo on an HP DL385 G5 system is actually installing and reformatting the USB stick. We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: linux ks=hd:sda1:/hostname.cfg The installation goes fine and our packages are installed, but upon reboot and examining the USB stick, it has been reformatted to ext3 FS and contains : stha3155 at ghost:/media/usb$ ls config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 Upon reboot of the system, it crashes with a bunch of OPCODE errors. The relevant part of our kickstart looks like this ( we don't do anything tricky in our packages or post install, just touch a few config files.. ) install cdrom lang en_US langsupport --default=en_US en_US keyboard us skipx text ignoredisk --drives=sda1,sdb1,sdc1 network --device eth0 --bootproto static --ip 192.168.27.17 --netmask 255.255.255.0 --hostname hostname.domain.com network --device eth1 --onboot no rootpw --iscrypted ##### firewall --disabled authconfig --enableshadow --enablemd5 timezone America/Los_Angeles selinux --disabled zerombr yes bootloader --location=mbr --append="rhgb quiet" reboot clearpart --all part /boot --fstype ext3 --size=128 --asprimary part swap --size=6912 --asprimary part pv.01 --size=100 --grow volgroup rootvg pv.01 logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv %packages Tried putting the 'ignoredisk' option in order to ignore the sda1 disk that the USB shows up as, but no luck. As a side note, the disks on the HP show up as /dev/cciss/c0d0. Any input would be appreciated. Thanks. -- sh -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Fri Oct 12 03:35:22 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 12 Oct 2007 11:35:22 +0800 Subject: RHEL5 kickstart overwrites USB In-Reply-To: References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: <470EEB7A.50405@herakles.homelinux.org> Shabazian, Chip wrote: > Are you sure the system is seeing the USB as sd(a,b,c)1? Add a sleep to > your %pre, get a shell, and take a look. I prefer /bin/sh -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From Pablo.Iranzo at redhat.com Fri Oct 12 12:42:03 2007 From: Pablo.Iranzo at redhat.com (=?UTF-8?Q?Pablo_Iranzo_G=C3=B3mez?=) Date: Fri, 12 Oct 2007 14:42:03 +0200 (CEST) Subject: RHEL5 kickstart overwrites USB In-Reply-To: <470EA9D1.5080902@rampaginggeek.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> <470EA9D1.5080902@rampaginggeek.com> Message-ID: What I use is: #Obtain first drive from system and number of them set $(list-harddrives) let numd=$#/2 # Number of drives d1=$1 # Device for first drive S1=$2 # Size of first drive (and so on $3,$4, etc) So you can process them after that Regards Pablo On Thu, 11 Oct 2007, Jason Edgecombe wrote: > Hi There, > > I use the following snippet in my kickstart files: > ====== > %include /tmp/part-include > > %pre > #----- partitioning logic below-------------- > # pick the first drive that is not removable and is over MINSIZE > DIR="/sys/block" > > # minimum size of hard drive needed specified in GIGABYTES > MINSIZE=23 > > > ROOTDRIVE="" > > # /sys/block/*/size is in 512 byte chunks > > for DEV in sda sdb hda hdb; do > if [ -d $DIR/$DEV ]; then > REMOVABLE=`cat $DIR/$DEV/removable` > if (( $REMOVABLE == 0 )); then > echo $DEV > SIZE=`cat $DIR/$DEV/size` > GB=$(($SIZE/2**21)) > if [ $GB -gt $MINSIZE ]; then > echo "$(($SIZE/2**21))" > if [ -z $ROOTDRIVE ]; then > ROOTDRIVE=$DEV > fi > fi > fi > fi > done > > echo "ROOTDRIVE=$ROOTDRIVE" > > cat << EOF >> /tmp/part-include > bootloader --location=mbr --driveorder=$ROOTDRIVE > clearpart --all --drives=$ROOTDRIVE --initlabel > part /boot --fstype ext3 --size=300 --asprimary --ondisk=$ROOTDRIVE > part /tmp --fstype ext3 --size=5000 --ondisk=$ROOTDRIVE > part swap --size=2000 --asprimary --ondisk=$ROOTDRIVE > part /usr/vice/cache --fstype ext3 --size=1500 --ondisk=$ROOTDRIVE > part /home --fstype ext3 --size=100 --grow --ondisk=$ROOTDRIVE > part / --fstype ext3 --size=20000 --grow --maxsize=30000 --asprimary > --ondisk=$ROOTDRIVE > EOF > > ======== > The script in %pre avoids removable drives such as USB. > > I hope that helps. > > Jason > > Hajducko, Steven wrote: > > > > Hi, > > > > So we're running into a strange issue where a kickstart from a > > USB/CDROM combo on an HP DL385 G5 system is actually installing and > > reformatting the USB stick. > > > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD and > > run: > > > > linux ks=hd:sda1:/hostname.cfg > > > > The installation goes fine and our packages are installed, but upon > > reboot and examining the USB stick, it has been reformatted to ext3 FS > > and contains : > > > > stha3155 at ghost:/media/usb$ ls > > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 > > > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > > > The relevant part of our kickstart looks like this ( we don't do > > anything tricky in our packages or post install, just touch a few > > config files.. ) > > > > install > > cdrom > > lang en_US > > langsupport --default=en_US en_US > > keyboard us > > skipx > > text > > ignoredisk --drives=sda1,sdb1,sdc1 > > network --device eth0 --bootproto static --ip 192.168.27.17 --netmask > > 255.255.255.0 --hostname hostname.domain.com > > network --device eth1 --onboot no > > rootpw --iscrypted ##### > > firewall --disabled > > authconfig --enableshadow --enablemd5 > > timezone America/Los_Angeles > > selinux --disabled > > zerombr yes > > bootloader --location=mbr --append="rhgb quiet" > > reboot > > clearpart --all > > part /boot --fstype ext3 --size=128 --asprimary > > part swap --size=6912 --asprimary > > part pv.01 --size=100 --grow > > volgroup rootvg pv.01 > > logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv > > logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv > > logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv > > logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv > > logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv > > logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv > > logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 > > --name=locallv > > > > %packages > > > > Tried putting the 'ignoredisk' option in order to ignore the sda1 disk > > that the USB shows up as, but no luck. As a side note, the disks on > > the HP show up as /dev/cciss/c0d0. > > > > Any input would be appreciated. > > > > Thanks. > > > > -- > > sh > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From mups.cp at gmail.com Fri Oct 12 14:07:21 2007 From: mups.cp at gmail.com (mups.cp) Date: Fri, 12 Oct 2007 11:07:21 -0300 Subject: RHEL5 kickstart overwrites USB In-Reply-To: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: Your USB was formated due to the clearpart --all This instruct the kicstart to clean all the partitions that are available on your system. I think that you could avoid this by instructing clearpart to only clear your hardrive with clearpart --drives=sdX. The kickstart is recognizing all your hard disks as part of your system. The docs from redhat warns about part: "All partitions created are formatted as part of the installation process unless --noformat and --onpart are used. " You could use part with --onpart to specify where you want you partition be installed. If you don't, the system will try by himself and chose your USB because it was clean. On 10/11/07, Hajducko, Steven wrote: > > > Hi, > > So we're running into a strange issue where a kickstart from a USB/CDROM > combo on an HP DL385 G5 system is actually installing and reformatting the > USB stick. > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: > > linux ks=hd:sda1:/hostname.cfg > > The installation goes fine and our packages are installed, but upon reboot > and examining the USB stick, it has been reformatted to ext3 FS and contains > : > > stha3155 at ghost:/media/usb$ ls > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > The relevant part of our kickstart looks like this ( we don't do anything > tricky in our packages or post install, just touch a few config files.. ) > > install > cdrom > lang en_US > langsupport --default=en_US en_US > keyboard us > skipx > text > ignoredisk --drives=sda1,sdb1,sdc1 > network --device eth0 --bootproto static --ip 192.168.27.17 --netmask > 255.255.255.0 --hostname hostname.domain.com > network --device eth1 --onboot no > rootpw --iscrypted ##### > firewall --disabled > authconfig --enableshadow --enablemd5 > timezone America/Los_Angeles > selinux --disabled > zerombr yes > bootloader --location=mbr --append="rhgb quiet" > reboot > clearpart --all > part /boot --fstype ext3 --size=128 --asprimary > part swap --size=6912 --asprimary > part pv.01 --size=100 --grow > volgroup rootvg pv.01 > logvol / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv > logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv > logvol /var --fstype ext3 --vgname=rootvg --size=1024 --name=varlv > logvol /opt --fstype ext3 --vgname=rootvg --size=2048 --name=optlv > logvol /home --fstype ext3 --vgname=rootvg --size=2048 --name=homelv > logvol /usr --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv > logvol /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv > > %packages > > Tried putting the 'ignoredisk' option in order to ignore the sda1 disk that > the USB shows up as, but no luck. As a side note, the disks on the HP show > up as /dev/cciss/c0d0. > > Any input would be appreciated. > > Thanks. > > -- > sh > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From steven.hajducko at digitalinsight.com Fri Oct 12 17:32:02 2007 From: steven.hajducko at digitalinsight.com (Hajducko, Steven) Date: Fri, 12 Oct 2007 10:32:02 -0700 Subject: RHEL5 kickstart overwrites USB In-Reply-To: References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com> Message-ID: <21F8C5D33731F44BB9DCC396A12F9F2105AC9F81@WLVEXM01.corp.ad.diginsite.com> Thanks, I was trying to get around the clearpart with the 'ignoredisk' statement, but I think I have the wrong format ( specified sda1 rather than sda ). If that doesn't work, I'll use the clearpart and part --ondrive statements. However, this still doesn't explain why anaconda doesn't see the USB device the first time, but once I hit enter after it complains, it locates it fine. -- sh -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of mups.cp Sent: Friday, October 12, 2007 7:07 AM To: Discussion list about Kickstart Subject: Re: RHEL5 kickstart overwrites USB Your USB was formated due to the clearpart --all This instruct the kicstart to clean all the partitions that are available on your system. I think that you could avoid this by instructing clearpart to only clear your hardrive with clearpart --drives=sdX. The kickstart is recognizing all your hard disks as part of your system. The docs from redhat warns about part: "All partitions created are formatted as part of the installation process unless --noformat and --onpart are used. " You could use part with --onpart to specify where you want you partition be installed. If you don't, the system will try by himself and chose your USB because it was clean. On 10/11/07, Hajducko, Steven wrote: > > > Hi, > > So we're running into a strange issue where a kickstart from a > USB/CDROM combo on an HP DL385 G5 system is actually installing and > reformatting the USB stick. > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD and run: > > linux ks=hd:sda1:/hostname.cfg > > The installation goes fine and our packages are installed, but upon > reboot and examining the USB stick, it has been reformatted to ext3 FS > and contains > : > > stha3155 at ghost:/media/usb$ ls > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 vmlinuz-2.6.18-8.el5 > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > The relevant part of our kickstart looks like this ( we don't do > anything tricky in our packages or post install, just touch a few > config files.. ) > > install > cdrom > lang en_US > langsupport --default=en_US en_US > keyboard us > skipx > text > ignoredisk --drives=sda1,sdb1,sdc1 > network --device eth0 --bootproto static --ip 192.168.27.17 --netmask > 255.255.255.0 --hostname hostname.domain.com network --device eth1 > --onboot no rootpw --iscrypted ##### firewall --disabled authconfig > --enableshadow --enablemd5 timezone America/Los_Angeles selinux > --disabled zerombr yes bootloader --location=mbr --append="rhgb quiet" > reboot > clearpart --all > part /boot --fstype ext3 --size=128 --asprimary part swap --size=6912 > --asprimary part pv.01 --size=100 --grow volgroup rootvg pv.01 logvol > / --fstype ext3 --vgname=rootvg --size=512 --name=rootlv logvol /tmp > --fstype ext3 --vgname=rootvg --size=1024 --name=tmplv logvol /var > --fstype ext3 --vgname=rootvg --size=1024 --name=varlv logvol /opt > --fstype ext3 --vgname=rootvg --size=2048 --name=optlv logvol /home > --fstype ext3 --vgname=rootvg --size=2048 --name=homelv logvol /usr > --fstype ext3 --vgname=rootvg --size=2048 --name=usrlv logvol > /usr/local --fstype ext3 --vgname=rootvg --size=2048 --name=locallv > > %packages > > Tried putting the 'ignoredisk' option in order to ignore the sda1 disk > that the USB shows up as, but no luck. As a side note, the disks on > the HP show up as /dev/cciss/c0d0. > > Any input would be appreciated. > > Thanks. > > -- > sh > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From steven.hajducko at digitalinsight.com Fri Oct 12 21:35:02 2007 From: steven.hajducko at digitalinsight.com (Hajducko, Steven) Date: Fri, 12 Oct 2007 14:35:02 -0700 Subject: RHEL5 kickstart overwrites USB In-Reply-To: References: <21F8C5D33731F44BB9DCC396A12F9F2105AC9E84@WLVEXM01.corp.ad.diginsite.com><470EA9D1.5080902@rampaginggeek.com> Message-ID: <21F8C5D33731F44BB9DCC396A12F9F2105ACA00F@WLVEXM01.corp.ad.diginsite.com> Thanks for all the suggestions, they're much appreciated and we'll start using these right away. I've opened a ticket with RH, in the meantime, to figure out why the USB drive is ignored on the first pass, but after clicking OK, is found. Thanks again for everyone's help and suggestions. -- sh -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Pablo Iranzo G?mez Sent: Friday, October 12, 2007 5:42 AM To: Discussion list about Kickstart Subject: Re: RHEL5 kickstart overwrites USB What I use is: #Obtain first drive from system and number of them set $(list-harddrives) let numd=$#/2 # Number of drives d1=$1 # Device for first drive S1=$2 # Size of first drive (and so on $3,$4, etc) So you can process them after that Regards Pablo On Thu, 11 Oct 2007, Jason Edgecombe wrote: > Hi There, > > I use the following snippet in my kickstart files: > ====== > %include /tmp/part-include > > %pre > #----- partitioning logic below-------------- # pick the first drive > that is not removable and is over MINSIZE DIR="/sys/block" > > # minimum size of hard drive needed specified in GIGABYTES > MINSIZE=23 > > > ROOTDRIVE="" > > # /sys/block/*/size is in 512 byte chunks > > for DEV in sda sdb hda hdb; do > if [ -d $DIR/$DEV ]; then > REMOVABLE=`cat $DIR/$DEV/removable` > if (( $REMOVABLE == 0 )); then > echo $DEV > SIZE=`cat $DIR/$DEV/size` > GB=$(($SIZE/2**21)) > if [ $GB -gt $MINSIZE ]; then > echo "$(($SIZE/2**21))" > if [ -z $ROOTDRIVE ]; then > ROOTDRIVE=$DEV > fi > fi > fi > fi > done > > echo "ROOTDRIVE=$ROOTDRIVE" > > cat << EOF >> /tmp/part-include > bootloader --location=mbr --driveorder=$ROOTDRIVE clearpart --all > --drives=$ROOTDRIVE --initlabel part /boot --fstype ext3 --size=300 > --asprimary --ondisk=$ROOTDRIVE part /tmp --fstype ext3 --size=5000 > --ondisk=$ROOTDRIVE part swap --size=2000 --asprimary > --ondisk=$ROOTDRIVE part /usr/vice/cache --fstype ext3 --size=1500 > --ondisk=$ROOTDRIVE part /home --fstype ext3 --size=100 --grow > --ondisk=$ROOTDRIVE part / --fstype ext3 --size=20000 --grow > --maxsize=30000 --asprimary --ondisk=$ROOTDRIVE EOF > > ======== > The script in %pre avoids removable drives such as USB. > > I hope that helps. > > Jason > > Hajducko, Steven wrote: > > > > Hi, > > > > So we're running into a strange issue where a kickstart from a > > USB/CDROM combo on an HP DL385 G5 system is actually installing and > > reformatting the USB stick. > > > > We place the kickstart file on the USB drive, drop in a RHEL5 DVD > > and > > run: > > > > linux ks=hd:sda1:/hostname.cfg > > > > The installation goes fine and our packages are installed, but upon > > reboot and examining the USB stick, it has been reformatted to ext3 > > FS and contains : > > > > stha3155 at ghost:/media/usb$ ls > > config-2.6.18-8.el5 grub initrd-2.6.18-8.el5.img lost+found > > symvers-2.6.18-8.el5.gz System.map-2.6.18-8.el5 > > vmlinuz-2.6.18-8.el5 > > > > Upon reboot of the system, it crashes with a bunch of OPCODE errors. > > > > The relevant part of our kickstart looks like this ( we don't do > > anything tricky in our packages or post install, just touch a few > > config files.. ) > > > > install > > cdrom > > lang en_US > > langsupport --default=en_US en_US > > keyboard us > > skipx > > text > > ignoredisk --drives=sda1,sdb1,sdc1 > > network --device eth0 --bootproto static --ip 192.168.27.17 > > --netmask 255.255.255.0 --hostname hostname.domain.com network > > --device eth1 --onboot no rootpw --iscrypted ##### firewall > > --disabled authconfig --enableshadow --enablemd5 timezone > > America/Los_Angeles selinux --disabled zerombr yes bootloader > > --location=mbr --append="rhgb quiet" > > reboot > > clearpart --all > > part /boot --fstype ext3 --size=128 --asprimary part swap > > --size=6912 --asprimary part pv.01 --size=100 --grow volgroup rootvg > > pv.01 logvol / --fstype ext3 --vgname=rootvg --size=512 > > --name=rootlv logvol /tmp --fstype ext3 --vgname=rootvg --size=1024 > > --name=tmplv logvol /var --fstype ext3 --vgname=rootvg --size=1024 > > --name=varlv logvol /opt --fstype ext3 --vgname=rootvg --size=2048 > > --name=optlv logvol /home --fstype ext3 --vgname=rootvg --size=2048 > > --name=homelv logvol /usr --fstype ext3 --vgname=rootvg --size=2048 > > --name=usrlv logvol /usr/local --fstype ext3 --vgname=rootvg > > --size=2048 --name=locallv > > > > %packages > > > > Tried putting the 'ignoredisk' option in order to ignore the sda1 > > disk that the USB shows up as, but no luck. As a side note, the > > disks on the HP show up as /dev/cciss/c0d0. > > > > Any input would be appreciated. > > > > Thanks. > > > > -- > > sh > > > > -------------------------------------------------------------------- > > ---- > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From dmc.fedora at filteredperception.org Sat Oct 13 20:23:29 2007 From: dmc.fedora at filteredperception.org (Douglas McClendon) Date: Sat, 13 Oct 2007 15:23:29 -0500 Subject: proxy with http install method? Message-ID: <47112941.1070600@filteredperception.org> This has probably been asked before, but googling for "kickstart http proxy" didn't give me much help (except for ubuntu). Can an http proxy be used for and specified by a kickstart install? (fedora 8?) If it isn't a known possibility, has the migration to the yum backend enabled some way to get this to work, perhaps with some mucking in %pre? -dmc From Joe_Wulf at yahoo.com Sun Oct 14 23:55:21 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Sun, 14 Oct 2007 19:55:21 -0400 Subject: How to totally exclude IPv6... Message-ID: During kickstart of new systems the vmlinuz and/or initrd.img waste a lot of time looking for IPv6 connectivity, routers and ethernet ports. Is there a method during the tftpboot/PXELinux phase that can bypass this? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: From Joe_Wulf at yahoo.com Sun Oct 14 23:58:53 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Sun, 14 Oct 2007 19:58:53 -0400 Subject: NFS booting problem Message-ID: I've got an on again, off again problem where I can initiate a kickstart for RHEL5 (32 or 64 bit), as well as for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS config cannot be found. Then, after numerous reboots to troubleshoot the problem, poof, the NFS mount is found and some systems get built. Nothing changed. Even reboots of the kickstart server, the Linksys router and the Mac Pro (with WinXP and VMware 6 installed) don't change that many restarts have to happen before it will somehow, magically start building. A most confusing problem and one that I need insight, advice and questions from you all on what to check so I can solve it. All help is appreciated! R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: From Colin.Coe at woodside.com.au Mon Oct 15 00:10:13 2007 From: Colin.Coe at woodside.com.au (Coe, Colin C. (Unix Engineer)) Date: Mon, 15 Oct 2007 08:10:13 +0800 Subject: How to totally exclude IPv6... In-Reply-To: Message-ID: say carbon default carbon prompt 1 timeout 100 label carbon kernel ks-rhel-x86_64-server-5/vmlinuz append initrd=ks-rhel-x86_64-server-5/initrd.img ks=http://somewhere/kickstart/ks/org/1x33bf2048269014bdb91b23c8c6411c37/ label/carbon load_ramdisk=1 ksdevice=link noipv6 ________________________________ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe_Wulf Sent: Monday, 15 October 2007 7:55 AM To: kickstart-list at redhat.com Subject: How to totally exclude IPv6... During kickstart of new systems the vmlinuz and/or initrd.img waste a lot of time looking for IPv6 connectivity, routers and ethernet ports. Is there a method during the tftpboot/PXELinux phase that can bypass this? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: ProSync_SignatureItem_Blue.jpg URL: From debian at herakles.homelinux.org Mon Oct 15 00:40:37 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 15 Oct 2007 08:40:37 +0800 Subject: NFS booting problem In-Reply-To: References: Message-ID: <4712B705.8030700@herakles.homelinux.org> Joe_Wulf wrote: > I've got an on again, off again problem where I can initiate a kickstart for > RHEL5 (32 or 64 bit), as well as > for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS config cannot > be found. Then, > after numerous reboots to troubleshoot the problem, poof, the NFS mount is found > and some systems > get built. Nothing changed. Even reboots of the kickstart server, the Linksys > router and the Mac Pro > (with WinXP and VMware 6 installed) don't change that many restarts have to > happen before it will > somehow, magically start building. > > A most confusing problem and one that I need insight, advice and questions from > you all on what to > check so I can solve it. All help is appreciated! It's some years since I did an NFS install. http, in my experience, works well. Do you have some reason (other than setup) not to do it too? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From Joe_Wulf at yahoo.com Mon Oct 15 02:19:13 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Sun, 14 Oct 2007 22:19:13 -0400 Subject: NFS booting problem In-Reply-To: <4712B705.8030700@herakles.homelinux.org> References: <4712B705.8030700@herakles.homelinux.org> Message-ID: John, Thank you for writing. At this point NFS is all I know. I have 'gotten' the concept of kickstarting only recently, much less learned and applied it and gotten it to work. A friend/co-worker helped me to get the NFS working. I've set it up, the same way for two different locations. One of the kickstart servers is FC5 the other is Fedora 7. I've pretty carefully checked my configuration stuff. Made sure DHCP, pxeconfig, tftp and NFS were set up. I've done matched up comparisons between the config files for both locations. At the FC5 site I can fully build repeatedly the same end systems (RHEL AS4u5 32/64 bit) and (RHEL5 32/64 bit) while only changing the nuts and bolts in the %post sections. I'm applying the same logic and applying the same kinds of things at the Fedora 7 site (even with the same IP networks/address space) and find that the at the Fedora 7 site, something is 'wrong'. About 1 time in 25 (or more) the system will build without anything changing; the rest of the time it is not NFS mounting for the KS.cfg parts. So, its failing at the same place. On the VC3 screen there is syslog-like output, of the following (retyped): 20:08:21 INFO : doing kickstart... setting it up 20:08:22 INFO : DHCPv4 interface configuration succeeded. 20:08:23 WARNING : reverse name lookup failed 20:08:24 INFO : url is 192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg 20:08:25 INFO : file location: nfs://192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg 20:08:26 ERROR : failed to mount nfs source I've put the 'seconds' in increments to uniquely talk about each line, as needed. Before ":21" I'm frustrated with the IPv6 that it wastes time trying to mount, but hopefully someone will give me a way to prevent that. At ":23" I do not understand that reverse name lookup failure. DNS has been setup, established, configured and not changed. For these boots, it seems that the errors only occasionally go away without any change to DNS or a restart of the named daemon. And when I don't get this error, the systems NFS mount and build fully. At the Fedora 7 site, the Fedora 7 system is a Pentium 4 with 512 MB of RAM 726 GB of disk storage with a 100 bit ethernet card. The network connections are through a Linksys RT41-BU router. The kickstart'ees are virtual machines on a MAC Pro with dual quad-core CPUs, 4GB RAM and 520 GB of internal storage. The MAC Pro has XP64bit installed and is current with all the Micro$loth updates, no firewall, no anti-virus and no anti-spam enabled. Manually built systems of the above mentioned guests flawlessly install time after time, I can get them repeatedly successfully mount filesystems via NFS (and successfully export them too) There is also a Dell XPS 1710 laptop within the same network, also every attempt to build 32 bit systems succeed. I even changed the 'mac' address of a problem one not building to identify the one from the MAC Pro over to the Dell XPS, and it built every time. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield Sent: Sunday, October 14, 2007 20:41 To: Discussion list about Kickstart Subject: Re: NFS booting problem Joe_Wulf wrote: > I've got an on again, off again problem where I can initiate a > kickstart for > RHEL5 (32 or 64 bit), as well as > for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS > config cannot be found. Then, after numerous reboots to troubleshoot > the problem, poof, the NFS mount is found and some systems get built. > Nothing changed. Even reboots of the kickstart server, the Linksys > router and the Mac Pro (with WinXP and VMware 6 installed) don't > change that many restarts have to happen before it will somehow, > magically start building. > > A most confusing problem and one that I need insight, advice and > questions from you all on what to check so I can solve it. All help > is appreciated! It's some years since I did an NFS install. http, in my experience, works well. Do you have some reason (other than setup) not to do it too? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From Joe_Wulf at yahoo.com Mon Oct 15 03:53:38 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Sun, 14 Oct 2007 23:53:38 -0400 Subject: How to totally exclude IPv6... In-Reply-To: References: Message-ID: That worked very well! Thank you! Now, if I could only get the REST of my system to build normally. Hmmmm....... R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com _____ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Coe, Colin C. (Unix Engineer) Sent: Sunday, October 14, 2007 20:10 To: Discussion list about Kickstart Subject: RE: How to totally exclude IPv6... say carbon default carbon prompt 1 timeout 100 label carbon kernel ks-rhel-x86_64-server-5/vmlinuz append initrd=ks-rhel-x86_64-server-5/initrd.img ks=http://somewhere/kickstart/ks/org/1x33bf2048269014bdb91b23c8c6411c37/label/car bon load_ramdisk=1 ksdevice=link noipv6 _____ From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Joe_Wulf Sent: Monday, 15 October 2007 7:55 AM To: kickstart-list at redhat.com Subject: How to totally exclude IPv6... During kickstart of new systems the vmlinuz and/or initrd.img waste a lot of time looking for IPv6 connectivity, routers and ethernet ports. Is there a method during the tftpboot/PXELinux phase that can bypass this? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ProSync_SignatureItem_Blue.jpg Type: image/jpeg Size: 3249 bytes Desc: not available URL: From debian at herakles.homelinux.org Mon Oct 15 09:28:10 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 15 Oct 2007 17:28:10 +0800 Subject: NFS booting problem In-Reply-To: References: <4712B705.8030700@herakles.homelinux.org> Message-ID: <471332AA.9@herakles.homelinux.org> Joe_Wulf wrote: > John, > > Thank you for writing. > > At this point NFS is all I know. I have 'gotten' the concept of kickstarting > only recently, much less learned and applied it and gotten it to work. A > friend/co-worker helped me to get the NFS working. I've set it up, the same > way for two different locations. One of the kickstart servers is FC5 the > other is Fedora 7. I've pretty carefully checked my configuration stuff. > Made sure DHCP, pxeconfig, tftp and NFS were set up. I've done matched up > comparisons between the config files for both locations. At the FC5 site > I can fully build repeatedly the same end systems (RHEL AS4u5 32/64 bit) > and (RHEL5 32/64 bit) while only changing the nuts and bolts in the %post > sections. I'm applying the same logic and applying the same kinds of > things at the Fedora 7 site (even with the same IP networks/address space) > and find that the at the Fedora 7 site, something is 'wrong'. About 1 > time in 25 (or more) the system will build without anything changing; the > rest of the time it is not NFS mounting for the KS.cfg parts. So, its > failing at the same place. What's in /var/log/messages? To use http, you need a web server. I use virtual hosts, but that's not essential. With a decent Internet connexion, one can also install via http directly off the 'net. It runs well with a caching proxy, and bot Squid and Apache can fill that role superbly. An advantage of this technique is that one only downloads those files actually needed: there's no need for several Gbytes of data. Once it's cached, installs go at local LAN speeds. If using Squid, then I suggest a transparent proxy - it simplifies installs (one does not need to configure the proxy) and applies to ordinary folk using Firefox, Seamonkey etc as well. I use this virtual host definition: [root at ns ~]# cat /etc/httpd/conf/vhosts.d/RHEL.conf ServerAdmin webmaster at computerdatasafe.com.au DocumentRoot /var/local/mirrors/linux/RHEL ServerName RHEL.demo.lan ServerAlias RHEL.demo.room ServerAlias RHEL Alias /RHEL/ "/var/local/mirrors/linux/RHEL/" Alias /Fedora/ "/var/local/mirrors/linux/Fedora/" Alias /Specifix/ "/var/local/mirrors/linux/Specifix/os/" Alias /ScientificLinux/ "/var/local/mirrors/linux/ScientificLinux/" Alias /CentOS/ "/var/local/mirrors/linux/CentOS/" ScriptAlias /ks/ "/var/local/mirrors/linux/ks/" ErrorLog /var/log/httpd/RHEL-error_log CustomLog /var/log/httpd/RHEL-access_log combined AllowOverride None Options +FollowSymLinks +Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 [root at ns ~]# If you don't want the virtual host stuff, just remove the virtualhost things fore and aft. I have another vhost which I used to install FC2 through a modem with time-limited sessions; I'll post it on provocation:-) > > On the VC3 screen there is syslog-like output, of the following (retyped): > 20:08:21 INFO : doing kickstart... setting it up > 20:08:22 INFO : DHCPv4 interface configuration succeeded. > 20:08:23 WARNING : reverse name lookup failed > 20:08:24 INFO : url is 192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg > 20:08:25 INFO : file location: nfs://192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg > 20:08:26 ERROR : failed to mount nfs source Like you, I found nfs a little temperamental. In contrast, httpp works every time, and also it writes a nice log so one can see what files are used. > > I've put the 'seconds' in increments to uniquely talk about each line, as > needed. Before ":21" I'm frustrated with the IPv6 that it wastes time trying > to mount, but hopefully someone will give me a way to prevent that. I think it's "noipv6" > > At ":23" I do not understand that reverse name lookup failure. DNS has been > setup, established, configured and not changed. For these boots, it seems > that the errors only occasionally go away without any change to DNS or a > restart of the named daemon. And when I don't get this error, the systems > NFS mount and build fully. It's trying to convert your install target's IP address to a host name. It plans to use this as the name of the system. > > At the Fedora 7 site, the Fedora 7 system is a Pentium 4 with 512 MB of RAM > 726 GB of disk storage with a 100 bit ethernet card. The network connections > are through a Linksys RT41-BU router. The kickstart'ees are virtual machines > on a MAC Pro with dual quad-core CPUs, 4GB RAM and 520 GB of internal storage. > The MAC Pro has XP64bit installed and is current with all the Micro$loth > updates, no firewall, no anti-virus and no anti-spam enabled. Manually built > systems of the above mentioned guests flawlessly install time after time, I > can get them repeatedly successfully mount filesystems via NFS (and > successfully export them too) Xen? Virtual PC? VMWare? Whichever you're using, have you tried one of the others? I'm not sure of the current situation, but it used to be the case that Anaconda's nfs tools weren't as good as the installed ones. Also, I think it's using pump for its dhcp client. > > There is also a Dell XPS 1710 laptop within the same network, also every attempt > to build 32 bit systems succeed. I even changed the 'mac' address of a problem > one not building to identify the one from the MAC Pro over to the Dell XPS, and > it built every time. > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield > Sent: Sunday, October 14, 2007 20:41 > To: Discussion list about Kickstart > Subject: Re: NFS booting problem > > Joe_Wulf wrote: >> I've got an on again, off again problem where I can initiate a >> kickstart for >> RHEL5 (32 or 64 bit), as well as >> for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS >> config cannot be found. Then, after numerous reboots to troubleshoot >> the problem, poof, the NFS mount is found and some systems get built. >> Nothing changed. Even reboots of the kickstart server, the Linksys >> router and the Mac Pro (with WinXP and VMware 6 installed) don't >> change that many restarts have to happen before it will somehow, >> magically start building. >> >> A most confusing problem and one that I need insight, advice and >> questions from you all on what to check so I can solve it. All help >> is appreciated! > > It's some years since I did an NFS install. http, in my experience, works well. > Do you have some reason (other than setup) not to do it too? > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From jason at rampaginggeek.com Mon Oct 15 12:57:20 2007 From: jason at rampaginggeek.com (Jason Edgecombe) Date: Mon, 15 Oct 2007 08:57:20 -0400 Subject: NFS booting problem In-Reply-To: <471332AA.9@herakles.homelinux.org> References: <4712B705.8030700@herakles.homelinux.org> <471332AA.9@herakles.homelinux.org> Message-ID: <471363B0.6070003@rampaginggeek.com> Your method is cool, but a little advanced. Try this: Just copy your NFS tree to a web-viewable directory on a web server and change the one line in your kickstart file to use http instead of nfs. Jason John Summerfield wrote: > Joe_Wulf wrote: >> John, >> >> Thank you for writing. >> >> At this point NFS is all I know. I have 'gotten' the concept of >> kickstarting >> only recently, much less learned and applied it and gotten it to >> work. A >> friend/co-worker helped me to get the NFS working. I've set it up, >> the same >> way for two different locations. One of the kickstart servers is FC5 >> the >> other is Fedora 7. I've pretty carefully checked my configuration >> stuff. >> Made sure DHCP, pxeconfig, tftp and NFS were set up. I've done >> matched up >> comparisons between the config files for both locations. At the FC5 >> site >> I can fully build repeatedly the same end systems (RHEL AS4u5 32/64 bit) >> and (RHEL5 32/64 bit) while only changing the nuts and bolts in the >> %post >> sections. I'm applying the same logic and applying the same kinds of >> things at the Fedora 7 site (even with the same IP networks/address >> space) >> and find that the at the Fedora 7 site, something is 'wrong'. About 1 >> time in 25 (or more) the system will build without anything changing; >> the >> rest of the time it is not NFS mounting for the KS.cfg parts. So, its >> failing at the same place. > > What's in /var/log/messages? > > > > To use http, you need a web server. I use virtual hosts, but that's > not essential. > > With a decent Internet connexion, one can also install via http > directly off the 'net. It runs well with a caching proxy, and bot > Squid and Apache can fill that role superbly. > > An advantage of this technique is that one only downloads those files > actually needed: there's no need for several Gbytes of data. > > Once it's cached, installs go at local LAN speeds. > > If using Squid, then I suggest a transparent proxy - it simplifies > installs (one does not need to configure the proxy) and applies to > ordinary folk using Firefox, Seamonkey etc as well. > > I use this virtual host definition: > [root at ns ~]# cat /etc/httpd/conf/vhosts.d/RHEL.conf > > ServerAdmin webmaster at computerdatasafe.com.au > DocumentRoot /var/local/mirrors/linux/RHEL > ServerName RHEL.demo.lan > ServerAlias RHEL.demo.room > ServerAlias RHEL > Alias /RHEL/ "/var/local/mirrors/linux/RHEL/" > Alias /Fedora/ > "/var/local/mirrors/linux/Fedora/" > Alias /Specifix/ > "/var/local/mirrors/linux/Specifix/os/" > Alias /ScientificLinux/ > "/var/local/mirrors/linux/ScientificLinux/" > Alias /CentOS/ > "/var/local/mirrors/linux/CentOS/" > ScriptAlias /ks/ "/var/local/mirrors/linux/ks/" > ErrorLog /var/log/httpd/RHEL-error_log > CustomLog /var/log/httpd/RHEL-access_log combined > > AllowOverride None > Options +FollowSymLinks +Indexes > Order allow,deny > Allow from 192.168 > > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > > > [root at ns ~]# > > If you don't want the virtual host stuff, just remove the virtualhost > things fore and aft. > > I have another vhost which I used to install FC2 through a modem with > time-limited sessions; I'll post it on provocation:-) > > > > > > >> >> On the VC3 screen there is syslog-like output, of the following >> (retyped): >> 20:08:21 INFO : doing kickstart... setting it up >> 20:08:22 INFO : DHCPv4 interface configuration succeeded. >> 20:08:23 WARNING : reverse name lookup failed >> 20:08:24 INFO : url is 192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg >> 20:08:25 INFO : file location: >> nfs://192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg >> 20:08:26 ERROR : failed to mount nfs source > > Like you, I found nfs a little temperamental. In contrast, httpp works > every time, and also it writes a nice log so one can see what files > are used. > > >> >> I've put the 'seconds' in increments to uniquely talk about each >> line, as >> needed. Before ":21" I'm frustrated with the IPv6 that it wastes >> time trying >> to mount, but hopefully someone will give me a way to prevent that. > > I think it's "noipv6" > >> >> At ":23" I do not understand that reverse name lookup failure. DNS >> has been >> setup, established, configured and not changed. For these boots, it >> seems >> that the errors only occasionally go away without any change to DNS or a >> restart of the named daemon. And when I don't get this error, the >> systems >> NFS mount and build fully. > It's trying to convert your install target's IP address to a host > name. It plans to use this as the name of the system. > >> >> At the Fedora 7 site, the Fedora 7 system is a Pentium 4 with 512 MB >> of RAM >> 726 GB of disk storage with a 100 bit ethernet card. The network >> connections >> are through a Linksys RT41-BU router. The kickstart'ees are virtual >> machines >> on a MAC Pro with dual quad-core CPUs, 4GB RAM and 520 GB of internal >> storage. >> The MAC Pro has XP64bit installed and is current with all the Micro$loth >> updates, no firewall, no anti-virus and no anti-spam enabled. >> Manually built >> systems of the above mentioned guests flawlessly install time after >> time, I >> can get them repeatedly successfully mount filesystems via NFS (and >> successfully export them too) > > Xen? > Virtual PC? > VMWare? > Whichever you're using, have you tried one of the others? > > > > I'm not sure of the current situation, but it used to be the case that > Anaconda's nfs tools weren't as good as the installed ones. Also, I > think it's using pump for its dhcp client. > >> >> There is also a Dell XPS 1710 laptop within the same network, also >> every attempt >> to build 32 bit systems succeed. I even changed the 'mac' address of >> a problem >> one not building to identify the one from the MAC Pro over to the >> Dell XPS, and >> it built every time. >> >> R, >> -Joe Wulf, CISSP, USN(RET) >> Senior IA Engineer >> ProSync Technology Group, LLC >> www.prosync.com >> >> -----Original Message----- >> From: kickstart-list-bounces at redhat.com >> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield >> Sent: Sunday, October 14, 2007 20:41 >> To: Discussion list about Kickstart >> Subject: Re: NFS booting problem >> >> Joe_Wulf wrote: >>> I've got an on again, off again problem where I can initiate a >>> kickstart for >>> RHEL5 (32 or 64 bit), as well as >>> for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS >>> config cannot be found. Then, after numerous reboots to >>> troubleshoot the problem, poof, the NFS mount is found and some >>> systems get built. Nothing changed. Even reboots of the kickstart >>> server, the Linksys router and the Mac Pro (with WinXP and VMware 6 >>> installed) don't change that many restarts have to happen before it >>> will somehow, magically start building. >>> >>> A most confusing problem and one that I need insight, advice and >>> questions from you all on what to check so I can solve it. All help >>> is appreciated! >> >> It's some years since I did an NFS install. http, in my experience, >> works well. >> Do you have some reason (other than setup) not to do it too? >> > > From Joe_Wulf at yahoo.com Mon Oct 15 15:39:05 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Mon, 15 Oct 2007 11:39:05 -0400 Subject: NFS booting problem In-Reply-To: <471332AA.9@herakles.homelinux.org> References: <4712B705.8030700@herakles.homelinux.org> <471332AA.9@herakles.homelinux.org> Message-ID: John, thank you. Jason Edgecombe also mentioned to just simply copy the NFS tree to a web-viewable directory on a web server. I've stayed away from the http/squid/apache method/version of installations as I don't know anything about apache or squid, securing them, etc... nor did I feel I had the time to spare to learn how to set THAT up just to get all my other stuff working. My task/project is to develop a straightforward method to install a baseline (stable standard) version of RHEL AS4 and RHEL5 that is usable across the enterprise (potentially thousands of machines) that is the same, and has been well secured/hardened. I'm pretty close to the final stages of that effort. The kickstart method has generally been working at a lab site, but not so well at the near- production site. Yes, the "noipv6" in the pxeconfig worked. Thank you. I've pretty closely watched (tail -f) the /var/log/messages and only see the DHCP and tftp related messages. No errors reported. This is the first time I've found NFS temperamental. But not sure how to further test this or 'fix' it, much less how to troubleshoot it. VMware Workstation v6.0+ is what is being used today. Haven't had the spare time to set up and try any of the others. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield Sent: Monday, October 15, 2007 05:28 To: Discussion list about Kickstart Subject: Re: NFS booting problem Joe_Wulf wrote: > John, > > Thank you for writing. > > At this point NFS is all I know. I have 'gotten' the concept of > kickstarting only recently, much less learned and applied it and > gotten it to work. A friend/co-worker helped me to get the NFS > working. I've set it up, the same way for two different locations. > One of the kickstart servers is FC5 the other is Fedora 7. I've pretty carefully checked my configuration stuff. > Made sure DHCP, pxeconfig, tftp and NFS were set up. I've done > matched up comparisons between the config files for both locations. > At the FC5 site I can fully build repeatedly the same end systems > (RHEL AS4u5 32/64 bit) and (RHEL5 32/64 bit) while only changing the > nuts and bolts in the %post sections. I'm applying the same logic and > applying the same kinds of things at the Fedora 7 site (even with the > same IP networks/address space) and find that the at the Fedora 7 > site, something is 'wrong'. About 1 time in 25 (or more) the system > will build without anything changing; the rest of the time it is not > NFS mounting for the KS.cfg parts. So, its failing at the same place. What's in /var/log/messages? To use http, you need a web server. I use virtual hosts, but that's not essential. With a decent Internet connexion, one can also install via http directly off the 'net. It runs well with a caching proxy, and bot Squid and Apache can fill that role superbly. An advantage of this technique is that one only downloads those files actually needed: there's no need for several Gbytes of data. Once it's cached, installs go at local LAN speeds. If using Squid, then I suggest a transparent proxy - it simplifies installs (one does not need to configure the proxy) and applies to ordinary folk using Firefox, Seamonkey etc as well. I use this virtual host definition: [root at ns ~]# cat /etc/httpd/conf/vhosts.d/RHEL.conf ServerAdmin webmaster at computerdatasafe.com.au DocumentRoot /var/local/mirrors/linux/RHEL ServerName RHEL.demo.lan ServerAlias RHEL.demo.room ServerAlias RHEL Alias /RHEL/ "/var/local/mirrors/linux/RHEL/" Alias /Fedora/ "/var/local/mirrors/linux/Fedora/" Alias /Specifix/ "/var/local/mirrors/linux/Specifix/os/" Alias /ScientificLinux/ "/var/local/mirrors/linux/ScientificLinux/" Alias /CentOS/ "/var/local/mirrors/linux/CentOS/" ScriptAlias /ks/ "/var/local/mirrors/linux/ks/" ErrorLog /var/log/httpd/RHEL-error_log CustomLog /var/log/httpd/RHEL-access_log combined AllowOverride None Options +FollowSymLinks +Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 AllowOverride None Options FollowSymLinks Indexes Order allow,deny Allow from 192.168 [root at ns ~]# If you don't want the virtual host stuff, just remove the virtualhost things fore and aft. I have another vhost which I used to install FC2 through a modem with time-limited sessions; I'll post it on provocation:-) > > On the VC3 screen there is syslog-like output, of the following (retyped): > 20:08:21 INFO : doing kickstart... setting it up > 20:08:22 INFO : DHCPv4 interface configuration succeeded. > 20:08:23 WARNING : reverse name lookup failed > 20:08:24 INFO : url is 192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg > 20:08:25 INFO : file location: nfs://192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg > 20:08:26 ERROR : failed to mount nfs source Like you, I found nfs a little temperamental. In contrast, httpp works every time, and also it writes a nice log so one can see what files are used. > > I've put the 'seconds' in increments to uniquely talk about each line, as > needed. Before ":21" I'm frustrated with the IPv6 that it wastes time trying > to mount, but hopefully someone will give me a way to prevent that. I think it's "noipv6" > > At ":23" I do not understand that reverse name lookup failure. DNS has been > setup, established, configured and not changed. For these boots, it seems > that the errors only occasionally go away without any change to DNS or a > restart of the named daemon. And when I don't get this error, the systems > NFS mount and build fully. It's trying to convert your install target's IP address to a host name. It plans to use this as the name of the system. > > At the Fedora 7 site, the Fedora 7 system is a Pentium 4 with 512 MB of RAM > 726 GB of disk storage with a 100 bit ethernet card. The network connections > are through a Linksys RT41-BU router. The kickstart'ees are virtual machines > on a MAC Pro with dual quad-core CPUs, 4GB RAM and 520 GB of internal storage. > The MAC Pro has XP64bit installed and is current with all the Micro$loth > updates, no firewall, no anti-virus and no anti-spam enabled. Manually built > systems of the above mentioned guests flawlessly install time after time, I > can get them repeatedly successfully mount filesystems via NFS (and > successfully export them too) Xen? Virtual PC? VMWare? Whichever you're using, have you tried one of the others? I'm not sure of the current situation, but it used to be the case that Anaconda's nfs tools weren't as good as the installed ones. Also, I think it's using pump for its dhcp client. > > There is also a Dell XPS 1710 laptop within the same network, also every attempt > to build 32 bit systems succeed. I even changed the 'mac' address of a problem > one not building to identify the one from the MAC Pro over to the Dell XPS, and > it built every time. > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield > Sent: Sunday, October 14, 2007 20:41 > To: Discussion list about Kickstart > Subject: Re: NFS booting problem > > Joe_Wulf wrote: >> I've got an on again, off again problem where I can initiate a >> kickstart for >> RHEL5 (32 or 64 bit), as well as >> for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS >> config cannot be found. Then, after numerous reboots to troubleshoot >> the problem, poof, the NFS mount is found and some systems get built. >> Nothing changed. Even reboots of the kickstart server, the Linksys >> router and the Mac Pro (with WinXP and VMware 6 installed) don't >> change that many restarts have to happen before it will somehow, >> magically start building. >> >> A most confusing problem and one that I need insight, advice and >> questions from you all on what to check so I can solve it. All help >> is appreciated! > > It's some years since I did an NFS install. http, in my experience, works well. > Do you have some reason (other than setup) not to do it too? > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From debian at herakles.homelinux.org Tue Oct 16 01:02:47 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 16 Oct 2007 09:02:47 +0800 Subject: NFS booting problem In-Reply-To: References: <4712B705.8030700@herakles.homelinux.org> <471332AA.9@herakles.homelinux.org> Message-ID: <47140DB7.4050903@herakles.homelinux.org> Joe_Wulf wrote: > John, thank you. Jason Edgecombe also mentioned to just simply copy the NFS tree > to a > web-viewable directory on a web server. I've stayed away from the > http/squid/apache > method/version of installations as I don't know anything about apache or squid, > securing > them, etc... nor did I feel I had the time to spare to learn how to set THAT up > just to > get all my other stuff working. My task/project is to develop a straightforward > method The allow/deny lines secure apache. If it's only listening on your LAN, it's secured from outside (assuming your firewall's okay). Mine's on 192.168.9.4 and there's no way you can get to it. Squid doesn't need much, mainly make sure you cache big files. Its config file is well commented, about as good as I've seen. You may need to loosen Squid' security a little:-) That said, it too is on 192.168.9.4 and you can't reach that either. > to install a baseline (stable standard) version of RHEL AS4 and RHEL5 that is > usable > across the enterprise (potentially thousands of machines) that is the same, and > has been > well secured/hardened. I'm pretty close to the final stages of that effort. The > kickstart method has generally been working at a lab site, but not so well at the > near- > production site. if you're going to be looking after that much kit you need to get your geek skills up really soon. Configuring Apache and Squid (and your MTA) are all part of what you need. btw Kickstart off DVD would be pretty cool too. "Here's your new machine. Boot this DVD." Your %pre would need to ensure they didn't do it twice (or after /home is populated or something). > > Yes, the "noipv6" in the pxeconfig worked. Thank you. > > I've pretty closely watched (tail -f) the /var/log/messages and only see the DHCP > and tftp > related messages. No errors reported. > > This is the first time I've found NFS temperamental. But not sure how to further > test > this or 'fix' it, much less how to troubleshoot it. > > VMware Workstation v6.0+ is what is being used today. Haven't had the spare time > to > set up and try any of the others. > > > > > R, > -Joe Wulf, CISSP, USN(RET) > Senior IA Engineer > ProSync Technology Group, LLC > www.prosync.com > > > > -----Original Message----- > From: kickstart-list-bounces at redhat.com > [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield > Sent: Monday, October 15, 2007 05:28 > To: Discussion list about Kickstart > Subject: Re: NFS booting problem > > Joe_Wulf wrote: >> John, >> >> Thank you for writing. >> >> At this point NFS is all I know. I have 'gotten' the concept of >> kickstarting only recently, much less learned and applied it and >> gotten it to work. A friend/co-worker helped me to get the NFS >> working. I've set it up, the same way for two different locations. >> One of the kickstart servers is FC5 the other is Fedora 7. I've pretty > carefully checked my configuration stuff. >> Made sure DHCP, pxeconfig, tftp and NFS were set up. I've done >> matched up comparisons between the config files for both locations. >> At the FC5 site I can fully build repeatedly the same end systems >> (RHEL AS4u5 32/64 bit) and (RHEL5 32/64 bit) while only changing the >> nuts and bolts in the %post sections. I'm applying the same logic and >> applying the same kinds of things at the Fedora 7 site (even with the >> same IP networks/address space) and find that the at the Fedora 7 >> site, something is 'wrong'. About 1 time in 25 (or more) the system >> will build without anything changing; the rest of the time it is not >> NFS mounting for the KS.cfg parts. So, its failing at the same place. > > What's in /var/log/messages? > > > > To use http, you need a web server. I use virtual hosts, but that's not > essential. > > With a decent Internet connexion, one can also install via http directly off the > 'net. It runs well with a caching proxy, and bot Squid and Apache can fill that > role superbly. > > An advantage of this technique is that one only downloads those files actually > needed: there's no need for several Gbytes of data. > > Once it's cached, installs go at local LAN speeds. > > If using Squid, then I suggest a transparent proxy - it simplifies installs (one > does not need to configure the proxy) and applies to ordinary folk using Firefox, > Seamonkey etc as well. > > I use this virtual host definition: > [root at ns ~]# cat /etc/httpd/conf/vhosts.d/RHEL.conf > > ServerAdmin webmaster at computerdatasafe.com.au > DocumentRoot /var/local/mirrors/linux/RHEL > ServerName RHEL.demo.lan > ServerAlias RHEL.demo.room > ServerAlias RHEL > Alias /RHEL/ "/var/local/mirrors/linux/RHEL/" > Alias /Fedora/ "/var/local/mirrors/linux/Fedora/" > Alias /Specifix/ > "/var/local/mirrors/linux/Specifix/os/" > Alias /ScientificLinux/ > "/var/local/mirrors/linux/ScientificLinux/" > Alias /CentOS/ "/var/local/mirrors/linux/CentOS/" > ScriptAlias /ks/ "/var/local/mirrors/linux/ks/" > ErrorLog /var/log/httpd/RHEL-error_log > CustomLog /var/log/httpd/RHEL-access_log combined "/var/local/mirrors/linux/RHEL/"> > AllowOverride None > Options +FollowSymLinks +Indexes > Order allow,deny > Allow from 192.168 > > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > AllowOverride None > Options FollowSymLinks Indexes > Order allow,deny > Allow from 192.168 > > > > > [root at ns ~]# > > If you don't want the virtual host stuff, just remove the virtualhost things fore > and aft. > > I have another vhost which I used to install FC2 through a modem with > time-limited sessions; I'll post it on provocation:-) > > > > > > >> On the VC3 screen there is syslog-like output, of the following (retyped): >> 20:08:21 INFO : doing kickstart... setting it up >> 20:08:22 INFO : DHCPv4 interface configuration succeeded. >> 20:08:23 WARNING : reverse name lookup failed >> 20:08:24 INFO : url is 192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg >> 20:08:25 INFO : file location: nfs://192.168.10.2:/ks/ks-f/RHEL5u0x32ks.cfg >> 20:08:26 ERROR : failed to mount nfs source > > Like you, I found nfs a little temperamental. In contrast, httpp works > every time, and also it writes a nice log so one can see what files are > used. > > >> I've put the 'seconds' in increments to uniquely talk about each line, as >> needed. Before ":21" I'm frustrated with the IPv6 that it wastes time trying >> to mount, but hopefully someone will give me a way to prevent that. > > I think it's "noipv6" > >> At ":23" I do not understand that reverse name lookup failure. DNS has been >> setup, established, configured and not changed. For these boots, it seems >> that the errors only occasionally go away without any change to DNS or a >> restart of the named daemon. And when I don't get this error, the systems >> NFS mount and build fully. > It's trying to convert your install target's IP address to a host name. > It plans to use this as the name of the system. > >> At the Fedora 7 site, the Fedora 7 system is a Pentium 4 with 512 MB of RAM >> 726 GB of disk storage with a 100 bit ethernet card. The network connections >> are through a Linksys RT41-BU router. The kickstart'ees are virtual machines >> on a MAC Pro with dual quad-core CPUs, 4GB RAM and 520 GB of internal storage. >> The MAC Pro has XP64bit installed and is current with all the Micro$loth >> updates, no firewall, no anti-virus and no anti-spam enabled. Manually built >> systems of the above mentioned guests flawlessly install time after time, I >> can get them repeatedly successfully mount filesystems via NFS (and >> successfully export them too) > > Xen? > Virtual PC? > VMWare? > Whichever you're using, have you tried one of the others? > > > > I'm not sure of the current situation, but it used to be the case that > Anaconda's nfs tools weren't as good as the installed ones. Also, I > think it's using pump for its dhcp client. > >> There is also a Dell XPS 1710 laptop within the same network, also every > attempt >> to build 32 bit systems succeed. I even changed the 'mac' address of a problem >> one not building to identify the one from the MAC Pro over to the Dell XPS, and >> it built every time. >> >> R, >> -Joe Wulf, CISSP, USN(RET) >> Senior IA Engineer >> ProSync Technology Group, LLC >> www.prosync.com >> >> -----Original Message----- >> From: kickstart-list-bounces at redhat.com >> [mailto:kickstart-list-bounces at redhat.com] On Behalf Of John Summerfield >> Sent: Sunday, October 14, 2007 20:41 >> To: Discussion list about Kickstart >> Subject: Re: NFS booting problem >> >> Joe_Wulf wrote: >>> I've got an on again, off again problem where I can initiate a >>> kickstart for >>> RHEL5 (32 or 64 bit), as well as >>> for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS >>> config cannot be found. Then, after numerous reboots to troubleshoot >>> the problem, poof, the NFS mount is found and some systems get built. >>> Nothing changed. Even reboots of the kickstart server, the Linksys >>> router and the Mac Pro (with WinXP and VMware 6 installed) don't >>> change that many restarts have to happen before it will somehow, >>> magically start building. >>> >>> A most confusing problem and one that I need insight, advice and >>> questions from you all on what to check so I can solve it. All help >>> is appreciated! >> It's some years since I did an NFS install. http, in my experience, works well. >> Do you have some reason (other than setup) not to do it too? >> > > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From tzcovill at ybs.co.uk Wed Oct 17 08:57:17 2007 From: tzcovill at ybs.co.uk (Terry Covill) Date: Wed, 17 Oct 2007 09:57:17 +0100 (BST) Subject: NFS booting problem In-Reply-To: References: Message-ID: <25231956.1192611437879.JavaMail.oracle@ybsllx61.ybs.com> ************************************************************************ This email and any attachments are confidential and may contain privileged information. If you are not the person for whom they are intended please return the email and then delete all material from any computer. You must not use the email or attachments for any purpose, nor disclose its contents to anyone other than the intended recipient. Any statements made by an individual in this email do not necessarily reflect the views of the Yorkshire Building Society Group. ************************************************************************ Hello Joe I have just joined this list and have been following your problem. An issue I have seen where the kickstart build stalls with DNS and NFS mount problems was a layer 2 problem. It was intermittent and was finally cured by setting the portfast option on the switch port. this reduced the delay of the switch putting the NIC's MAC address in it's MAC table. Best regards Terry Covill Technical Support Group Yorkshire Building Society __________________________________________________ >From Joe_Wulf Sent Mon 15/10/2007 00:58 To kickstart-list at redhat.com Subject NFS booting problem I've got an on again, off again problem where I can initiate a kickstart for RHEL5 (32 or 64 bit), as well as for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS config cannot be found. Then, after numerous reboots to troubleshoot the problem, poof, the NFS mount is found and some systems get built. Nothing changed. Even reboots of the kickstart server, the Linksys router and the Mac Pro (with WinXP and VMware 6 installed) don't change that many restarts have to happen before it will somehow, magically start building. A most confusing problem and one that I need insight, advice and questions from you all on what to check so I can solve it. All help is appreciated! R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ __________________________________________________ _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com (mailto:Kickstart-list at redhat.com) https://www.redhat.com/mailman/listinfo/kickstart-list (https://www.redhat.com/mailman/listinfo/kickstart-list) ____________________________________________________________ Yorkshire Building Society, which is authorised and regulated by the Financial Services Authority, chooses to introduce its customers to: -Legal & General for the purposes of advising on and arranging life assurance and investment products bearing Legal & General's name; and -Homeowners Friendly Society for the purpose of arranging stakeholder Child Trust Funds. We are entered in the FSA Register and our FSA registration number is 106085 http://www.fsa.gov.uk/register Head Office: Yorkshire Building Society, Yorkshire House, Yorkshire Drive, Bradford, BD5 8LJ Tel: 0845 1 200 100 Visit Our Website http://www.ybs.co.uk All communications with us may be monitored/recorded to improve the quality of our service and for your protection and security. ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________ From Joe_Wulf at yahoo.com Wed Oct 17 21:47:40 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Wed, 17 Oct 2007 17:47:40 -0400 Subject: NFS booting problem In-Reply-To: <25231956.1192611437879.JavaMail.oracle@ybsllx61.ybs.com> References: <25231956.1192611437879.JavaMail.oracle@ybsllx61.ybs.com> Message-ID: Hi Terry, thank you. Both of my sites are small. One is facilitation connectivity with an 8 port BlackBox switch (not sure of the make/model, but its got no intelligence, just a straightforward switch), while my other site has a Linksys router. How would I manifest your suggestion in that environment? My problems continue. Seemingly at random a VM will kickstart build, but most of the time they still continue with the problems I've previously reports. I'm not going to have the project time to invest in another alternative solution (apache with proxy), as previously suggested. I am looking for how to troubleshoot the NFS problem. Would greatly appreciate thoughts and suggestions on what to look at, settings to put in place, etc... Thank you. R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Terry Covill Sent: Wednesday, October 17, 2007 04:57 To: Discussion list about Kickstart Subject: RE: NFS booting problem ************************************************************************ This email and any attachments are confidential and may contain privileged information. If you are not the person for whom they are intended please return the email and then delete all material from any computer. You must not use the email or attachments for any purpose, nor disclose its contents to anyone other than the intended recipient. Any statements made by an individual in this email do not necessarily reflect the views of the Yorkshire Building Society Group. ************************************************************************ Hello Joe I have just joined this list and have been following your problem. An issue I have seen where the kickstart build stalls with DNS and NFS mount problems was a layer 2 problem. It was intermittent and was finally cured by setting the portfast option on the switch port. this reduced the delay of the switch putting the NIC's MAC address in it's MAC table. Best regards Terry Covill Technical Support Group Yorkshire Building Society __________________________________________________ >From Joe_Wulf Sent Mon 15/10/2007 00:58 To kickstart-list at redhat.com Subject NFS booting problem I've got an on again, off again problem where I can initiate a kickstart for RHEL5 (32 or 64 bit), as well as for RHEL AS4 (32 or 64 bit) and many times the NFS mount for the KS config cannot be found. Then, after numerous reboots to troubleshoot the problem, poof, the NFS mount is found and some systems get built. Nothing changed. Even reboots of the kickstart server, the Linksys router and the Mac Pro (with WinXP and VMware 6 installed) don't change that many restarts have to happen before it will somehow, magically start building. A most confusing problem and one that I need insight, advice and questions from you all on what to check so I can solve it. All help is appreciated! R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com From debian at herakles.homelinux.org Wed Oct 17 22:58:25 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 18 Oct 2007 06:58:25 +0800 Subject: NFS booting problem In-Reply-To: <25231956.1192611437879.JavaMail.oracle@ybsllx61.ybs.com> References: <25231956.1192611437879.JavaMail.oracle@ybsllx61.ybs.com> Message-ID: <47169391.4070105@herakles.homelinux.org> Terry Covill wrote: > > ************************************************************************ > This email and any attachments are confidential and may contain privileged information. > Having this nonsence at the end of emails is almost more than I can bare. This is too much. I'm not going to wade through disclaimers to get to the guts. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From vikumar at redhat.com Wed Oct 24 13:04:25 2007 From: vikumar at redhat.com (Vimal Kumar) Date: Wed, 24 Oct 2007 18:34:25 +0530 Subject: Specify MAC address in kickstart Message-ID: <471F42D9.4010607@redhat.com> Hello, I had a query from a customer who has four network interfaces in his server and while doing a kickstart, he want interfaces with particular MAC addresses get assigned the name eth0, eth1 etc.. ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. I was only able to locate the directives for the 'network' section in kickstart, specified below. Are there any directives available to configure MAC addresses or is there a work around for this. *|network --device --bootproto --ip --netmask --gateway --nameserver --hostname ||--nodns|* Any ideas... Thanks in advance... Cheers, Vimal Kumar From email at jasonkohles.com Wed Oct 24 13:34:15 2007 From: email at jasonkohles.com (Jason Kohles) Date: Wed, 24 Oct 2007 09:34:15 -0400 Subject: Specify MAC address in kickstart In-Reply-To: <471F42D9.4010607@redhat.com> References: <471F42D9.4010607@redhat.com> Message-ID: On Oct 24, 2007, at 9:04 AM, Vimal Kumar wrote: > Hello, > > I had a query from a customer who has four network interfaces in > his server and while doing a kickstart, he want interfaces with > particular MAC addresses get assigned the name eth0, eth1 etc.. > > ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, > interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. > > I was only able to locate the directives for the 'network' section > in kickstart, specified below. Are there any directives available > to configure MAC addresses or is there a work around for this. > The only way to do configuration that kickstart can't do directly, is to write the configuration files yourself from a %post script %post cat < /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 BOOTPROTO=static HWADDR= 00:14:5E:B3:56:F4 IPADDR=192.168.0.1 NETMASK=255.255.255.0 ONBOOT=yes END cat < /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE=eth0 BOOTPROTO=static HWADDR= 00:14:5E:A7:0B:B8 IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=yes END -- Jason Kohles email at jasonkohles.com http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From hhoffman at ip-solutions.net Wed Oct 24 13:41:05 2007 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Wed, 24 Oct 2007 09:41:05 -0400 Subject: Specify MAC address in kickstart In-Reply-To: References: <471F42D9.4010607@redhat.com> Message-ID: <471F4B71.3040909@ip-solutions.net> While I'm not 100% sure, I think you may be able to accomplish this via boot parameters 'man bootparam' shows that ethernet devices can be assigned based upon IO and IRQ: ether=irq,iobase[,param_1[,...param_8]],name ether=0,0,eth1 This would, of course, require you to know the io address and the interrupt but it sounds doable. If you decide to go this route I'd be curious to hear how it works. Cheers, Harry Jason Kohles wrote: > On Oct 24, 2007, at 9:04 AM, Vimal Kumar wrote: > >> Hello, >> >> I had a query from a customer who has four network interfaces in his >> server and while doing a kickstart, he want interfaces with >> particular MAC addresses get assigned the name eth0, eth1 etc.. >> >> ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, >> interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. >> >> I was only able to locate the directives for the 'network' section in >> kickstart, specified below. Are there any directives available to >> configure MAC addresses or is there a work around for this. >> > The only way to do configuration that kickstart can't do directly, is > to write the configuration files yourself from a %post script > > %post > cat < /etc/sysconfig/network-scripts/ifcfg-eth0 > DEVICE=eth0 > BOOTPROTO=static > HWADDR= 00:14:5E:B3:56:F4 > IPADDR=192.168.0.1 > NETMASK=255.255.255.0 > ONBOOT=yes > END > > cat < /etc/sysconfig/network-scripts/ifcfg-eth1 > DEVICE=eth0 > BOOTPROTO=static > HWADDR= 00:14:5E:A7:0B:B8 > IPADDR=192.168.1.1 > NETMASK=255.255.255.0 > ONBOOT=yes > END > > --Jason Kohles > email at jasonkohles.com > http://www.jasonkohles.com/ > "A witty saying proves nothing." -- Voltaire > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From Chip.Shabazian at bankofamerica.com Wed Oct 24 16:21:27 2007 From: Chip.Shabazian at bankofamerica.com (Shabazian, Chip) Date: Wed, 24 Oct 2007 09:21:27 -0700 Subject: Specify MAC address in kickstart In-Reply-To: <471F4B71.3040909@ip-solutions.net> References: <471F42D9.4010607@redhat.com> <471F4B71.3040909@ip-solutions.net> Message-ID: You can also use ks=MAC_ADDR on the boot line to use that particular interface for the Kickstart. -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Harry Hoffman Sent: Wednesday, October 24, 2007 6:41 AM To: Discussion list about Kickstart Subject: Re: Specify MAC address in kickstart While I'm not 100% sure, I think you may be able to accomplish this via boot parameters 'man bootparam' shows that ethernet devices can be assigned based upon IO and IRQ: ether=irq,iobase[,param_1[,...param_8]],name ether=0,0,eth1 This would, of course, require you to know the io address and the interrupt but it sounds doable. If you decide to go this route I'd be curious to hear how it works. Cheers, Harry Jason Kohles wrote: > On Oct 24, 2007, at 9:04 AM, Vimal Kumar wrote: > >> Hello, >> >> I had a query from a customer who has four network interfaces in his >> server and while doing a kickstart, he want interfaces with >> particular MAC addresses get assigned the name eth0, eth1 etc.. >> >> ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, >> interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. >> >> I was only able to locate the directives for the 'network' section in >> kickstart, specified below. Are there any directives available to >> configure MAC addresses or is there a work around for this. >> > The only way to do configuration that kickstart can't do directly, is > to write the configuration files yourself from a %post script > > %post > cat < /etc/sysconfig/network-scripts/ifcfg-eth0 > DEVICE=eth0 > BOOTPROTO=static > HWADDR= 00:14:5E:B3:56:F4 > IPADDR=192.168.0.1 > NETMASK=255.255.255.0 > ONBOOT=yes > END > > cat < /etc/sysconfig/network-scripts/ifcfg-eth1 > DEVICE=eth0 > BOOTPROTO=static > HWADDR= 00:14:5E:A7:0B:B8 > IPADDR=192.168.1.1 > NETMASK=255.255.255.0 > ONBOOT=yes > END > > --Jason Kohles > email at jasonkohles.com > http://www.jasonkohles.com/ > "A witty saying proves nothing." -- Voltaire > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From email at jasonkohles.com Wed Oct 24 18:28:41 2007 From: email at jasonkohles.com (Jason Kohles) Date: Wed, 24 Oct 2007 14:28:41 -0400 Subject: Specify MAC address in kickstart In-Reply-To: <471F4B71.3040909@ip-solutions.net> References: <471F42D9.4010607@redhat.com> <471F4B71.3040909@ip-solutions.net> Message-ID: <3C6B9A13-7B19-4478-BCEE-1D61E82B34A2@jasonkohles.com> On Oct 24, 2007, at 9:41 AM, Harry Hoffman wrote: > While I'm not 100% sure, I think you may be able to accomplish this > via boot parameters > > 'man bootparam' shows that ethernet devices can be assigned based > upon IO and IRQ: > ether=irq,iobase[,param_1[,...param_8]],name > ether=0,0,eth1 > > This would, of course, require you to know the io address and the > interrupt but it sounds doable. > > If you decide to go this route I'd be curious to hear how it works. > On newer hardware it doesn't work at all, in modern hardware (after the mid-90s), the BIOS assigns the IO and IRQ at boot time, so you can't reliably predict what it will be in order to pass it on the command line. Also the arguments to ether= can vary depending on the driver being used for the card. On top of all that, ether= has been deprecated as of kernel 2.6.10. You can change the device name at run time though, with ip: ip link set eth0 name eth1 but putting HWADDR in network-scripts/ifcfg-* does this for you, and you don't have to figure out which ones are wrong in order to change them. > Cheers, > Harry > > > Jason Kohles wrote: >> On Oct 24, 2007, at 9:04 AM, Vimal Kumar wrote: >> >>> Hello, >>> >>> I had a query from a customer who has four network interfaces in >>> his server and while doing a kickstart, he want interfaces with >>> particular MAC addresses get assigned the name eth0, eth1 etc.. >>> >>> ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, >>> interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. >>> >>> I was only able to locate the directives for the 'network' >>> section in kickstart, specified below. Are there any directives >>> available to configure MAC addresses or is there a work around >>> for this. >>> >> The only way to do configuration that kickstart can't do directly, >> is to write the configuration files yourself from a %post script >> >> %post >> cat < /etc/sysconfig/network-scripts/ifcfg-eth0 >> DEVICE=eth0 >> BOOTPROTO=static >> HWADDR= 00:14:5E:B3:56:F4 >> IPADDR=192.168.0.1 >> NETMASK=255.255.255.0 >> ONBOOT=yes >> END >> >> cat < /etc/sysconfig/network-scripts/ifcfg-eth1 >> DEVICE=eth0 >> BOOTPROTO=static >> HWADDR= 00:14:5E:A7:0B:B8 >> IPADDR=192.168.1.1 >> NETMASK=255.255.255.0 >> ONBOOT=yes >> END >> >> --Jason Kohles >> email at jasonkohles.com >> http://www.jasonkohles.com/ >> "A witty saying proves nothing." -- Voltaire >> >> >> _______________________________________________ >> Kickstart-list mailing list >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > -- Jason Kohles email at jasonkohles.com http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From hhoffman at ip-solutions.net Wed Oct 24 18:53:46 2007 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Wed, 24 Oct 2007 14:53:46 -0400 Subject: Specify MAC address in kickstart In-Reply-To: <3C6B9A13-7B19-4478-BCEE-1D61E82B34A2@jasonkohles.com> References: <471F42D9.4010607@redhat.com> <471F4B71.3040909@ip-solutions.net> <3C6B9A13-7B19-4478-BCEE-1D61E82B34A2@jasonkohles.com> Message-ID: <471F94BA.3040900@ip-solutions.net> Awesome! thanks for the heads up... hopefully the bootparam manpage will be updated Jason Kohles wrote: >> > On newer hardware it doesn't work at all, in modern hardware (after the > mid-90s), the BIOS assigns the IO and IRQ at boot time, so you can't > reliably predict what it will be in order to pass it on the command > line. Also the arguments to ether= can vary depending on the driver > being used for the card. > > On top of all that, ether= has been deprecated as of kernel 2.6.10. > > You can change the device name at run time though, with ip: > > ip link set eth0 name eth1 > > but putting HWADDR in network-scripts/ifcfg-* does this for you, and you > don't have to figure out which ones are wrong in order to change them. > >> Cheers, >> Harry >> From vikumar at redhat.com Fri Oct 26 01:21:24 2007 From: vikumar at redhat.com (Vimal Kumar) Date: Fri, 26 Oct 2007 06:51:24 +0530 Subject: Specify MAC address in kickstart In-Reply-To: <471F42D9.4010607@redhat.com> References: <471F42D9.4010607@redhat.com> Message-ID: <47214114.8000804@redhat.com> Vimal Kumar wrote: > Hello, > > I had a query from a customer who has four network interfaces in his > server and while doing a kickstart, he want interfaces with particular > MAC addresses get assigned the name eth0, eth1 etc.. > > ie.. He wants the interface with MAC '00:14:5E:B3:56:F4' be eth0, > interface with MAC '00:14:5E:A7:0B:B8' be eth1 and so on.. > > I was only able to locate the directives for the 'network' section in > kickstart, specified below. Are there any directives available to > configure MAC addresses or is there a work around for this. > > *|network --device --bootproto > --ip --netmask > --gateway > --nameserver > --hostname > ||--nodns|* > > Any ideas... > > Thanks in advance... > > Cheers, > Vimal Kumar > > Hello, Thank you everyone, for the quick responses. I tried the configuration ( a little bit differently) as per Jason's response, did the configuration in the %post section. Here is what i added : ------------ %post mv /etc/sysconfig/network-scripts/ifcfg-eth0 /root/ifcfg-eth0.back touch /etc/sysconfig/network-scripts/ifcfg-eth0 echo "DEVICE=eth0 BOOTPROTO=static HWADDR=00:0C:29:CF:3D:1A IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth0 mv /etc/sysconfig/network-scripts/ifcfg-eth1 /root/ifcfg-eth1.back touch /etc/sysconfig/network-scripts/ifcfg-eth1 echo "DEVICE=eth1 BOOTPROTO=static HWADDR=00:0C:29:CF:3D:24 IPADDR=192.168.1.2 NETMASK=255.255.255.0 ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth1 mv /etc/sysconfig/network-scripts/ifcfg-eth2 /root/ifcfg-eth2.back touch /etc/sysconfig/network-scripts/ifcfg-eth2 echo "DEVICE=eth3 BOOTPROTO=static HWADDR=00:0C:29:CF:3D:2E IPADDR=192.168.1.3 NETMASK=255.255.255.0 ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth2 mv /etc/sysconfig/network-scripts/ifcfg-eth3 /root/ifcfg-eth3.back touch /etc/sysconfig/network-scripts/ifcfg-eth3 echo "DEVICE=eth4 BOOTPROTO=static HWADDR=00:0C:29:CF:3D:38 IPADDR=192.168.1.4 NETMASK=255.255.255.0 ONBOOT=yes" >> /etc/sysconfig/network-scripts/ifcfg-eth3 ----------------- This worked as intended and the system booted with the new configuration. The customer has not yet updated us, and so i am waiting. Thank you once again for all the responses. Vimal Kumar From Joe_Wulf at yahoo.com Fri Oct 26 12:24:24 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Fri, 26 Oct 2007 08:24:24 -0400 Subject: RHEL5.0 x64? Message-ID: During recent efforts in the %post processing section of RHEL5 x64 kickstarts, I'm unable to successfully NFS mount a locally available filesystem. I use the command "mount 192.168.10.2:/project /mnt". In VC3 I monitor the progress and receive the error "mount.nfs: Input/output error". At that moment in the build, over on VC2 I can manually accomplish the same command with immediate success (proven as I can list the contents of the NFS mount). Around that time efforts to list all of the mounted filesystems (no matter how I configure it) displays only a single entry for "/dev/root". Which is funny, as from VC2, "df -k" properly shows all the filesystems I've established and subsequent boots of the installed system show all the right filesystems, sized appropriately and where they should be. It's almost like the anaconda environment has lost its way. Another annoying issue is with timezone establishment. Seems like whatever I put, I cannot select the 'right' combination to get "GMT" to be recognized during install. Every effort I've tried shows error messages in either VC3 or VC4 of "Invalid timezone". Is the content from each of the Virtual Consoles preserved anywhere, like a log file available to the booted image only? Sure would be nice for troubleshooting to put a 'sleep 99999' in %post somewhere and then review those log files. Is there an 'option' that would allow this to happen? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com {resent without company graphic} -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joe_Wulf at yahoo.com Tue Oct 30 13:04:21 2007 From: Joe_Wulf at yahoo.com (Joe_Wulf) Date: Tue, 30 Oct 2007 09:04:21 -0400 Subject: Separate reference for %post Message-ID: Can the %post be a separate file altogether and 'included'? Where would I actually put the file so anaconda can properly get it? Where should it be put so that the %include directive properly picks it up? R, -Joe Wulf, CISSP, USN(RET) Senior IA Engineer ProSync Technology Group, LLC www.prosync.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From email at jasonkohles.com Tue Oct 30 14:57:30 2007 From: email at jasonkohles.com (Jason Kohles) Date: Tue, 30 Oct 2007 10:57:30 -0400 Subject: Separate reference for %post In-Reply-To: References: Message-ID: <2FD47064-1C35-4FA8-ABEB-06DEA6248979@jasonkohles.com> On Oct 30, 2007, at 9:04 AM, Joe_Wulf wrote: > Can the %post be a separate file altogether and ?included?? Where > would I actually put the file so anaconda can properly get it? > Where should it be put so that the %include directive properly picks > it up? > > > I don't know about %including it, but I almost always make my %posts a separate script, and then in the kickstart just run it from the real %post. Where you put it is going to depend on what kind of kickstart you are doing (cdrom,http,nfs?). My %post scripts are usually very minimal, generally something like this: %post wget http://kickstart/cgi-bin/post-install > /tmp/post-install-script chmod +x /tmp/post-install-script /tmp/post-install-script -- Jason Kohles, RHCA RHCDS RHCE email at jasonkohles.com - http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire -------------- next part -------------- An HTML attachment was scrubbed... URL: From Mohammed_Khan at Dell.com Wed Oct 31 16:14:21 2007 From: Mohammed_Khan at Dell.com (Mohammed_Khan at Dell.com) Date: Wed, 31 Oct 2007 11:14:21 -0500 Subject: issue w/ pykickstart when being used by liveinst... Message-ID: Hi I posted this on the livecd forums.. perhaps this forum is more appropriate audience: When running liveinst off of a livecd buit today, error I get is /usr/lib/anaconda/kickstart.py line 738... STATE_PRE is not defined... Looking into pykickstart... seems like the parser.py in pykickstart-1.13-2.fc7 does not have a STATE_PRE defined whereas FC7 gold's pykickstart (1.1-1) has it... Since the 1.13-2.fc7 is in updates, I am having to build livecd image against gold... building it w/ updates repo enabled causes issue described above. Thanks, MFK -------------- next part -------------- An HTML attachment was scrubbed... URL: From clumens at redhat.com Wed Oct 31 18:59:03 2007 From: clumens at redhat.com (Chris Lumens) Date: Wed, 31 Oct 2007 14:59:03 -0400 Subject: issue w/ pykickstart when being used by liveinst... In-Reply-To: References: Message-ID: <20071031185903.GJ24227@exeter.boston.redhat.com> > When running liveinst off of a livecd buit today, error I get is > /usr/lib/anaconda/kickstart.py line 738... STATE_PRE is not defined... > > > > Looking into pykickstart... seems like the parser.py in > pykickstart-1.13-2.fc7 does not have a STATE_PRE defined whereas FC7 > gold's pykickstart (1.1-1) has it... > > > > Since the 1.13-2.fc7 is in updates, I am having to build livecd image > against gold... building it w/ updates repo enabled causes issue > described above. You need pykickstart-1.13.1-1.fc7 which I have built an update for, but has still not been pushed. Keep watching the f7-updates-testing repo for when this appears. - Chris From Mohammed_Khan at Dell.com Wed Oct 31 19:19:09 2007 From: Mohammed_Khan at Dell.com (Mohammed_Khan at Dell.com) Date: Wed, 31 Oct 2007 14:19:09 -0500 Subject: issue w/ pykickstart when being used by liveinst... In-Reply-To: <20071031185903.GJ24227@exeter.boston.redhat.com> References: <20071031185903.GJ24227@exeter.boston.redhat.com> Message-ID: Chris, thanks for the heads up, I will await the update pykickstart. Thanks, MFK -----Original Message----- From: kickstart-list-bounces at redhat.com [mailto:kickstart-list-bounces at redhat.com] On Behalf Of Chris Lumens Sent: Wednesday, October 31, 2007 1:59 PM To: kickstart-list at redhat.com Subject: Re: issue w/ pykickstart when being used by liveinst... > When running liveinst off of a livecd buit today, error I get is > /usr/lib/anaconda/kickstart.py line 738... STATE_PRE is not defined... > > > > Looking into pykickstart... seems like the parser.py in > pykickstart-1.13-2.fc7 does not have a STATE_PRE defined whereas FC7 > gold's pykickstart (1.1-1) has it... > > > > Since the 1.13-2.fc7 is in updates, I am having to build livecd image > against gold... building it w/ updates repo enabled causes issue > described above. You need pykickstart-1.13.1-1.fc7 which I have built an update for, but has still not been pushed. Keep watching the f7-updates-testing repo for when this appears. - Chris _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list