HP XC System Software Release Notes for Version 3.1

4 Head Node Installation
This chapter contains notes that apply to the HP XC System Software Kickstart installation
session.
4.1 Notes to Read Before the Kickstart Installation Session
Read the notes in this section before starting the Kickstart installation session.
4.1.1 Additional Kickstart Boot Command Options For Some Hardware Models
Some hardware models require additional options to be included on the boot command line.
Before booting the head node, look in Table 4-1 to determine if your head node requires a special
option on the boot command line.
Table 4-1 Boot Command Line Based on Hardware Model
Boot Command LineHardware Model
boot: linux ks=cdrom:/ks.cfg pci=nommconf
HP ProLiant DL385 G2
boot: linux ks=cdrom:/pci=nommconf
HP ProLiant DL585 G2
4.2 Reusing Partitions Does Not Work on All HP Integrity Systems
The option to reuse existing disk partitions rather then using the default HP XC default
partitioning does not work on all HP Integrity systems. The installation process looks for the
/boot/efi partition to be in a fat16 format, but this partition can be a fat32 format on some
systems.
To work around this problem, install and boot the node using the default HP XC partitioning
scheme. Then, after the system has booted, disable swap, unmount the partitions, and adjust the
partition sizes using the parted utility.
4.3 MySQL Database Daemon Does Not Start
If the mysql database daemon does not start, check the appropriate log file in
/var/lib/mysql/node_name.err for errors. One of the most common reasons for this type
of failure is that the mysql database daemon could not create a temporary file in the /tmp
directory on start up.
Follow this procedure to resolve the problem:
1. Verify the /tmp directory permissions and change the permissions if needed:
# ls -l -d /tmp
# chmod 1777 /tmp
2. Restart the mysql database daemon:
# service mysqld restart
4.1 Notes to Read Before the Kickstart Installation Session 37