Sharpe, Sam J wrote:
Jan-Frode Myklebust wrote:We have this small snippet in our kickstart files:clearpart --all --initlabel part /boot --fstype ext3 --size=128 part pv.0 --size=0 --grow volgroup rootvg pv.0 logvol / --fstype ext3 --name=rootlv --vgname=rootvg --size=5120 logvol swap --fstype swap --name=swaplv --vgname=rootvg --size=2048 logvol /var --fstype ext3 --name=varlv --vgname=rootvg --size=3072logvol /local --fstype ext3 --name=locallv --vgname=rootvg --size=1024which works fine, except when there's more than one disk in the system. Then it picks the first disk (sda or hda) to hold the /boot fs, and the second disk (sdb or hdb) to hold the root volume group. Does anybody know how fix this so that both are placed on the same disk during kickstart ?Two things to try, as arguments to both of your "part" lines:--ondisk=sda (not really useful unless you detect whether the first disk is hda or sda first)--onbiosdisk=80 (I think that will be the first disk detected by the machine's BIOS - I've never tried this option myself)The information on the latter, I found on the Dell Linux site a while ago and put on my list for investigation:http://linux.dell.com/installermagic.shtml -- Sam
Another option is to use "ignoredisk --drives=sdb,sdc,sdd,hdb,hdc,hdd" though the --onbiosdisk option looks more useful so that you don't end up with a growing list of drives to ignore.
I generally find this page useful when dealing with kickstart http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html
Hugh
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
