dolvm invoked, but LVM binary not available

Message

n8V8r · Post by **n8V8r** » Sat Sep 14, 2019 6:36 pm

booting up with minimal installation CD (09 Sept '19)

gentoo dolvm

it prints

dolvm invoked, but LVM binary not available! skipping LVM volume group activiation!

Which seems strange that the binary is reported as not being available whilst there is an explicit invocation command present. Is this to be expected?

madurani · Post by **madurani** » Fri Oct 04, 2019 11:37 am

Probably LVM package/tool missing. You should be boot your pc from install medium, chroot new installation and emerge LVM package via: emerge -av sys-fs/lvm2

xanderal · Post by **xanderal** » Fri Oct 04, 2019 12:29 pm

Hej n8V8r,
I just checked and I can reproduce your issue with my minimal image (june 2019).
Before trying to fix that, let me ask: Why do you need that?
I did my installation with a couple LVs using just the standard kernel without changing parameters. I did have some error messages later during grub config, but it still worked.
So assuming you want to use lvm in your installation I would say just do the installation, it will probably just work.
EDIT: Also for repairing purposes. I can use the old image to chroot into my install, everything works.
So basically: Cool if you want to improve gentoo but then maybe file a bug.
If you just want to install using lvm, you most likely won't need to boot the minimal image with dolvm (again, I didn't).

Post by Hu » Sat Oct 05, 2019 12:19 am

