Troubleshooting7–2
7.1 Installation issues
This section deals with issues that may arise when the HP SFS software is being installed on the client nodes.
The section is organized as follows:
• The initrd file is not created (Section 7.1.1)
• Client node still boots the old kernel after installation (Section 7.1.2)
7.1.1 The initrd file is not created
When you have installed the client kernel (see Section 3.3.2), there should be an initrd file (/boot/
initrd-kernel_version.img) on the client node; however, if the modules.conf file on the client
node is not suitable for the client kernel supplied with the HP SFS client software, the initrd file will not
be created.
If the initrd file does not exist after you have installed the client kernel, you must modify the
modules.conf file, and then create the initrd file manually. When you have finished creating the
initrd file, you can safely return the modules.conf file to its previous state.
To modify the modules.conf file and create the initrd file, perform the following steps:
1. Load the modules.conf into an editor. The contents of the file will be similar to the following:
alias parport_lowlevel parport_pc
alias eth0 tg3
alias eth1 tg3
alias scsi_hostadapter1 cciss
alias scsi_hostadapter2 qla2200
alias scsi_hostadapter3 qla2300_conf
alias scsi_hostadapter4 qla2300
alias scsi_hostadapter5 sg
options qla2200 ql2xmaxqdepth=16 qlport_down_retry=64 qlogin_retry_count=16
ql2xfailover=0
options qla2300 ql2xmaxqdepth=16 qlport_down_retry=64 qlogin_retry_count=16
ql2xfailover=0
post-remove qla2300 rmmod qla2300_conf
options ep MachineId=0x3064 txd_stabilise=1
Identify the module names. On the alias lines, the module name is the third entry (for example,
parport_pc); on the options lines, the module name is the second entry (for example,
qla2200).
2. Use the name of the kernel RPM file to determine the kernel version by entering the following
command:
# echo kernel_rpm_name | sed -e ’s/kernel\-\(.*\)\.[^\.]*\.rpm/\1/’
-e ’s/\(smp\)-\(.*\)/\2\1/’
3. Look at the contents of the /lib/modules/kernel_version directory (where
kernel_version is the kernel version determined in the previous step). If any of the modules listed
in the modules.conf file is not present in the /lib/modules/kernel_version directory,
comment out the corresponding line in the modules.conf file.
4. When you have finished modifying the modules.conf file, save the file.
5. Create the initrd file by entering the following command:
# mkinitrd /boot/initrd-kernel_version kernel_version
6. Verify that there is an appropriate entry for the initrd file in the boot loader on the client node.
When the initrd file has been successfully created, you can safely return the modules.conf file to its
previous state.
Kommentare zu diesen Handbüchern