How to get kickstart to use existing logical volumes?
Gordon McDowall
gordon.mcdowall at fasthosts.co.uk
Wed Dec 8 08:34:22 UTC 2004
Hi Andrew
I had a similar issue when trying to do the same with a box running software
raid, I tried all sorts of different things before I eventually giving up.
What might be worth trying (although it didn't work for me) is to comment
out the partition info in the kickstart file, the kickstart process will
drop out at the partitioning point where you can manually configure the
partitions the way you want, once this has been done the kickstart install
will continue, after the install is complete and the machine has rebooted,
log in and take a look at the file /root/anaconda-ks.cfg to see how the
installer interpreted what you did with the partitions. Like I said, using
this partition info on software raid 1 still did not resolve my issue but it
might be worth a go for logical volumes. Sorry I can't be of more help.
Gordon McDowall
________________________________
From: Robinson, Andrew W. [mailto:Andrew.W.Robinson at mms.gov]
Sent: 07 December 2004 22:59
To: 'Discussion list about Kickstart'
Subject: How to get kickstart to use existing logical volumes?
I'm installing RHEL 3 EL on a server where I have already built the file
systems. Some of the file systems are on physical volumes and some are on
logical volumes. Apparently kickstart will not let me use the existing
logical volumes, or I haven't figured out the syntax to do so. Will
kickstart let me specify existing logical volumes? If so, how?
Had I build the file systems with kickstart, here's how it would have
looked:
clearpart -linux
part /boot --fstype ext3 --size 100 -ondisk sda
part swap --size 8196 --ondisk sda
part / --fstype ext3 --size 1 grow --ondisk sda
part pv.01 --size 1 --grow -ondisk sdb
volgroup vg01 pv.01
logvol /opt --vgname=vg01 --size=30720 --name=opt
logvol /var --vgname=vg01 --size=30720 --name=var
logvol /var/ftp/pub --vgname=vg01 --size=61440 --name=pub
Having built the file systems in advance, I tried this syntax:
clearpart --none
part /boot --onpart=sda2
part swap --onpart=sda3
part / --onpart=sda4
part /opt --onpart=/dev/vg01/opt
part /var --onpart=/dev/vg01/var
Part /var/ftp/pub --onpart=/dev/vg01/pub
The Kickstart failed, complaining about the /dev/vg01. It did not like plain
vg01 when I took off the /dev/. Any suggestions on what it might like?
Thanks.
Andrew Robinson
More information about the Kickstart-list
mailing list