|
Did you use a double dash for â--preexistingâ? I didnât notice
as I was typing it that Outlook had âhelpfullyâ changed the two dashes to a single
emdash. Did the pvcreate command actually work: does that disk now have a full-disk
PV on it? In the pvcreate documentation, I just came across For
whole disk devices only the partition table must be erased, which will
effectively destroy all data on that disk. This can be done by zeroing the
first sector with: dd if=/dev/zero of=PhysicalVolume bs=512 count=1 Hereâs something else to try: echo
"part pv.01 --onpart sdb --grow" >> /tmp/custom-part echo
"volgroup rootvg /dev/sdb pv.01" >> /tmp/custom-part If kickstart refuses to create a partition on sdb, you will have
to do something like lvm
pvcreate /dev/sdb lvm
vgcreate rootvg /dev/sdb echo
"logvol / --fstype ext3 --name=root --vgname=rootvg --size=4096
--useexisting" >> /tmp/custom-part Moray. âTo
err is human; to purr, feline.â From: Speagle, Andy
[mailto:andy.speagle@xxxxxxxxxxx] Iâve actually tried that in the past. It doesnât
work. But, for completeness, I tried it againâ and I receive this error
from anaconda: Error Parsing Kickstart Config The following error was found while parsing the kickstart
configuration file: The following problem occurred on line 2 of the kickstart file: Tried to use undefined partition /dev/sdb in Volume Group
specification Any thoughts on that? Iâm at a loss. -Andy From: kickstart-list-bounces@xxxxxxxxxx
[mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Moray Henderson
(ICT) As well as generating /tmp/custom-part for kickstart, your %pre
script also has to execute the Linux commands to create the PV. There
were some examples given earlier in this thread: lvm
pvcreate /dev/sdb echo
"volgroup rootvg /dev/sdb âuseexisting" >> /tmp/custom-part ought to give you a volgroup called rootvg consisting of the
whole of /dev/sdb. See 31.4. Kickstart
Options if you havenât found it already. Moray. âTo err is human; to purr, feline.â From: Speagle, Andy [mailto:andy.speagle@xxxxxxxxxxx]
Hi Team, Iâve progressed a bit on this issue. What Iâm presently
trying to do is use a simple %pre script to generate a temp file with the
commands to be included in the partitioning section of the kickstart. So,
I run the %pre script, it creates /tmp/custom-part, which is included in the
partitioning section using: %include /tmp/custom-part All of that works duckilyâ however anaconda refuses to use
ârootvgâ without it being defined using the âvolgroupâ command in the
partitioning section. And sadly, I canât get the âvolgroupâ command to
work without a PV defined. If I try to specify the partition by passing
the --useexisting and --onpart options to the âpartâ commandâ that fails too â
so I continue to be stuck. This is what I do to have the /tmp/custom-part
created: echo "part /boot --fstype=ext3 -- >
/tmp/custom-part echo "volgroup rootvg --useexisting" >>
/tmp/custom-part echo "logvol / --fstype=ext3 --name=root --vgname=rootvg
--size=4096" >> /tmp/custom-part echo "logvol swap --fstype=swap --name=swap --vgname=rootvg
--size=2048" >> /tmp/custom-part echo "logvol /var --fstype=ext3 --name=var --vgname=rootvg
--size=2048" >> /tmp/custom-part echo "logvol /var/tmp --fstype=ext3 --name=vartmp
--vgname=rootvg --size=1024" >> /tmp/custom-part echo "logvol /home --fstype=ext3 --name=home
--vgname=rootvg --size=2048" >> /tmp/custom-part echo "logvol /tmp --fstype=ext3 --name=tmp --vgname=rootvg
--size=1024" >> /tmp/custom-part echo "logvol /opt --fstype=ext3 --name=opt --vgname=rootvg
--size=2048" >> /tmp/custom-part Has anyone actually done this? Is there some magic Iâm
missing? -Andy OM International Limited - Unit B Clifford Court, Cooper Way -
Carlisle CA3 0JG - United Kingdom |
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
