3.5.1 Matrix Server Installation Guide (June 2008)

Appendix A: Install the RHEL4 Operating System 45
2. Run the mkinitrd command to create the initrd image. See step “5.
Run mkinitrd If Necessary” on page 47.
NOTE: Although this procedure removes the HBA drivers from the initrd
image, you will likely see the HBA drivers loaded after the first
reboot of the kernel. The kernel HBA modules will be exempted
from loading after the Matrix Server rpm is installed and the
blacklist is updated.
Third-Party MPIO Solution
If you will be using a third-party MPIO solution such as EMC PowerPath
or IBM RDAC, the HBA driver must be loaded during the initial booting
of the kernel. (The MPIO drivers are dependent on the HBA drivers and
require that they be loaded first.) When Matrix Server starts later in the
boot process, it recognizes the third-party MPIO driver and does not try
to load its own HBA driver. (You may need to take steps to ensure that
the appropriate HBA driver is loaded. See your vendor documentation
for more information.)
SAN Boot Disk
With certain storage arrays, the boot disk can be on the SAN. In this case,
the HBA driver must be loaded with the kernel so that the boot disk can
be located. (You may need to take steps to ensure that the appropriate
HBA driver is loaded. See your vendor documentation for more
information.) You will need to use non-fabric fencing with this
configuration.
Install Other HBA Drivers
If your configuration requires either an HBA driver version that is
provided with Matrix Server but is not the default, or an HBA driver
version that is not provided with Matrix Server, you can install that
version after Matrix Server is installed on the server. (The installation
procedure in Chapter 2 specifies when to install the driver.)