similar to: Moving logical volumes

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

Why are there so many Fedora 6 packages in CentOS 5? Are there something wrong with the build system? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20070413/2a65a831/attachment-0004.bin>

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"

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

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

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

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

Hi all, This the latest output from anaconda.log:- 06:08:54,828 DEBUG anaconda: new disk order: [] 06:08:54,832 DEBUG anaconda: new disk order: [] 06:08:54,851 DEBUG anaconda: stage1 device cannot be of type disk 06:08:54,865 DEBUG anaconda: _is_valid_disklabel(sda1) returning True 06:08:54,867 DEBUG anaconda: _is_valid_size(sda1) returning True 06:08:54,867 DEBUG anaconda:

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

On Fri, Aug 26, 2016 at 10:39 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 08/25/2016 11:35 PM, Phil Manuel wrote: >> >> The relevant kickstart section is:- >> >> part /boot/efi --fstype efi --grow --maxsize=200 --size=20 --ondisk=sda >> bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda1 >> autopart

hello there, I wonder if you could help me: I am trying to install 50 diskless servers using PXE / kickstart, it all starts well, DHCP server issues a dynamic address, tftp issues the kickstart file, the client starts reading the KS file but at some point anaconda brings up an unhandled exception related to Python when reading Comps.xml?? What is really unsettling is the fact that if I plug

When try to install CentOS 5 via ftp on an system with less then 256MB RAM it fails. After select the ftp server witch contains the data, some files are loaded, then the dialog witch prompt for the ftp sever is shown again. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic

Hello, how can I get all files from an directory of an web server. An simple wget http://www.foo.bar/sample/* will not work:( Thanks for your help. Frank -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5766 bytes Desc: S/MIME Cryptographic Signature URL:

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.

Hello, This is my first post on this list. I am experiencing very often hard-locks while using different wine versions (from wine 0.9.58 until 1.0-rc3). My OS is Fedora 9 x86_64 and I also compiled 1.0-rc3 how the wine wiki told me to do. I am also experiencing hard-locks just by using winetricks. The hard-locks appear not immediately but sporadically. But that's a kernel issue I guess,

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