SAN, ISCSI and NAS devices are mostly support booting and can be used as OS disks. However, it's important to be very careful when installing/kickstarting a storage node attached via fibre channel, you may never want to see that one of your SAN disk is accidentally installed as OS disk, even worse, there are some data on the SAN disk.

Here I show you some ways to prevent this from happening. I Use Qlogic HBA driver as example, you can just replace it with your own device driver.

1. blacklist FC driver

Add the following line to grub

append initrd=/boot/initrd.img blacklist=qla2xxx

2. remove FC module

This is for kickstart installing, remove the FC module

%pre
modprobe -r qla2xxx

3. Remove FC driver from intrid image.

It is preferable to modify the pxe-boot initrd image and remove the QLogic HBA drivers to prevent the anaconda kernel from seeing them.

 

When creating a new pxeboot area for this purpose do the following (this example uses SL 6.4):

 


### create a working directory and unpack the initrd image into it:
# mkdir /var/tmp/work ; cd /var/tmp/work
# cp -p /.../pxeboot/initrd.img .
# file initrd.img
initrd.img: LZMA compressed data, streamed
# xz --format=lzma -S .img initrd.img --decompress
# ls
initrd
# file initrd
initrd: ASCII cpio archive (SVR4 with no CRC)
# cat initrd | cpio -dimvu
# rm initrd
# cd modules/
# ls
2.6.32-358.el6.x86_64  module-info
# cd 2.6.32-358.el6.x86_64
### find the kernel driver modules and remove the qla2* drivers:
# find . -name '*qla2*.ko*'
./kernel/drivers/scsi/qla2xxx/qla2xxx.ko.gz
# rm -rf kernel/drivers/scsi/qla2xxx
# cd ../../
### repack the initrd image: 
# find . | cpio -o -H newc | xz --format=lzma > ../initrd.img
### make a special directory in the PXE-boot area and copy the kernel
### and the modified initrd image into it:
# cd /osinstall/nbp
# mkdir x86_64_hsm_sl6.4
# cd x86_64_hsm_sl6.4
# cp -p /.../pxeboot/vmlinuz .
# cp -p /var/tmp/work/initrd.img .