Discuss November 2023

discuss@lists.centos.org

7 participants
9 discussions

Problems with CentOS 8 kickstart
by Hooton, Gerard 23 Jun '25

23 Jun '25

Hi All, I am having problems with a kickstart install of CentOS 8 When I try to do a completely automated install using PXE/UEFI it get to the point where it reads the kickstart config file. Then I see the following message "kickstart install Started cancel waiting for multipath siblings for nvme0n1" This is what I have in the kickstart file # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel autopart --nohome --type=lvm --fstype=xfs ================ When I install from a USB drive it works OK and I have the following in /dev/disk/by-id lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810 -> ../../nvme0n1 lrwxrwxrwx. 1 root root 13 Jul 5 10:28 nvme-eui.002538b11102f46d -> ../../nvme0n1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part3 -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 lvm-pv-uuid-5Dg4mg-saHa-hJJ6-n5a8-MxBS-gdFi-5jPoNn -> ../../nvme0n1p3 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part2 UNG_MZVL2512HCJQ-0-> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part2 -> ../../nvme0n1p2 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part2 -> ../../nvme0n1p2 drwxr-xr-x. 2 root root 400 Jul 5 10:28 . lrwxrwxrwx. 1 root root 15 Jul 5 10:28 wwn-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-SAMSUNG_MZVL2512HCJQ-00BL7_S64KNE0R161810-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 15 Jul 5 10:28 nvme-eui.002538b11102f46d-part1 -> ../../nvme0n1p1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKtEdtLjwJQyIdxJcSvPv8TEAjwYGMv6yU -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkKAooqrczySYJyiHvUAUji9oScPN2cVi7J -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-swap -> ../../dm-1 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-root -> ../../dm-0 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-uuid-LVM-qQok4M7AOo1TxZZ42GwZcbuVNBs0hnkK5HZXbR2ow5xKGuD7jVe4UPzZm2qRLLXI -> ../../dm-2 lrwxrwxrwx. 1 root root 10 Jul 5 11:07 dm-name-cs_uews027-home -> ../../dm-2 It's looks like that I am not doing the disk drive stuff in the config file correctly. -- Gerard Hooton. Senior Technical Officer School of Engineering. University College Cork. College Road. Cork. Ireland. Loc8: WDR-04-60G Tel: +353 21 4902296 Mobile: +353 852813491

3 7

Issues booting centos7 [dracut is failing to enable centos/root, centos/swap LVs]
by Yannis Milios 02 Feb '25

02 Feb '25

Hello, I'm having a strange problem booting a new centos7 installation. Below some background on this. [I have attached the tech details at the bottom of this message] I started a new CentOS7 installation on a VM, so far all good, o/s boots fine. Then I decided to increase VM disk size (initially was 10G) to 13G. Powered off the VM, increased the vhd via the hypervisor, booted from CentOS livecd, selected "recover my centos installation". Then I used the following sequence of commands to make the new vhd size "visible" to the o/s ... - ran fdisk /dev/sda and deleted partition 2. (This is the LVM partition where the o/s is stored. The first partition is /boot [xfs] partition *non lvm*.) - created a new partition with same starting sector as before deleting it, but a different ending sector (to reflect to the increased space). - set partition type to 8e (lvm), saved settings and exit. - ran pvresize and lvresize to make new space visible to the o/s.All good, I can see the space increase on 'lvdisplay centos/root'. - ran 'mount /dev/mapper/centos-root /mnt/root' to temporarily mount the o/s partition. - ran 'xfs_growfs /mnt/root' to resize the o/s fs to the new size. It was successful and I could actually chroot to the o/s and verify new disk size. - rebooted and tried to boot from hdd this time. Grub menu shows up and loads default kernel (3.10.0-862.9.1.el7.x86_64). - after initial kernel boot up process, booting continues to initrd and then it's where the problem starts... - looks like dracut has issues locating/enabling /dev/mapper/centos-root (lv) and as a result it cannot boot to the 'real' root fs (/). - while in dracut shell, I execute the following command sequence: 1. lvm lvchange -ay /dev/centos/root 2. lvm lvchange -ay /dev/centos/swap 3. ln -s /dev/mapper/centos-root /dev/root 4. exit ...and the o/s boots fine...so looks like the pv,vg,lv is detected properly while in initrd, but somehow dracut has difficulties enabling the root,swap LVs ? - While in o/s, I rebuild initrd by using: 'dracut -f -v -a lvm' Note, I have to use '-a lvm' as for some reason, if don't, the lvm utils (lvm,lvm_scan) are not being included to the initrd, not sure why this happens. After rebooting, same thing happens, I have to manually boot the system via dracut shell. I'm a bit stuck at this point, any clues what I'm doing wrong in here ? As I previously said, this is a new installation, so I could simply reinstall the whole thing, but I would rather try to find out some answer to why is this happening ... :-) [curiosity] Some additional details: ================== I've attached /run/initramfs/rdsosreport.txt file [generated while in inird] here: https://privatebin.net/?fdc4052c0c402884#gdB/QYR3IeR55SxUbjfrkZPQfJ7jMxiUxq… o/s ver=CentOS Linux release 7.5.1804 (Core) [root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 13G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 0 12.5G 0 part ├─centos-root 253:0 0 11.5G 0 lvm / └─centos-swap 253:1 0 1G 0 lvm [SWAP] [root@localhost ~]# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rd.shell rhgb" GRUB_DISABLE_RECOVERY="true"

