similar to: ext3 partition on LVM lost all data

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

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

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

I am using a kickstart file for CentOS 7 raid / --device=md0 --fstype="xfs" --level=1 --useexisting raid /home --noformat --device=md1 --level=1 --useexisting It is erroring out on the --useexisting. The exact text is: RAID volume "0" specified with "--useexisting" does not exist. What did I do wrong? Jerry

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

Dear All, I'm trying to create a kickstart installer. 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? The following is the lines for disk partitioning definition specified in my kickstart file. ------------------------- ## ## Disk partitioning information

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

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 >

Sorry - I did not include that I am actually "updating" a system from C6 to C7 and it has an existing RAID /dev/md0 and /dev/md1. Hit send to quick. Jerry On Wed, Aug 29, 2018 at 3:52 PM Jerry Geis <jerry.geis at gmail.com> wrote: > I am using a kickstart file for CentOS 7 > > raid / --device=md0 --fstype="xfs" >

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

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

I've install a CentOS Stream 9 system from a kickstart file that specified (among other things) several logical volumes: logvol / --fstype="ext4" --size=10240 --name=lv_root --vgname=VolGroup logvol /var --fstype="ext4" --size=4096 --name=lv_var --vgname=VolGroup logvol swap --fstype="swap" --size=2048 --name=lv_swap --vgname=VolGroup When that system rebooted,

Hey, I solved my "The installation source given by device ['sdb2'] could not be found". Apparently ignoredisk is so strong it not only ignores the disks to be partitioned but also the disks holding the installation source... Now I ran into: ? In interactive step cleardiskssel, can't continue In anaconda.log I saw: ? step installtype does not exist ? step confirminstall

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".

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"

> 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

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

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