n8V8r wrote:booting up with minimal installation CD (09 Sept '19)
Code: Select all
gentoo dolvm
it prints
dolvm invoked, but LVM binary not available! skipping LVM volume group activiation!
Which seems strange that the binary is reported as not being available whilst there is an explicit invocation command present. Is this to be expected?

It is reported as unavailable because you explicitly invoked it, and the system was not able to satisfy your request. Is the minimal CD documented to support this? If yes, then it is a bug that should be fixed, either by changing the documentation or by adding LVM. If no, then it is a convenience that the system advised you that it cannot do as you ask.

jlpoole · Post by **jlpoole** » Wed Jan 11, 2023 2:09 am

I have run into a similar problem in the context of creating a Gentoo VM in Xen running on Gentoo. I'm posting to this topic because a search for "dolvm invoked, but LVM binary not available" provides very few results, so this looks to be an unusual error condition.

Background:

I have had a Gentoo Xen hypervisor running Gentoo VMs for over a year with no problem assigning LVM logical volumes for various VMs. My Xen configuration files for a Gentoo VM environment had been working fine. Then I started having problems with Qemu in trying to build a Raspberry Pi 64 image (chrooting in the VM to aarch64) so I upgraded the kernel, xen and xentools. Now I cannot launch a VM for Gentoo because LVM is not found and/or working in the guest start-up.

My kernel is used both by Dom0 [hermes] and the Gentoo VMs.

Code: Select all

hermes /etc/xen # uname -a
Linux hermes 5.15.80-gentoo-x86_64 #1 SMP Sun Jan 8 17:40:29 PST 2023 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux
hermes /etc/xen #

I use LVM and in DOM0 the group, /dev/vg0, appears and the /dev/mapper has all the names appearing. However, when I try to launch a new Gentoo VM, the assignment of an LVM logical volume no longer works. I altered by kernel command line and found if I place "dolvm" immediately after the volume, I get a more descriptive error message. Earlier I was just getting a message to the effect the drive could not be found and no mention of lvm. At least now, a warning "LVM binary not available" gives me further insight into the problem.

Here's the error message from an "xl create gentoo1.conf -c" command:

Code: Select all

    [    3.267850] Write protecting the kernel read-only data: 22528k
    [    3.282598] Freeing unused kernel image (text/rodata gap) memory: 2036K
    [    3.283555] Freeing unused kernel image (rodata/data gap) memory: 1072K
    [    3.597873] x86/mm: Checked W+X mappings: passed, no W+X pages found.
    [    3.597898] rodata_test: all tests were successful
    [    3.597910] Run /init as init process
    >> Genkernel 4.2.6 (2023-01-09 02:34:08 UTC). Linux kernel 5.15.80-gentoo-x86_64
    >> Activating udev ...
    !! dolvm invoked but LVM binary not available; Skipping LVM volume group activation ...
    >> Determining root device (trying /dev/xvda3) ........
    !! Block device /dev/xvda3 is not a valid root device ...
    !! Could not find the root block device in /dev/xvda3.
    !! Please specify another value or:
    !! - press Enter for the same
    !! - type "shell" for a shell
    !! - type "q" to skip ...
    root block device(/dev/xvda3) ::

I end up returning to the DomO console and then executing an "xl destroy [ID]".

I've entered the BusyBox shell and searched /dev and nothing shows up, so the LVM maps are not present.

My Xen packages:

Code: Select all

    hermes /etc/xen # date; eix -I xen
    Tue Jan 10 16:55:18 PST 2023
    [I] app-emulation/xen
         Available versions:  4.15.4_pre1^st ~4.15.4_pre2^st 4.15.4^st ~4.16.3_pre^st ~4.16.3_pre1^st {+boot-symlinks debug efi flask}
         Installed versions:  4.15.4^st(19:22:28 01/08/23)(-debug -efi -flask)
         Homepage:            https://xenproject.org
         Description:         The Xen virtual machine monitor

    [I] app-emulation/xen-tools
         Available versions:  4.15.4_pre1-r1(0/4.15)^t ~4.15.4_pre2-r1(0/4.15)^t 4.15.4-r1(0/4.15)^t ~4.16.3_pre-r1(0/4.16)^t ~4.16.3_pre1-r1(0/4.16)^t {api debug doc +hvm +ipxe lzma ocaml ovmf pygrub python +qemu +qemu-traditional +rombios screen sdl selinux static-libs system-ipxe system-qemu system-seabios systemd zstd PYTHON_SINGLE_TARGET="python3_8 python3_9 python3_10 python3_11"}
         Installed versions:  4.15.4-r1(0/4.15)^t(19:34:15 01/08/23)(hvm ipxe qemu qemu-traditional rombios sdl -api -debug -doc -lzma -ocaml -ovmf -pygrub -python -screen -selinux -static-libs -system-ipxe -system-qemu -system-seabios PYTHON_SINGLE_TARGET="python3_10 -python3_8 -python3_9")
         Homepage:            https://xenproject.org
         Description:         Xen tools including QEMU and xl

    Found 2 matches
    hermes /etc/xen #

Sample VM configuration file:

Code: Select all

    hermes /etc/xen # cat gentoo1.conf
    #
    # 1/14/2022 jlpoole  first VM for gentoo1
    # based on https://wiki.gentoo.org/wiki/Xen#Networking_on_domains
    #
    kernel = "/boot/vmlinuz-5.15.80-gentoo-x86_64"
    ramdisk = "/boot/initramfs-5.15.80-gentoo-x86_64.img"
    #bootargs = "dolvm"
    #bootargs = "root=/dev/sda3"
    #memory = 16384
    memory = 8192
    vcpus  = 2
    name   = "gentoo1"
    #disk   = ['/dev/mapper/vg0-gentoo1,xvda3,w'] # Map the disk image to the virtual /dev/sda3
    disk  = ['/dev/mapper/vg0-gentoo1,,xvda3,w']  # 1/9/2023 above was not working, so try this

    root   = "/dev/xvda3 ro dolvm"
    #
    # 1/10/23 cmdline supplant root command
    #
    #cmdline = "/dev/xvda3 dolvm ro"
    #vif    = ['bridge=br0'] # set the bridge name to br0 (see later), otherwise xen will use xenbr0

    #
    #  Hermes has [redacted]
    # [redacted]
    #
    vif = ['mac=[redacted],bridge=xenbr0']

    hermes /etc/xen #

Activating '#bootargs = "dolvm"' does not change anything.

Here's what I have for lvm:

Code: Select all

hermes /etc/xen # eix -I lvm
[I] sys-devel/llvm
     Available versions:
     (13)   13.0.1^t
     (14)   14.0.6-r2^t
     (15)   15.0.5(15/15)^t 15.0.6(15/15)^t ~15.0.6-r1(15/15)^t **15.0.6.9999(15/15)*l^t
     (16)   ~*16.0.0_pre20221217(16/16.0.0_pre20221217)^t ~*16.0.0_pre20221226(16/16.0.0_pre20221226)^t ~*16.0.0_pre20230101(16/16.0.0_pre20230101)^t **16.0.0.9999(16/16.0.0.9999)*l^t
       {+binutils-plugin debug doc exegesis libedit +libffi ncurses test verify-sig xar xml z3 zstd ABI_MIPS="n32 n64 o32" ABI_S390="32 64" ABI_X86="32 64 x32" LLVM_TARGETS="AArch64 AMDGPU ARC ARM AVR BPF CSKY DirectX Hexagon Lanai LoongArch M68k MSP430 Mips NVPTX PowerPC RISCV SPIRV Sparc SystemZ VE WebAssembly X86 XCore Xtensa"}
     Installed versions:  15.0.6(15/15)^t(20:37:25 12/23/22)(binutils-plugin libffi ncurses xml -debug -doc -exegesis -libedit -test -verify-sig -xar -z3 -zstd ABI_MIPS="-n32 -n64 -o32" ABI_S390="-32 -64" ABI_X86="64 -32 -x32" LLVM_TARGETS="AArch64 AMDGPU ARM AVR BPF Hexagon Lanai MSP430 Mips NVPTX PowerPC RISCV Sparc SystemZ VE WebAssembly X86 XCore -ARC -CSKY -DirectX -LoongArch -M68k -SPIRV")
     Homepage:            https://llvm.org/
     Description:         Low Level Virtual Machine

[I] sys-devel/llvm-common
     Available versions:  13.0.1 14.0.6 15.0.5 15.0.6 **15.0.6.9999*l ~*16.0.0_pre20221217 **16.0.0_pre20221226 ~*16.0.0_pre20230101 **16.0.0.9999*l {verify-sig}
     Installed versions:  15.0.6(12:56:22 12/23/22)(-verify-sig)
     Homepage:            https://llvm.org/
     Description:         Common files shared between multiple slots of LLVM

[I] sys-devel/llvm-toolchain-symlinks
     Available versions:
     (14)   ~14-r1
     (15)   15-r1
     (16)   ~*16-r1
       {multilib-symlinks +native-symlinks}
     Installed versions:  15-r1(15)(20:37:47 12/23/22)(native-symlinks -multilib-symlinks)
     Homepage:            https://wiki.gentoo.org/wiki/Project:LLVM
     Description:         Symlinks to use LLVM on binutils-free system

[I] sys-devel/llvmgold
     Available versions:  13-r2 14 15 ~*16
     Installed versions:  15(20:38:00 12/23/22)
     Homepage:            https://llvm.org/
     Description:         LLVMgold plugin symlink for autoloading

[I] sys-fs/lvm2
     Available versions:  2.03.14-r5 2.03.17-r1 {lvm lvm2create-initrd readline sanlock selinux static static-libs systemd thin +udev}
     Installed versions:  2.03.17-r1(13:03:23 01/07/23)(lvm lvm2create-initrd readline udev -sanlock -selinux -static -static-libs -systemd -thin)
     Homepage:            https://sourceware.org/lvm2/
     Description:         User-land utilities for LVM2 (device-mapper) software

Found 5 matches
hermes /etc/xen #

One thing I've noticed, I have other servers on my network which use LVM and at times I've seen on a machine some suggestion that the LVM from another server is being communicated with or tied in. I've not tried to have the LVM traverse multiple machines, but maybe I have that occurring, if it can and the "sharing" is somehow at play?

grknight · Post by **grknight** » Wed Jan 11, 2023 2:57 am

jlpoole wrote:I have run into a similar problem in the context of creating a Gentoo VM in Xen running on Gentoo. I'm posting to this topic because a search for "dolvm invoked, but LVM binary not available" provides very few results, so this looks to be an unusual error condition.

Background:

I have had a Gentoo Xen hypervisor running Gentoo VMs for over a year with no problem assigning LVM logical volumes for various VMs. My Xen configuration files for a Gentoo VM environment had been working fine. Then I started having problems with Qemu in trying to build a Raspberry Pi 64 image (chrooting in the VM to aarch64) so I upgraded the kernel, xen and xentools. Now I cannot launch a VM for Gentoo because LVM is not found and/or working in the guest start-up.

My kernel is used both by Dom0 [hermes] and the Gentoo VMs.
Code: Select all
hermes /etc/xen # uname -a
Linux hermes 5.15.80-gentoo-x86_64 #1 SMP Sun Jan 8 17:40:29 PST 2023 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux
hermes /etc/xen #
I use LVM and in DOM0 the group, /dev/vg0, appears and the /dev/mapper has all the names appearing. However, when I try to launch a new Gentoo VM, the assignment of an LVM logical volume no longer works. I altered by kernel command line and found if I place "dolvm" immediately after the volume, I get a more descriptive error message. Earlier I was just getting a message to the effect the drive could not be found and no mention of lvm. At least now, a warning "LVM binary not available" gives me further insight into the problem.

Here's the error message from an "xl create gentoo1.conf -c" command:
Code: Select all
    [    3.267850] Write protecting the kernel read-only data: 22528k
    [    3.282598] Freeing unused kernel image (text/rodata gap) memory: 2036K
    [    3.283555] Freeing unused kernel image (rodata/data gap) memory: 1072K
    [    3.597873] x86/mm: Checked W+X mappings: passed, no W+X pages found.
    [    3.597898] rodata_test: all tests were successful
    [    3.597910] Run /init as init process
    >> Genkernel 4.2.6 (2023-01-09 02:34:08 UTC). Linux kernel 5.15.80-gentoo-x86_64
    >> Activating udev ...
    !! dolvm invoked but LVM binary not available; Skipping LVM volume group activation ...
    >> Determining root device (trying /dev/xvda3) ........
    !! Block device /dev/xvda3 is not a valid root device ...
    !! Could not find the root block device in /dev/xvda3.
    !! Please specify another value or:
    !! - press Enter for the same
    !! - type "shell" for a shell
    !! - type "q" to skip ...
    root block device(/dev/xvda3) ::

The only reason you see that message is because of specifically adding dolvm to the startup.

Instead, it cannot find the Xen block device. Perhaps you want doload="xenblk" instead of dolvm.

If this is a custom built kernel, then building in the Xen Frontend block device (as * not M) would be beneficial.

jlpoole · Post by **jlpoole** » Fri Jan 13, 2023 4:50 pm

Thank you, grknight.

My recompiled kernel can now see the LVM logical volume containing my root system.

3 points:

1) My kernel was compiled with the additional flag "--lvm", I had not used that option in my prior attempt, but I may have done so months/year ago and not made note to always use the --lvm option:

