search for: pesize

Hi, I'm trying to setup the provisioning of new OpenStack hypervisors with cinder volumes on them. The problem is that kickstart doesn't allow dashed in volume group names? I tried this: volgroup cinder-volumes --pesize=4096 pv.02 and this: volgroup cinder--volumes --pesize=4096 pv.02 but in both cases I end up with a volume group named "cindervolumes" on the system. Any idea what I have to do to accomplish this? Defining VGs with dashes works perfectly fine on the command line. Regards, Denis

...SystemError: vgcreate 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...

...et a "device is 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

...bit stuck. This is what I 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 --driv...

...t the partitioning information: ks.cfg supplied: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14 --end=796 --ondisk=hda part pv.34 --start=797 --end=2303 --ondisk=hda part swap --start=2304 --end=2434 --ondisk=hda volgroup VolGroup00 --pesize=32768 pv.34 logvol /var/opt/scalix --fstype ext3 --name=Scalix --vgname=VolGroup00 --size=8192 anaconda-ks.cfg reports: clearpart --all --drives=hda part /boot --fstype ext3 --size=100 --ondisk=hda part / --fstype ext3 --start=14 --end=796 --ondisk=hda part pv.100000 --start=797 --end=2303 --ond...

...ed the whole virtual machine and started from scratch. Any suggestions on 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 --vgn...

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

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

...t described) as the disk and map it to a frontend device called 'xvda'. Again using kickstart, I expect it would look like this: ####### in domU kickstart... ####### clearpart --all --initlabel --drives=xvda #... part pv.01 --size=100 --grow --asprimary --ondisk=xvda volgroup volgroup00 --pesize=4096 pv.01 logvol /home --fstype ext3 --name=LV_home --vgname=volgroup00 --size=3072 #... ####### (5) Any comments, criticisms, or suggestions for improvement on these ideas? Thanks!

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

...eted are not expressed >> # here so unless you clear all partitions first, this is >> # not guaranteed to work >> clearpart --linux --drives=sda >> part /boot --fstype ext3 --size=100 --ondisk=sda >> part pv.9 --size=0 --grow --ondisk=sda >> volgroup VolGroup00 --pesize=32768 pv.9 >> logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 >> --grow >> logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 >> --size=1000 --grow --maxsize=1984 >> >> %packages >> @base >> @core >> @editors...

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

...oo 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 > If I'm reading that correctly - ha...

On 08.05.19 19:16, Leon Fauster via CentOS wrote: ... > I get a "device is too small for new format" error. Any hints? ...> part pv.0104 --fstype="lvmpv" --ondisk=sda --grow pv.0104 > volgroup ee --pesize=4096 pv.1974 pv.1974 mismatch! -- Kind Regards, Markus Falb -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 236 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attach...

...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 &g...

...cord zerombr yes #Partition clearing information clearpart --all --initlabel --drives=hda #Disk partitioning information part pv.1 --size 1058 --noformat part /boot --fstype ext3 --size 100 --ondisk=hda part swap --start=4603 --end=4864 part pv.6 --size=0 --grow --ondisk=hda volgroup VolGroup00 --pesize=32768 pv.6 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=10240 logvol /home --fstype ext3 --name=home --vgname=VolGroup00 --size=25600 --grow ================================================= I get an error of lvm cann''t create the volgroup. The partitions were creat...

..., it comes up without the /data partition, it is not mounted and not in fstab. But the lvol exists and can be mounted manually, with all data preserved. /root/anaconda-ks.cfg shows the following: #part /boot --fstype=ext3 --onpart=sda1 #part pv.008002 --onpart=sda2 --noformat #volgroup vol0 --pesize=32768 --useexisting --noformat pv.008002 #logvol / --fstype=ext4 --name=lvol1 --vgname=vol0 --useexisting #logvol /tmp --fstype=ext4 --name=lvol2 --vgname=vol0 --useexisting #logvol swap --name=lvol3 --vgname=vol0 --useexisting #logvol --name=lvol4 --vgname=vol0 --useexisting --noformat I.e. the...

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

...ev/VolGroup00/LogVol00' [2.91 GB] inherit I've tried various alternatives 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 (/), whi...