Arvind, On Tue, Mar 09, 2010 at 10:24:04PM +0000, Arvind Navale wrote: > I am in the process of performing Kickstart test for HP blade server which has internal drives managed by Smart Array Controller. I will be installing RHEL-4.4 version of OS and will be applying kernel patch to bring it to update-6 version of kernel. This server has SAN attached disks and I am trying to understand how can call out the OS disk and its partition in the kickstart.cfg file and prevent SAN disks being selected. So far I used SCSI disks and different hardware platform which had device path as /dev/sd# and were as with this HP blade server my understanding is that the OS disk will be using CCISS drivers and will have /dev/cciss/c#d# as its device path. I am looking have / on physical partition and remaining OS file systems on LVM partition. Based on my research so far here is what I have come with and would like to have it validated to make it will work without issues. > > clearpart --drives=cciss/c0d0 -all --initlabel > part / -fstype ext3 --size=8000 --asprimary --ondisk=cciss/c0d0 > part pv.1 --size=120000 --grow --ondisk=cciss/c0d0 > > volgroup rootvg pv.1 > logvol /usr --fstype ext3 --name=usr-vol --vgname=rootvg --size=8000 > logvol /var --fstype ext3 --name=var-vol --vgname=rootvg --size=8000 > logvol /opt --fstype ext3 --name=opt-vol --vgname=rootvg --size=8000 > logvol swap --fstype swap --name=swap-vol --vgname=rootvg --size=8192 > logvol /tmp --fstype ext3 --name=tmp-vol --vgname=rootvg --size=4000 The above looks eerily similar to those used on a daily basis here (only slight preference type differences): part / --ondisk cciss/c0d0 --fstype ext3 --size 2048 part /boot --ondisk cciss/c0d0 --fstype ext3 --size 100 part swap --ondisk cciss/c0d0 --size 8192 part pv.01 --ondisk cciss/c0d0 --size 7680 --grow volgroup vg00 pv.01 logvol /usr --vgname vg00 --fstype ext3 --size 4096 --name usr logvol /var --vgname vg00 --fstype ext3 --size 4096 --name var logvol /home --vgname vg00 --fstype ext3 --size 4096 --name home logvol /opt --vgname vg00 --fstype ext3 --size 4096 --name opt logvol /tmp --vgname vg00 --fstype ext3 --size 4096 --name tmp One other action we do take though, is often to explicitely remove the SAN/FibreChannel qla*ko from the install images initrd. Mostly we did this for boot time performance, so as not to wait for the scan time, but also helps to protect incase a more generic "clearpart --all" appears in ks.cfg. Another side benefit is that the installed grub seems less likely to be confused. HTH, bryang _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