Code: Select all

01    hermes /usr/src/linux # date; time genkernel --menuconfig --lvm all
02    Thu Jan 12 18:46:19 PST 2023
03    * Gentoo Linux Genkernel; Version 4.2.6
04    * Using genkernel configuration from '/etc/genkernel.conf' ...
05    * Running with options: --menuconfig --lvm all
06
07    * Working with Linux kernel 5.15.80-gentoo-x86_64 for x86_64
08    * Using kernel config file '/etc/kernels/kernel-config-5.15.80-gentoo-x86_64' ...
09    *
10    * Note: The version above is subject to change (depends on config and status of kernel sources).
11
12    * kernel: >> Initializing ...
13    *         >> Running 'make mrproper' ...
14    *         >> Running 'make oldconfig' ...
15    *         >> Invoking menuconfig ...
16    *         >> Compiling 5.15.80-gentoo-x86_64 bzImage ...
17    *         >> Compiling 5.15.80-gentoo-x86_64 modules ...
18    date
19    date
20    *         >> Installing 5.15.80-gentoo-x86_64 modules (and stripping) ...
21    *         >> Generating module dependency data ...
22    *         >> Saving config of successful build to '/etc/kernels/kernel-config-5.15.80-gentoo-x86_64' ...
23
24    * initramfs: >> Initializing ...
25    *         >> Appending devices cpio data ...
26    *         >> Appending base_layout cpio data ...
27    *         >> Appending util-linux cpio data ...
28    *         >> Appending eudev cpio data ...
29    *         >> Appending devicemanager cpio data ...
30    *         >> Appending auxiliary cpio data ...
31    *         >> Appending busybox cpio data ...
32    *         >> Appending lvm cpio data ...
33    *         >> Appending modprobed cpio data ...
34    *         >> Appending modules cpio data ...
35    *         >> Deduping cpio ...
36    *         >> Pre-generating initramfs' /etc/ld.so.cache ...
37    *         >> Compressing cpio data (.xz) ...
38
39    * Kernel compiled successfully!
40    *
41    * --no-bootloader set; Skipping bootloader update ...
42    *
43    * Required kernel parameter:
44    *
45    *       root=/dev/$ROOT
46    *
47    * Where $ROOT is the device node for your root partition as the
48    * one specified in /etc/fstab
49
50    * If you require Genkernel's hardware detection features, you MUST
51    * tell your bootloader to use the provided initramfs file '/boot/initramfs-5.15.80-gentoo-x86_64.img'.
52
53    * WARNING... WARNING... WARNING...
54    * Additional kernel parameters that *may* be required to boot properly:
55    * - Add "dolvm" for LVM support
56
57    * Do NOT report kernel bugs as genkernel bugs unless your bug
58    * is about the default genkernel configuration...
59    *
60    * Make sure you have the latest ~arch genkernel before reporting bugs.
61
62    real    85m37.220s
63    user    377m43.523s
64    sys     111m7.604s
65    hermes /usr/src/linux # date
66    Thu Jan 12 20:11:56 PST 2023
67

