search for: logvol

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 made active, so my /dev/volgroup/logvol did not exist. Running `lvm lvchange -a -y pathname` from with in the shell after anaconda failed made the volgroup / logvol act...

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 after doing a manual install to generate the file lvm configuration I'm getting the same results. I have also deleted the whole virtual machine and started from scratch. Any sugge...

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 "DEBUG blivet: failed to set size...

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 --name=lvol4 --noformat The purpose is reinstalling a machine with a given partitioning schem...

...have: %pre if [ -b /dev/sda ] then zerombr clearpart --all bootloader --location=mbr --timeout=0 --driveorder=sda --append="crashkernel=auto rhgb quiet" part /boot --fstype=ext4 --size=500 part pv.008002 --grow --size=1 volgroup vg_host --pesize=4096 pv.008002 logvol / --fstype=ext4 --name=lv_root --vgname=vg_host --grow --size=1024 --maxsize=51200 logvol swap --name=lv_swap --vgname=vg_host --grow --size=512 --maxsize=1024 fi elif [ -b /dev/vda ] then zerombr clearpart --all bootloader --location=mbr --timeout=0 --driveorder=vda --append="...

..., 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 pv.00 --fstype="lvmpv" --onpart=vda2 --noformat volgroup v --noformat logvol / --fstype=xfs --name=wurzel --vgname=v --useexisting logvol /home --fstype=ext4 --name=home --vgname=v --noformat ... you see, / will be reformatted, /boot will be reformatted, but /home will not. Now a machine with md raid 1. I tried the following. ... #zerombr #clearpart --none --initl...

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 ## part /boo...

Hi, I need to mount a LVM in rescue mode to create a new initrd image. I am not sure how do I fond out which LogVol is to be mounted. How do I find it out? In most of the configs I have used LogVol00 with ext3 filesystem which contains OS install. This particular system is not installed by me and I am not sure how do I find it out. I did try 'lvm lvs' command, but probably that's not the right comma...

...too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" --name=00 --vgname=ee logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" --name=01 --vgname=ee Thanks, LF

...on my code looks like.* cat > /tmp/partmap.ks <<EOPM *clearpart --all --initlabel --drives=sda *part swap --fstype swap --asprimary --size=16000 part /boot --fstype ext3 --size=400 --asprimary --fsoptions=noatime,defaults part pv.01 --size=1 --grow volgroup jmpvgnocf pv.01 logvol / --fstype ext3 --name=lvroot --vgname=jmpvgnocf --size=1 --grow --fsoptions=noatime,defaults logvol swap --fstype swap --name=lvswap --vgname=jmpvgnocf --size=$swap_size EOPM LV Name always shows /dev/volGroup00/LogVol00. *my VM partition code looks like* cat > /tmp/partmap.ks <<EOOPM...

Has anyone gotten this to work ? I can define a raid device but cant put a VG on it. I then tried 'autopartition' and it created an 'LVM' of sorts, when I tried to edit it I wasnt able to as a message appeared saying, LVM editing was not allowed in text mode. Any help ? Cheers, Brian. PS - PIII-500mhz 128mb RAM, 4mb AGP.

...quiet" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work #clearpart --none #volgroup VolGroup00 --pesize=32768 --useexisting --noformat pv.253002 #logvol None --fstype=ext3 --name=LogVol00_data --vgname=VolGroup00 --useexisting --noformat #logvol /home --fstype=ext4 --name=LogVol00_home --vgname=VolGroup00 --useexisting #logvol / --fstype=ext4 --name=LogVol00_root --vgname=VolGroup00 --useexisting #logvol swap --name=LogVol00_swap --vgname=VolGro...

...ate failed for VolGroup00". The Xen VM file is allowed to grow up to 2GB. The kickstart commands for partioning are: clearpart --all --initlabel --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 pv.2 --pesize=32768 pv.2 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=416 --grow --maxsize=832 This is taken exactly from the "template" kickstart file, I just added the --initlabel after reading the kickstart tips on...

...ume 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 --fstype="None" --grow --size=1232 --thinpool --name=pool00 --vgname=centos_centos7 logvol swap --fstype="swap" --size=819 --name=swap --vgname=centos_centos7 logvol / --fstype="xfs" --grow --maxsize=51200 --size=1024 --thin --poolname=pool00 --name=root --vgname=c...

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. The only way to successful kickstart is to not encrypt the lvm pv. The contents of the passphrase are not to blame, installer still dies after accepting a passphrase from th...

...hints? >> >> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >> /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT >> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee --pesize=4096 >> pv.0104 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" >> --name=00 --vgname=ee >> logvol /srv --fstype="ext4" --percent=100 --grow --encrypted --label="SRV" >> --name=01 --vgname=ee >> > If I'm reading that correctly - haven...

Hello, Can you check following entrys: Old: disk = [''phy:vm_volumes/root.dhcp1,sda1,w'', ''phy:vm_volumes/var.dhcp1,sda2,w'', ''phy:vm_volumes/swap.dhcp1,sda3,w''] New: disk = [''phy:/vm_volumes/root.dhcp1,sda1,w'', ''phy:/vm_volumes/var.dhcp1,sda2,w'',

...t; > > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT > > part pv.0104 --fstype="lvmpv" --ondisk=sda --grow volgroup ee > --pesize=4096 > > pv.1974 logvol / --fstype="ext4" --size=3072 --encrypted --label="ROOT" > > --name=00 --vgname=ee > > logvol /srv --fstype="ext4" --percent=100 --grow --encrypted > --label="SRV" > > --name=01 --vgname=ee > > > If I'm reading that correctly...

...mate 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 Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol01 36G 11G 24G 30% / /dev/sda1 99M 17M 78M 18% /boot /dev/mapper/VolGroup00-LogVol02...

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, the kernel args did specify &qu...