Appendix A - Kickstart
Kickstart automates installations by using a script tailored to your needs. Although this method replaces most human interaction through Anaconda, it requires a serial connection.
For more information on kickstart options, visit www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-kickstart2-options.html .
- To initiate a Kickstart installation, you must first enter the QS2x or PXCAB firmware via a serial connection.
- Repeatedly press "s" when powering on the QS2x or PXCAB.
- To conduct a Kickstart installation:
boot net ks=[http://[url]/kickstart.cfg [ENTER]
- Repeatedly press "s" when powering on the QS2x or PXCAB.
- In your Kickstart script, you must specify the nfsroot command which takes two arguments: --server $nfsServer and –path $nfsPath where nfsServer and
nfsPath where defined during the NFS Setup, as given in the example script below.
install url --url http://192.168.100.1/ydl6installer lang en_US.UTF-8 network --device eth0 --bootproto dhcp --hostname qs21 a rootpw --iscrypted $1$xuUUbIfg$TbI79vvXXfpkAC3FmaeYZ/ firewall --enabled –port=22:tcp authconfig --enableshadow –enablemd5 selinux –disabled timezone --utc America/New_York bootloader –location=none nfsroot --server 192.168.100.1 --path /srv/nfsroot/ %packages @editors @text-internet @core @base @development-libs @development-tools
- The installer will attempt to create a new directory inside the directory named after the MAC address of the eth0 interface. Note that if this new
directory already exists, the installer will abruptly exit. Remove the directory and try again.
- Once the installation is complete, a file will be placed within the /{MAC ADDRESS}/boot directory within the specified NFS path of the new YDL installation on the Server. For example, if the NFS directory was /srv/nfsroot, the file will be placed in /srv/nfsroot/{MAC ADDRESS}/boot. The file will be named "$hostname-nfsroot-$uname.img" where $hostname is the manually configured hostname of the QS2x/PXCAB and $uname is the kernel version.
Copy this file to the /tftpboot directory. The file may need to be renamed to match the image name configured on your DHCPD server during the DHCPD Server Setup. For example, it may need to be renamed {HOSTNAME}.img if this is what you set the "filename" to in the dhcpd.conf file.
- Restart XINETD:
service xinetd restart [ENTER]
Appendix B - Manipulating the boot process and NFS roots
You have the option to create a new boot image or modify the NFS server IP and path in order to change the location of NFS root.
- Create a new boot image.
- On the installed blade, edit /etc/fstab to point to the new location and then create a new boot image:
mknfszimage [ENTER]
- A file will be placed within the /{MAC ADDRESS}/boot directory within the specified NFS path of the new YDL installation on the Server. For example, if the NFS directory was /srv/nfsroot, the file will be placed in /srv/nfsroot/{MAC ADDRESS}/boot. The file will be named "$hostname-nfsroot-$uname.img" where $hostname is the manually configured hostname of the QS2x/PXCAB and $uname is the kernel version.
Copy this file to the /tftpboot directory. The file may need to be renamed to match the image name configured on your DHCPD server during the DHCPD Server Setup. For example, it may need to be renamed {HOSTNAME}.img if this is what you set the "filename" to in the dhcpd.conf file.
- Restart XINETD:
service xinetd restart [ENTER]
- On the installed blade, edit /etc/fstab to point to the new location and then create a new boot image:
- Change the NFS server IP and Path.
- To specify a root-path, edit /etc/dhcpd.conf on the Server and add a root-path option:
host qs21a { hardware ethernet 00:04:ac:00:00:aa; filename "qs21a.img"; fixed-address 192.168.100.100; option root-path "192.168.100.1:/srv/nfsroots/00:04:AC:00:00:AA” } - Restart DHCPD:
service dhcpd restart [ENTER]
- Reboot the blade in order to use the new root-path.
- To specify a root-path, edit /etc/dhcpd.conf on the Server and add a root-path option:
- Subsequent blade installations.
- Once the first installation is complete, copy the installation for other QS2x's or PXCAB's:
cp [/path/to/AA:BB:CC:00:00:AA] [/path/to/AA:BB:CC:00:00:BB] [ENTER]
... where AA:BB:CC:00:00:AA is the existing installation/MAC address of the first blade, and AA:BB:CC:00:00:BB is the new installation/MAC address of the second blade.
- Edit [/path/to/AA:BB:CC:00:00:BB/]etc/fstab to point to /path/to/AA:BB:CC:00:00:BB instead of /path/to/AA:BB:CC:00:00:AA
- Edit [/path/to/AA:BB:CC:00:00:BB/]etc/sysconfig/network to specify the correct hostname and
[/path/to/AA:BB:CC:00:00:BB/]etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 to specify the correct the Ethernet MAC addresses for the new
blade.
- Follow the steps in the Installation section to configure net booting for the new blade.
- Once the first installation is complete, copy the installation for other QS2x's or PXCAB's:
Appendix C - Trouble Shooting
- Load failed ! - Netboot fails
If your blade was previously able to load the boot image via TFTP fine, try restarting xinetd with the following command:service xinetd restart [ENTER]
- Kernel panic during boot:
udhcpc[1161]: Sending select for 192.168.100.100... Lease of 192.168.200.100 obtained, lease time 86400 udhcpc[1161]: Kernel panic - not syncing: Attempted to kill init! Lease of 192.168Rebooting in 180 seconds..
If you see the following error while booting, either the blade's /etc/fstab or root-path option is incorrect. Verify /etc/fstab or the root-path argument and follow step 1 in Appendix B - Manipulating the boot process and NFS roots.
Terra Soft Solutions offers a variety of support services with fast, friendly, and personalized service. Please contact your Terra Soft Solutions account manager with any issues or questions you may have regarding the installation and use of Yellow Dog Linux v6.0 for the IBM QS2x blade or for the PXCAB.
This HOWTO was prepared by Owen Stampflee and Kai Staats, Terra Soft Solutions, Inc.





