similar to: Kickstart from floppy falling into regular install

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart

Hey, Can anyone tell me why option 1 works and option 2 fails ? I know I need swap and such, however in trouble shooting this issue I trimmed down my config. It fails on trying to format my logical volume, because the mount point does not exist (/dev/volgroup/logvol) It seems that with option 2, the partitions are created and LVM is setup correctly. However the volgroup / logvolume was not

Hi. I'm currently trying to configure a kickstart script to do auto installs. We split up the partitions so that we have control on the mount security like setting no execute on the tmp portions etc . I keep hitting the same error : "Could not stat /dev/VolGroup00/LogVol_root --- No Such file or directory The device apparently does not exist; did you specify is correctly " Even

I am trying using a kickstart file to install CentOS 6.2 into a new virtual machine (the MBR sector of the harddisk is all zero), however I found that the installer cannot go through the harddisk partition. It failed after I chose "Use All Space" at harddisk partition option. The error message is: http://anony.ws/i/bMcTJ.png "You have not defined a root partition (/), which is

>> Dave wrote: >>> Hi, >>> >>> Thanks for your reply. Yah i do have apache running, your idea >>> certainly would make things easier. How did you set up the http area? >>> And where in it do you put the kickstart? I'd like this area to be >>> accessible to my local network only, internet users shouldn't be able >>>

hi, The problem: for kvm/qemu disks are /dev/vdx devices when using the virtio driver. For vmware, drives are /dev/sdx devices. For hp servers, /dev/ccisss/whatever (sorry, no proliant with an array controller handy to check it). in order to just have one kickstart script to maintain I am trying to use the %pre section but getting a bit stuck. This is what I have: %pre if [ -b /dev/sda ] then

Hi, I am struggling with kickstart. What I want to achieve is a reinstall, but some data partitions should survive the install, i.e. they should not be formatted. With a single disk this works, here is the relevant part from the kickstart file (I shortened the name of the volume group) ... zerombr clearpart --none --initlabel part /boot --fstype="xfs" --label=boot --onpart=vda1 part

So I took the anaconda cfg, commented out the partition/disk pieces and ran it off my repo server and it almost worked. Little things like not including things I had done on network setup. No first boot.... :) So now I am reading up on building a kickstart cfg http://wiki.centos.org/TipsAndTricks/KickStart http://www.centos.org/docs/5/html/5.2/Installation_Guide/s1-kickstart2-howuse.html

Hello Group, I am building a company application based on Centos 5.7 OS. The application was working earlier and creating right partitions both for hardware as well as VM. But since we introduced Centos 5.7 OS and start building application with 5.7 anaconda the hardware partitions are duplicate of VM partitions *while creating hardware partition my code looks like.* cat >

On Sun, 21 Aug 2016 at 12:51 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/19/2016 11:35 PM, Phil Manuel wrote: > > The install fails under UEFi due to the fact the partitions are not > cleared, and it doesn?t have any space to continue. Is there an extra step > I need to do to remove the original partitions before the new layout will > work ? > > >

I'd like to automate the upgrade from CentOS 4.6 to 5.1 as much as possible. Since upgrades per se are not really recommended, I'm planning to do a kickstart installation. However, I want to leave one of the existing partitions (/scratch) untouched during the installation. Here is my current layout (LogVol00 is swap so not shown in the df output below): # df -hl

Hi, I was at the Puppet talk at Oscon and I would like to try using Puppet for PXE on RHEL machines and I was wondering if there are standard minimal Kickstart recipes from which Puppet can then take over. Thanks, Jason van Zyl jason at maven.org

I was just wondering how (or indeed if) people use the %include directive in Kickstart configuration files when building systems via NFS. I've been trying to modularise our Kickstart files a little to make things more readable, having generic defaults and role specific stuff split out into separate configs. I've tried this configuration... [root at archive kickstart]# cat

I am trying to add an efi partition to my working kickstart file. bootloader --driveorder=sda --append="rhgb quiet biosdevname=0 net.ifnames=0" clearpart --all --initlabel part / --ondisk=sda --fstype xfs --size=20000 --asprimary part swap --ondisk=sda --size=4000 --asprimary part /boot/efi --ondisk=sda --fstype efi --size=1000 --asprimary part /home --ondisk=sda

Gordon Messmer wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart --type=lvm > > A couple of things to consider: > * The documentation for

I am testing some kickstarts on ESXi virtual machine with pair of 16GB disks. Partitioning is lvm over raid. If i am using "logvol --grow i get "ValueError: not enough free space in volume group" Only workaround i can find is to add --maxsize=XXX where XXX is at least 640MB less than available. (10 extents or 320Mb per created logical volume) Following snippet is failing with

Hello, I am trying to build a PXE boot image for CentOS 7. livemedia-creator --make-pxe-live --ks=ks --no-virt It runs the entire process and then it says: losetup: /dev/: detach failed: Inappropriate ioctl for device 2019-12-26 11:49:47,293: Disk Image install successful 2019-12-26 11:49:47,293: working dir is /var/tmp/tmpKwqC77 mount: /dev/loop0 is write-protected, mounting read-only mount:

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

On Tue, 23 Aug 2016 at 02:18 Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/21/2016 11:56 PM, Phil Manuel wrote: > > part /boot/efi --fstype="efi" --size=200 --ondisk=sda > > And I have tried the latter with location as mbr still fails > > What am I missing ? > > > I very vaguely remember struggling with this as well, but I can't find