I looked up the documentation on %pre and its example.  I see
what you are saying.

Thanks for the tip.

I usually use kickstart via nfs so I have a copy of the kickstart
that installed the machine.



On 10/12/2015 09:34 AM, Nico Kadel-Garcia wrote:
> On Mon, Oct 12, 2015 at 10:14 AM, Ken Teh <[log in to unmask]> wrote:
>> I'm having problems with an 6.7 install.  Here are the relevant lines:
>>
>> # partitions
>>
>> #clearpart --drives=disk/by-id/ata-SATA_SSD_96D70756062400160297
>> part /boot --fstype=ext4 --size=1024 --asprimary
>> --ondisk=disk/by-id/ata-SATA_SSD_96D70756062400160297
>> part pv.01 --size=1 --grow --asprimary
>> --ondisk=disk/by-id/ata-SATA_SSD_96D70756062400160297
>>
>> volgroup sysvg pv.01
>> logvol swap --fstype=swap --vgname=svsvg --size=12288 --name=swap
>> logvol / --fstype=ext4 --vgname=sysvg --size=1 --grow --name=root
>
>> Kickstart stops trying to create the swap logical volume.  Claims there is
>> no such sysvg volume.  I did an alt-F2 and ran parted on the disk.  The
>> 'part' command never created the partitions.  This is my first time using
>> the 'disk/by-id/...'  syntax.  Also, first time with an SSD disk.  I checked
>> /dev/disk/by-id and the disk is listed with the correct id.
>
> Don't hurt yourself. That "disk-by-id" or using UUID, is not stable.
> If you need to ensure particular disk layouts, put in a '%pre'
> statement to partition things the way *you* want in a saveable,
> scriptable format, and use the resulting LABEL or  LVM based volumes
> to hand off to the rest of the kickstart configuration. The anaconda
> disk configuration tools are powerful, but awfully confusing and very
> diffficult to get right if you try to do *anything* that is not bog
> standard. And the "system-config-kickstart" GUI for resetting
> kickstart files is not much help: it profoundly reformats the
> kickstart file you start with, and throws out multiple "%pre" or
> "%post" steps.
>
>
> And ooohh, if you're using kickstart files? Put in a %post --nochroot"
> to copy /tmp/ks.cfg to /mnt/sysimage/root/ks.cfg, so that you have an
> actual copy of the kickstart file you actually used on that particular
> system!
>
>> Has anyone tried the ssh option with kickstart?  I understand you can ssh to
>> the machine and monitor it during the installation.  The one advantage I can
>> see is the saved lines on a terminal window instead of the 80x24 console.
>
> I've not tried that, I'm not sure the SSH binaries are even in the CD
> boot images: I don't see them in the "boot.iso" images.
>