2) My kernel was configured with these XEN settings:

Code: Select all

01    hermes /usr/src/linux # date; ls -la .config; cat .config |grep -i xen
02    Fri Jan 13 08:25:50 PST 2023
03    -rw-r--r-- 1 root root 232078 Jan 12 18:51 .config
04    CONFIG_XEN=y
05    CONFIG_XEN_PV=y
06    CONFIG_XEN_512GB=y
07    CONFIG_XEN_PV_SMP=y
08    CONFIG_XEN_PV_DOM0=y
09    CONFIG_XEN_PVHVM=y
10    CONFIG_XEN_PVHVM_SMP=y
11    CONFIG_XEN_PVHVM_GUEST=y
12    CONFIG_XEN_SAVE_RESTORE=y
13    CONFIG_XEN_DEBUG_FS=y
14    CONFIG_XEN_PVH=y
15    CONFIG_XEN_DOM0=y
16    CONFIG_PCI_XEN=y
17    # CONFIG_KVM_XEN is not set
18    CONFIG_NET_9P_XEN=m
19    CONFIG_XEN_PCIDEV_FRONTEND=m
20    CONFIG_XEN_BLKDEV_FRONTEND=y
21    CONFIG_XEN_BLKDEV_BACKEND=y
22    CONFIG_XEN_SCSI_FRONTEND=m
23    CONFIG_NETXEN_NIC=m
24    CONFIG_XEN_NETDEV_FRONTEND=y
25    CONFIG_XEN_NETDEV_BACKEND=y
26    CONFIG_INPUT_XEN_KBDDEV_FRONTEND=m
27    CONFIG_HVC_XEN=y
28    CONFIG_HVC_XEN_FRONTEND=y
29    # CONFIG_TCG_XEN is not set
30    CONFIG_XEN_WDT=m
31    # CONFIG_DRM_XEN_FRONTEND is not set
32    CONFIG_XEN_FBDEV_FRONTEND=y
33    # CONFIG_SND_XEN_FRONTEND is not set
34    CONFIG_MMC_SDHCI_XENON=m
35    # Xen driver support
36    CONFIG_XEN_BALLOON=y
37    # CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set
38    CONFIG_XEN_MEMORY_HOTPLUG_LIMIT=512
39    CONFIG_XEN_SCRUB_PAGES_DEFAULT=y
40    CONFIG_XEN_DEV_EVTCHN=m
41    CONFIG_XEN_BACKEND=y
42    CONFIG_XENFS=m
43    CONFIG_XEN_COMPAT_XENFS=y
44    CONFIG_XEN_SYS_HYPERVISOR=y
45    CONFIG_XEN_XENBUS_FRONTEND=y
46    CONFIG_XEN_GNTDEV=m
47    CONFIG_XEN_GRANT_DEV_ALLOC=m
48    # CONFIG_XEN_GRANT_DMA_ALLOC is not set
49    CONFIG_SWIOTLB_XEN=y
50    CONFIG_XEN_PCIDEV_BACKEND=m
51    CONFIG_XEN_PVCALLS_FRONTEND=y
52    # CONFIG_XEN_PVCALLS_BACKEND is not set
53    CONFIG_XEN_SCSI_BACKEND=m
54    CONFIG_XEN_PRIVCMD=m
55    CONFIG_XEN_ACPI_PROCESSOR=m
56    # CONFIG_XEN_MCE_LOG is not set
57    CONFIG_XEN_HAVE_PVMMU=y
58    CONFIG_XEN_EFI=y
59    CONFIG_XEN_AUTO_XLATE=y
60    CONFIG_XEN_ACPI=y
61    CONFIG_XEN_SYMS=y
62    CONFIG_XEN_HAVE_VPMU=y
63    CONFIG_XEN_UNPOPULATED_ALLOC=y
64    # end of Xen driver support
65    hermes /usr/src/linux #