4 11

Puppet from EPEL ?
by lejeczek 01 Dec '23

01 Dec '23

Hi guys. It's a bit confusing - I'm only about to start a foray into it - whether _puppet_ from EPEL is the whole-lot-server? From the look of included _puppet.service_ - this package is only agent and if not why no server bits? Looking at what comes with Puppet's own repo - those appear quite different, packages. do. How do you install/get your _puppets_? thanks, L.

2 1

possible LVM corruption?
by Gordon Messmer 28 Nov '23

28 Nov '23

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 'vm_ipa-data_rimage_0'. grub2-probe: error: ../grub-core/kern/disk.c:236:disk `lvmid/uhx5FA-RmdV-cPYP-ELEA-pUrn-FfHl-M2RBEV/JQKCwn-RhKX-ek4u-VJxX-ja9j-rtAD-fVUBGc' not found. "vgdisplay --verbose" output includes: --- Volume group --- VG Name VolGroup System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 2053 VG Access read/write VG Status resizable MAX LV 0 Cur LV 82 Open LV 18 Max PV 0 Cur PV 2 Act PV 2 VG Size <7.28 TiB PE Size 32.00 MiB Total PE 238392 Alloc PE / Size 163262 / 4.98 TiB Free PE / Size 75130 / 2.29 TiB VG UUID uhx5FA-RmdV-cPYP-ELEA-pUrn-FfHl-M2RBEV --- Logical volume --- LV Path /dev/VolGroup/vm_ipa-data LV Name vm_ipa-data VG Name VolGroup LV UUID YSw2fz-e4cA-7i86-4ssj-5b49-7572-uNWm2p LV Write Access read/write LV Creation host, time ascension, 2023-10-26 21:31:26 -0700 LV Status available # open 1 LV Size 5.00 GiB Current LE 160 Mirrored volumes 2 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:197 # lvs -a | grep vm.ipa.data vm_ipa-data VolGroup rwi-aor--- 5.00g 100.00 [vm_ipa-data_rimage_0] VolGroup gwi-aor--- 5.00g [vm_ipa-data_rimage_0_iorig] 100.00 [vm_ipa-data_rimage_0_imeta] VolGroup ewi-ao---- 96.00m [vm_ipa-data_rimage_0_iorig] VolGroup -wi-ao---- 5.00g [vm_ipa-data_rimage_1] VolGroup gwi-aor--- 5.00g [vm_ipa-data_rimage_1_iorig] 100.00 [vm_ipa-data_rimage_1_imeta] VolGroup ewi-ao---- 96.00m [vm_ipa-data_rimage_1_iorig] VolGroup -wi-ao---- 5.00g [vm_ipa-data_rmeta_0] VolGroup ewi-aor--- 32.00m [vm_ipa-data_rmeta_1] VolGroup ewi-aor--- 32.00m

1 0

Apps moving to laptop display when switching KVM
by Michael B Allen 27 Nov '23

27 Nov '23

So I installed CentOS Stream 9 on a new Lenovo T14 Gen 4 Intel. I have a 4x1 HDMI KVM with external monitor. When switching the KVM, apps move between displays / workspaces in erratic ways. More specifically, when switching out, apps on the external display usually move to the laptop display. This sorta makes sense for a laptop with an external display. When the external display is disconnected, you want to have access to the apps. But for a KVM, the desired behavior is that the apps do NOT move. When switching back, I want all apps (terminals) to be where they were when I switched out. After much searching, I have found NO discussion of this issue. Is this a scenario that is even supposed to work? The KVM worked perfectly with the Windows 11 install that come with the machine (apps on the external display did not move when switching the KVM). Questions: Is there a GNOME window manager configuration that does not move apps when it senses the HDMI connection has changed? I actually had this mostly working with a Dell laptop running a RHEL 9 clone and selecting Xorg on the GDM screen. Apps were not moved when switching out (although depending on particular circumstances they could when switching back). Where should I be asking about this? A freedesktop.org list? Where is the code that moves windows in reaction to a change in displays? Currently the only way to reliably switch the KVM without all of the apps loosing their positions is to just suspend the machine before and resume after.

1 1

CentOS box images at Vagrant Cloud give 404
by Kees Bakker 22 Nov '23

22 Nov '23

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on cloud.centos.org. Do we know who is maintaining this centos account at Vagrant Cloud? Can someone update the centos entries overthere? [1] https://app.vagrantup.com/centos/ [2] https://app.vagrantup.com/centos/boxes/stream9/versions/20230727.1 -- Kees Bakker

1 0

emulate ARM ?
by lejeczek 16 Nov '23

16 Nov '23

Hi guys. How do you emulate AMR arch - I mean, with what's in distro &| SIGs repos as oppose to do-it-yourself? many thanks, L.

2 3

can I convert a linear thin pool to raid1?
by Gordon Messmer 09 Nov '23

09 Nov '23

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 VolGroup/vm_pool --yes Operation not permitted on LV VolGroup/vm_pool type thinpool. Is it sufficient to simply convert the tdata and tmeta LVs to raid1 type? Should I also convert lvol0_pmspare? Is there anything else I should consider? # lvs VolGroup/vm_pool VolGroup/vm_pool_tmeta VolGroup/vm_pool_tdata VolGroup/lvol0_pmspare LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert [lvol0_pmspare] VolGroup ewi-a----- 128.00m vm_pool VolGroup twi-aotz-- 200.00g 12.83 15.93 [vm_pool_tdata] VolGroup Twi-ao---- 200.00g [vm_pool_tmeta] VolGroup ewi-ao---- 128.00m

1 0

selinux blocks rsync client in systemd service
by Kenneth Porter 04 Nov '23

04 Nov '23

I'm trying to slurp a CentOS 7's filesystem to another CentOS 7 system using rsyncd on the supplying side and rsync running as a client in a timer unit on the client side. My backup script on the backup system runs fine from the command line. When run from a systemd timer unit, rsync sends nothing to the systemd log and I see a denial in the audit log for a Unix domain socket in init_t context. I'm guessing it's trying to write to stdout which is getting redirected to systemd's log. The service unit file has StandardOutput=syslog in order to capture the list of files backed up. The following selinux rule seems to fix this: allow rsync_t init_t:unix_stream_socket { getattr read write }; I also found it necessary to add --no-devices and --no-specials to my backup script, but I can live with that. A few devices show up in chroots and postfix has some sockets in its package. Those are easily recreated if I need to do a restore. So is this selinux rule an oversight? Should there be an rsync bool for it? Or was this fixed in a more recent version of systemd?

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2023