similar to: Kickstart 8TB partition limit?

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 all, I've started playing with kvm on CentOS 5.5, with not much success so far. In a nutshell, I have the same problem as http://lists.centos.org/pipermail/centos-virt/2010-April/001854.html I followed the RHEL5 virtualization guide to set up a bridge interface br0, and then used virt-install (rather than virt-manager - I like automation) to set up the vm. It hangs at some point.

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

We're trying to migrate RHEL3 and CentOS4 based samba servers over to CentOS5, but it's a bleeding disaster. We cannot get it to work reliably with any version of CentOS5, i386 or x86_64, the included 3.0.x version of samba or 3.4.x/3.5.x compiled from source. The symptoms are: read access is extremely slow, write access seems to work in principle (e.g. creating a zeros-sized file on

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.

I'm trying to build a bugfixed anaconda package for 5.3 x84_64, but there are some fairly basic failures, like pkg-config .pc files not being found. When I modify the spec file accordingly, linking fails because installed libraries are not found. $ rpmbuild -ba anaconda.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.25019 + umask 022 + cd /usr/src/redhat/BUILD + LANG=C + export LANG +

I've written some %pre code to grab a few files off a logical volume, if it exits, before the disk gets formatted, but can't get get it to work correctly. Essentially: %pre ... lvm vgscan lvm vgchange -a y ... if [ -d /dev/vol0 ]; then # do stuff fi lvm vgremove -f vol0 The problem is that /dev/vol0 does not exist after lvm vgchange. I added a few debug statements (lvm pvdisplay, lvm

I'm following this thread here http://www.centos.org/modules/newbb/viewtopic.php?topic_id=23749&forum=38 to build an rpm for thunderbird 3.1.6/3.1.7 from source. While it works well on i386, compilation fails for x86_64. Any advice how to fix the spec file? ... rm -f libthebes.so c++ -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth

I rebuilt my xen host with the 64-bit OS and am in the process of recreating the guests, both 32 and 64 bit. I use a kickstart installation with virt-install, and so far none of the installation attempts has completed. Anaconda indicates installation should take about 2-3 minutes, but when it comes to installation of selinux policies, it just sits there, and I have no idea what it's

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

In the 2.7 relnotes the 16-bit half float type is described, with a link to the corresponding LangRef section. However, this section seems to be missing in the 2.7 LangRef, I do see it in trunk, though... Regards, Paul

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

I need to support 3.9 for another while and thought I would set up a local repo with base and updates merged into one. How can I update repodata? I don't see createrepo in 3.9. --------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise

Which configuration or rc script is responsible for loading the kvm modules on CentOS 5.4/5.5? They interfere with vmware. --------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.

Hi all, I'm updating a customised CentOS 5.2 repo to 5.4. After running createrepo, I find all the usual .xml.gz files updated, but the sqlite.bz2 files have not been touched. What is the significance of these files? If they need to be updated, how is it done? -r--r--r-- 1 user group 1811 Oct 1 2009 TRANS.TBL -rw-r--r-- 1 user group 1050329 May 12 11:04 comps.xml -rw-r--r-- 1 user

Hi, I have a 24TB RAID6 disk with a GPT partition table on it. I need to partition it into 2 partitions one of 16TB and 1 of 8TB to put ext4 filesystems on both. But I really need to do this remotely. ( if I can get to the site I could use gparted ) Now fdisk doesn't understand GPT partition tables and pat

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

The 5.3 upgrade broke the kickstart procedures for my xen virtual machines. They are installed via http. 1. The installer sets up the timezone interactively even though it is specified in the kickstart file. Not a big deal, though. 2. The installer hangs unpredictably when installing selinux-policy-targeted-2.4.6-203.el5.noarch.rpm. Performing a dozen or so installs, sometimes the