3) My guest configuration file:

Code: Select all

01    hermes /etc/xen # date; ls -la gentoo1.conf ;cat gentoo1.conf
02    Fri Jan 13 08:32:27 PST 2023
03    -rw-r--r-- 1 root root 886 Jan 12 20:15 gentoo1.conf
04    #
05    # 1/14/2022 jlpoole  first VM for gentoo1
06    # based on https://wiki.gentoo.org/wiki/Xen#Networking_on_domains
07    #
08    kernel = "/boot/vmlinuz-5.15.80-gentoo-x86_64"
09    ramdisk = "/boot/initramfs-5.15.80-gentoo-x86_64.img"
10    bootargs = "dolvm"
11    #bootargs = "doload=xenblk"
12    #bootargs = "root=/dev/sda3"
13    #memory = 16384
14    memory = 8192
15    vcpus  = 2
16    name   = "gentoo1"
17    #disk   = ['/dev/mapper/vg0-gentoo1,xvda3,w'] # Map the disk image to the virtual /dev/sda3
18    disk  = ['/dev/mapper/vg0-gentoo1,,xvda3,w']  # 1/9/2023 above was not working, so try this
19
20    root   = "/dev/xvda3 dolvm ro"
21    #
22    # 1/10/23 cmdline supplant root command
23    #
24    #cmdline = "/dev/xvda3 dolvm ro"
25    #vif    = ['bridge=br0'] # set the bridge name to br0 (see later), otherwise xen will use xenbr0
26
27    #
28    #  Hermes has 00:16:3e:11:12:XX
29    # ...11:12:01 = gentoo1 = Production = 192.168.XX.XX (pfSense)
30    #
31    vif = ['mac=00:16:3e:11:12:01,bridge=xenbr0']
32
33    hermes /etc/xen #

