similar to: CentOS7 kickstart failed ( no such option: --bytes-per-inode)

On Thu, 19 Nov 2015, Mihoko.Tanaka at jp.yokogawa.com wrote: > I specified an option --byes-per-inode to 'logvol' command, but I got a > message "No such option: --bytes-per-inode" during installation. > > Does anybody know a solution? Wasn't that removed years ago?

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'm trying to create a kickstart file that uses a thinly provisioned lvm volume as root but I've run into trouble. I installed a System manually using this option and this is the anaconda file produced: part /boot --fstype="xfs" --ondisk=vda --size=500 part pv.10 --fstype="lvmpv" --ondisk=vda --size=7691 volgroup centos_centos7 --pesize=4096 pv.10 logvol

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 >

> Am 08.05.2019 um 19:20 schrieb mark <m.roth at 5-cent.us>: > > 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

I'm testing doing kickstart installations on Xen VMs. This is the first time I'm trying out kickstart at all, so I rather think I'm doing something wrong in the kickstart configuration than it is a Xen issue. I use a modified kickstart file from an earlier manual installation with a very basic filesystem setup. It fails with "SystemError: vgcreate failed for VolGroup00".

I am asking this here, that although a kickstart question, may have something to do with the Centos install? I took my Anaconda-ks.cfg from my system, turned it into a ks.cfg and did the install. Everything SEEMS ok, but why? First the partitioning information: ks.cfg supplied: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14

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"

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

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

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 (despite that c7 uses vda, f29 uses sda) doesn't work > with Fedora29 (EL8). I get a "device is too small for new

On 2019-05-08 12:28, Stephen John Smoogen wrote: > 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

Hello, I've been trying to kickstart a install centos from a USB memory stick. Everything with that is working fine, but I seem to be having a problem with the ks.cfg file. When I boot the install media from the usb drive, the the boot prompt I type linux ks=hd:/dev/uba1/ks.cfg Then I peek at the logs and it even says * getting kickstart file * getting kickstart file from harddrive *

I have a kickstart file with the following partitioning directives: part /boot --fstype ext3 --onpart=sda1 part pv.100000 --onpart=sda2 --noformat volgroup vol0 pv.100000 --noformat logvol / --vgname=vol0 --name=lvol1 --useexisting --fstype=ext4 logvol /tmp --vgname=vol0 --name=lvol2 --useexisting --fstype=ext4 logvol swap --vgname=vol0 --name=lvol3 --useexisting logvol /data --vgname=vol0

I fought with this for a day, and now am crying for help.... The goal is 5 partitions: boot, notebook suspend, / , /home. and swap. So I have to use LVM. Here are my commands: #System bootloader configuration bootloader --location=mbr #Clear the Master Boot Record zerombr yes #Partition clearing information clearpart --all --initlabel --drives=hda #Disk partitioning information part pv.1

Hello, Our environment: CentOS 5.2 (updated over time with "yum update", current "yum update" lists about 7 packages out of date), x86_64. Running Xen, building Xen DomU's with kickstart. We are trying to debug the %post part of the kickstart process for DomU and are hitting difficulties in accessing the output. For a start, the "cmdline" directive in the

Hello Gentlemen, I would like to ask a question about an issue I have with the Centos 6.3 installation. I have installed a Centos 6.3 on a server we used before with 5.4 on Friday. I have created a KS file to let me connect to the server via VNC and have all repos and packages preconfigured. I only needed to partition the hard drive using VNC. During the partition process I selected which

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

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

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