On 11/24/2010 06:43 AM, Robert Moskowitz wrote:
I am using my anaconda-ks.cfg to rebuild a system (F12). I am using
the
same partitions as before, just reformatting. This is what I did in my
last rebuild manually, so I ASSUMEd the anaconda-ks.cfg file had all the
right commands to uncomment, but I still got an error. Here are the
pertinent lines:
#clearpart --none
The default is --none so it does not matter if this is included or not.
volgroup vg_klovia_00 --pesize=4096 --useexisting --noformat
pv.cqT7O1-lvx9-fBxs-0b1q-91j0-PRDt-xH3d3s
logvol /home --fstype=ext4 --name=Home_00 --vgname=vg_klovia_00
--useexisting
logvol / --fstype=ext4 --name=Root_00 --vgname=vg_klovia_00 --useexisting
part /boot --fstype=ext4 --onpart=sda1
part swap --onpart=sda2
part pv.cqT7O1-lvx9-fBxs-0b1q-91j0-PRDt-xH3d3s --onpart=sda3 --noformat
I took a guess that the part commands have to come before the lvm
commands, and that anaconda had written them out in the 'wrong' order. I
was right, because I changed the order and the install is chugging
along. It is nice to pull both the base OS and the Updates in a single
pass from a local repo.
But one thing I have NOT found in reading docs at:
https://fedoraproject.org/wiki/Anaconda/Kickstart is what is the <id>
part of pv.<id>
I would guess that Disk Druid originally used a random number for <id>,
but I cannot find any information on 'good' choices for <id>.