Also, I studied the genkernel options at https://gitweb.gentoo.org/proj/genkerne ... 02f5eac3a8
and searched using "lvm". That's when I learned when I compile with genkernel, I could send it a flag --lvm.

Moreover, at the end of the compile, I was warned @line 55 (see kernel session above) to use "dolvm". See also @line 32 (see kernel session above) "Appending lvm cpio data...".

Here's the point in the VM boot-up where the logical volumes are scanned and found:

Code: Select all

001    hermes /etc/xen # xl create gentoo1.conf -c
002    Parsing config from gentoo1.conf
003    [    0.000000] Linux version 5.15.80-gentoo-x86_64 (root@hermes) (x86_64-pc-linux-gnu-gcc (Gentoo 11.3.1_p20221209 p3) 11.3.1 20221209, GNU ld (Gentoo 2.39 p5) 2.39.0) #1 SMP Thu Jan 12 18:51:26 PST 2023
004    [    0.000000] Command line: root=/dev/xvda3 dolvm ro
...
052    [    1.473514] Booting kernel on Xen
053    [    1.473516] Xen version: 4.15.4 (preserve-AD)

060    [    1.479073] Kernel command line: root=/dev/xvda3 dolvm ro
061    [    1.479118] Unknown kernel command line parameters "dolvm", will be passed to user space.
...

