search for: volgroups

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

Thanks all for the advice. It seems there is an issue with Dracut booting from these hosts when LVM is used. dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit dracut: inactive '/dev/VolGroup/lv_root' [230.69 GiB] inherit dracut: PARTIAL MODE. Incomplete logical volumes will be

While updating a hypervisor, I'm getting the following errors printed to the terminal during rpm upgrade scripts.? The first line is printed 15 times, and GRUB prints a similar error at boot.? "vgck" doesn't seem to find any problems.? Does anyone have suggestions for diagnosing the issue? error: ../grub-core/disk/diskfilter.c:524:unknown node

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,

In the past, I've used LVM on MD RAID, and I'd like to try using LVM RAID in order to also add dm-integrity data to some LVs.? I've added new PVs to my VG, and I've converted some of my LVs to raid1 types, but I also have one thin pool that I use for VMs with multiple layers of snapshots.? That pool can't be converted, directly: # lvconvert --type raid1 -m 1

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

On 1/9/22 15:37, Gordon Messmer wrote: > 1: The system also includes a volume group named "BackupGroup" and > that group activates on boot (post-dracut).? Why are those LVs > activated when rd.lvm.lv is specified? As far as I can tell, this is because in the dracut boot process, the device backing VolGroup is activated, but the device backing BackupGroup is not.? As a

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

Fasiha Ashraf --- On Sat, 22/8/09, Fasiha Ashraf <feehapk@yahoo.co.in> wrote: From: Fasiha Ashraf <feehapk@yahoo.co.in> Subject: Re: [Xen-users] my bootlog To: "Boris Derzhavets" <bderzhavets@yahoo.com> Date: Saturday, 22 August, 2009, 11:12 AM Please check what wrong here grub.conf        title Fedora (2.6.30-rc6-tip)         root (hd0,6)         kernel

On Thu, Dec 4, 2014 at 12:39 PM, Bob Ball <bob.ball at citrix.com> wrote: > Thanks all for the advice. > > It seems there is an issue with Dracut booting from these hosts when LVM is used. > > dracut: Scanning devices sda2 for LVM logical volumes VolGroup/lv_swap VolGroup/lv_root > dracut: inactive '/dev/VolGroup/lv_swap' [1.94 GiB] inherit > dracut: inactive

Hi All, One of my servers upon a restart today comes up with an error checking filesystems: fsck.ext3: no such file or directory while trying to open /dev/VolGroup-1/Logvol00. /dev/VolGroup-1/LogVol00. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then

Hi All, I just tried to create a DomU using the following method... (I normally use the Xen install kernel when I create CentOS domus, but when I tried that with the PXE image, that had the same effect as below). This is the first time I have created a Fedora domu in ages... years, even. virt-install \ --paravirt \ --name demo \ --ram 500 \

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

As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here. To upgrade: yum update --enablerepo=centos-virt-xen-testing To install from scratch: * Install centos-release-xen from centos-extras yum install

Graphic installer doesn't like my graphics card, so I am using the text installer. I have two physical disks in my system. When I get to the "partitioning type" page, I choose "remove all partitions on selected drives [etc]" and put an asterisk next to sda, no asterisk next to sdb. I want to use sdb as a separate partition, no LVM, I figure I can set it up after

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, These are my make menuconfig screen shots. I haven''t found any xen option in v2.6.30-rc. Why is that so? this happens with most of the version. What should I do? should I just let it as it is an run the make command to build the kernel? Regards, Fasiha Ashraf See the Web''s breaking stories, chosen by people like you. Check out Yahoo! Buzz. Love Cricket?

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

Dear Robert, Thank you. The state after reboot are as follows. # LANG=C lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom vda 252:0 0 15G 0 disk |-vda1 252:1 0 500M 0 part /boot `-vda2 252:2 0 14.5G 0 part |-VolGroup-lv_root (dm-0) 253:0 0

On 04/13/2016 12:02 AM, ???? wrote: > In /etc/rc.d/rc.sysinit, > there's "mount -a -n -t nonfs,nfs4,smbfs,ncpfs,cifs,gfs,gfs2i,glusterfs -O > no_netdev". > > > I have other same type servers. And on other servers with same /etc/fstsb, > file system is correct. > There's no difference between normal server's rc.sysinit and this problem > server's