HP DL360 Booting HP ProLiant servers from a storage area network - Page 6

Scripted installs If multiple LUNs are visible to the HBA, by default the Red Hat Linux kickstart file will install Linux partitions across the available LUNs. In most cases, it is desirable to place the OS partitions on the first LUN. To do this, copy and rename the desired kickstart file and add the following to the end of each part command: --ondisk=sda On Red Hat Enterprise Linux 3, you must specify the location of the bootloader. To place the grub bootloader on the first LUN, add the following to the end of the bootloader command in your kickstart file: --driveorder=sda Copy and modify the desired job to point to the modified kickstart file. Setting up two paths to the LUN (for example, through both HBAs on a blade) will cause an OS failure due to a drive that is "unformatted, damaged, or formatted with a file system that is incompatible" or return errors like "Invalid Partition." The OS must be installed in a single path configuration. To resolve the issue, either remove one of the HBA cables or set up the SAN switch zoning to allow access to the LUN from only the first HBA and one array controller port. After the OS is installed, install the multipathing software and enable the second HBA to access the LUN. Image deployment After deploying the first server using scripting, you can deploy additional servers using imaging. To deploy a server with an embedded array controller to boot from SAN using imaging, you must first modify the provided image deployment jobs in the Server Replication job folder to eliminate the array configuration tasks. Copy and rename the appropriate job, and then delete the third and fourth tasks. 6