175    [    1.962552] Trying to unpack rootfs image as initramfs...

201    [    2.063671] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
202    [    2.063712] device-mapper: uevent: version 1.0.3
203    [    2.063793] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
204    [    2.068538] device-mapper: multipath round-robin: version 1.2.0 loaded
205    [    2.068552] device-mapper: multipath queue-length: version 0.2.0 loaded
206    [    2.068562] device-mapper: multipath service-time: version 0.3.0 loaded
207    [    2.068593] device-mapper: dm-log-userspace: version 1.3.0 loaded
...
214    [    2.069227] xen_netfront: backend supports XDP headroom
215    [    2.077676] blkfront: xvda3: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled; bounce buffer: enabled

276    [    3.425488] Freeing unused kernel image (text/rodata gap) memory: 2036K
277    [    3.426815] Freeing unused kernel image (rodata/data gap) memory: 1044K
278    [    3.736024] x86/mm: Checked W+X mappings: passed, no W+X pages found.
279    [    3.736046] rodata_test: all tests were successful
280    [    3.736063] Run /init as init process
281    >> Genkernel 4.2.6 (2023-01-13 03:45:07 UTC). Linux kernel 5.15.80-gentoo-x86_64
282    >> Activating udev ...
283    >> Scanning for volume groups ...
284      Reading all physical volumes.  This may take a while...
285    >> Activating volume groups ...
286    >> Determining root device (trying /dev/xvda3) ...
287    >> Root device detected as /dev/xvda3!
288    >> Mounting /dev/xvda3 as root ...
289    >> Using mount -t ext4 -o ro /dev/xvda3 /newroot
290    >> Restoring console log level (7) ...
291    >> Switching to real root: switch_root /newroot /sbin/init
292    INIT: version 3.05 booting
293
294       OpenRC 0.45.2 is starting up Gentoo Linux (x86_64) [XENU]
...

dolvm invoked, but LVM binary not available

dolvm invoked, but LVM binary not available

Re: dolvm invoked, but LVM binary not available

Re: dolvm invoked, but LVM binary not available

Resolved