similar to: Problem creating volgroups with kickstart installations (on xen)

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 all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4"

centos-virt, I'm trying to create/install domU guests all in "one" step, following Daniel's wiki page (I've found these pages really helpful, BTW): http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU I have a few questions about this process: (1) How would it be modified (w/respect to defining the disk in the domain configuration file) to use a disk layout where dom0

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

Has anyone managed to create an encrypted disk partition with CentOS 8 kickstart? 1 reqpart --add-boot 2 part /boot --fstype ext3 --size=1024 --ondrive=sda 3 part pv.1 --size=1 --grow --ondrive=sda --encrypted --pashphrase="bla" 4 volgroup vol0 pv.100000 5 logvol / --vgname=vg_00 --name=lv_root --size=102400 --fstype=ext4 ... No matter what I specify in line 3, the installer bombs out.

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

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

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 Wed, 8 May 2019 at 13:24, mark <m.roth at 5-cent.us> wrote: > Leon Fauster via CentOS wrote: > > Hi all, > > > > > > I still use the following kickstart partition scheme for C7 installations > > (via virt-install): > > Briefly, fixed size for /root and /boot, and the rest is filled up for > > /srv. > > > > The same kickstart

>> 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, 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

Hi, just to avoid re-inventing the wheel, is there any document that can help me reduce even further a "minimum" installation of Centos 4.4 (BTW can you say 600mb is minimum)? I am in the process of creating a small Centos-4.4-based Asterisk box and I need to boot it from a CF card. Deleting useless packages will help me do what i want. Example: even a minimum install of Centos 4.4 (or

Hi, just to avoid re-inventing the wheel, is there any document that can help me reduce even further a "minimum" installation of Centos 4.4 (BTW can you say 600mb is minimum)? I am in the process of creating a small Centos-4.4-based Asterisk box and I need to boot it from a CF card. Deleting useless packages will help me do what i want. Example: even a minimum install of Centos 4.4 (or

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

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

I am trying to install CentOS 4.6 to a pair of 750GB hard drives. I can successfully install to either of the drives as a single drive, but when I try to use both drives and mirror the partitions, I start having problems. Anaconda crashes as it is trying to format the drives. This is what I'm trying to create: /dev/md0: 200MB, /boot /dev/md1: 2GB, swap /dev/md2: rest of the

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

I am trying to install Centos 7 on a couple 4TB drives with software raid. In the Supermicro bios I set UEFI/BIOS boot mode to legacy. I am using the Centos 7 minimal install ISO flashed to a USB thumb drive. So I do custom drive layout something like this using sda and sdb. Create /boot as 512 MB XFS raid1 array. Create SWAP as 32 GB SWAP raid1 array. Create / on 3.xxx TB XFS raid1 array.

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

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