search for: vgname

...n how I can resolve this ? >From ks.cfg bootloader --location=mbr --driveorder=sda clearpart --linux part /boot --size=101 --fstype ext3 part swap --size=2048 --asprimary part pv.22 --size=100 --grow volgroup VolGroup00 --pesize=32768 pv.22 logvol /var/log --fstype ext3 --name=LogVol_var_log --vgname=VolGroup00 --size=2048 logvol /home --fstype ext3 --name=LogVol_home --vgname=VolGroup00 --size=2048 logvol /var --fstype ext3 --name=LogVol_var --vgname=VolGroup00 --size=2048 logvol /usr --fstype ext3 --name=LogVol_usr --vgname=VolGroup00 --size=2048 logvol / --fstype ext3 --name=LogVol_root --vg...

...lgroup / logvol active. Which would allow the format command to complete. Option 1: zerombr yes clearpart --all --initlabel part /boot --fstype ext3 --size=100 part pv.os --size=10000 --grow --maxsize=10000 --asprimary volgroup os_volgroup01 pv.os logvol swap --fstype swap --name=os_swap_logvol --vgname=os_volgroup01 --recommended logvol / --fstype ext3 --name=os_root --vgname=os_volgroup01 --size=1024 --grow Option 2: zerombr yes clearpart --all --initlabel part /boot --fstype ext3 --size=100 part pv.os --size=10000 --grow --maxsize=10000 --asprimary volgroup os_volgroup01 pv.os logvol / --fst...

...the former to rename the logical volume that my root partition resides on, the system became unbootable. In addition to renaming the LV (and VG if I decide to to that as well), what else needs to be changed? So far my list includes: o /etc/fstabb o /boot/grub/grub.conf o /dev/<vgname>/<lvnamex> o /dev/mapper/<vgname-lvnamex> I was hoping the lvrename and/or vgrename would take care of these details. Are there any scripts out there that take care of all the details? If not, I may write one (once I have the recipe to get this working, of course). Alfre...

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 scheme and pres...

...mount. I''m trying to do this at the moment with a define of the following type: # Manage a partition and create if needed. define lv_partition( $name = "partition", $location = "/tmp", $lvsize = "1G", $fstype = "ext3", $vgname = "vg00", $lvname = $name, $owner = "root", $group = "root", $mode = "755" ) { file { "$location/$name": ensure => directory, owner => $owner, group => $group, mode =&gt...

...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="crashkernel=auto rhgb quiet" cl...

...art 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 --initlabel part raid.01 --onpart vda1 --noformat...

...ve=sdb --grow raid /boot --fstype="xfs" --device="md0" --level=RAID1 raid.01 raid.11 raid pv.01 --fstype="lvmpv" --device="md1" --level=RAID1 raid.02 raid.12 volgroup vg0 pv.01 logvol / --fstype="xfs" --grow --size=4096 --name=lvRoot --vgname=vg0 logvol swap --fstype="swap" --size=2048 --name=lvSwap --vgname=vg0 If i only add --maxsize=13164 everything is working. (but after install i have 640MB in 20 Free PE in vg0, for details see "after --maxsize install") logvol / --fstype="xfs" --grow -...

...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 clearpart --all --initlabel #autopart...

...disk=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

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.

...rmation 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=VolGroup00 --useexisting #logvol /tmp --fstype=ext4 --n...

...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 the wiki. I read the kickstart part of t...

...help to create my mountpoint location with root:root/755 and after mounting allow the same location to have a different owner:group/ permissions. These are the defines I use at this moment define lvm::createfs ( $mountpath = undef, $mountpoint = undef, $lvsize = undef, $fstype = undef, $vgname = undef, $lvname = "${name}", $requisite = '''' ) { # Load defaults require lvm::params # Check mountpath equals root $rootpath = $mountpath ? { ''/'' => undef, default => $mountpath, } # Create directory tree includin...

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 the console....

...tion ## part /boot/efi --fstype="efi" --ondisk=sda --size=190 part /boot --fstype="xfs" --ondisk=sda --size=476 part pv.01 --fstype="lvmpv" --ondisk=sda --size=1 --grow volgroup centos --pesize=4096 pv.01 logvol swap --fstype="swap" --size=4096 --name=swap --vgname=centos logvol / --fstype="xfs" --size=9536 --name=root --vgname=centos logvol /var --fstype="xfs" --size=4768 --name=var --vgname=centos logvol /opt --fstype="xfs" --size=25600 --name=opt --vgname=centos logvol /data --fstype="xfs" --size=204800 --name=da...

...> /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 - haven't worked on a kickstart in years - > I'd start by increasing root to 1024 (1M) for /bo...

I have a series of unmounted lv's that are used in xen vm's of various flavors in a lab environment. I made a script that I use to backup all of them prior to doing anything I may need to undo and all I execute is: dd if=/dev/vgname/lvname of=/dir/name.img Are there any additional parameters I should use? I haven't tried to restore this into an lv, but I did swap the 'phy' specification for 'file' and started a vm using the backed up image and it was fine. Thanks! jlc

...is 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=centos_centos7 The Problem is that when I use this as the basis for a kickstart A...

...atives of specifying the disk layout in the kickstart file, and here is my latest attempt: part /boot --fstype ext3 --onpart sda1 part pv.2 --noformat --onpart sda2 volgroup VolGroup00 --noformat --useexisting --pesize=32768 logvol swap --useexisting --fstype swap --name=LogVol00 -- vgname=VolGroup00 logvol / --useexisting --fstype ext3 --name=LogVol01 -- vgname=VolGroup00 But when I try to install CentOS 5.1 via kickstart, anaconda complains that "You have not defined a root partition (/), which is required for installation of CentOS to continue". Has anyone...