Update to Kernel 5.10.52-1 causes LVM to partly fail

I upgraded from kernel 5.4 to 5.10 (both latest) and now I’m experiencing problems with LVM. As a result, I have to manually activate the LVs under one VG (media). All other LVs are activated during boot as they should be. Here my drives:

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 10.9T 0 disk
└─sda1 8:1 1 10.9T 0 part
└─md0 9:0 0 10.9T 0 raid1
├─photos-photo_stripe 254:22 0 5.7T 0 lvm
└─photos-tmp_stripe 254:23 0 800G 0 lvm
sdb 8:16 1 931.5G 0 disk
└─sdb1 8:17 1 931.5G 0 part
├─vmvg-centos8 254:6 0 50G 0 lvm
├─vmvg-linuxmint 254:7 0 50G 0 lvm
├─vmvg-opensuse15.1 254:8 0 40G 0 lvm
├─vmvg-worker2 254:9 0 40G 0 lvm
├─vmvg-worker1 254:10 0 40G 0 lvm
├─vmvg-worker3 254:11 0 40G 0 lvm
├─vmvg-worker4 254:12 0 40G 0 lvm
├─vmvg-ubuntu1804 254:13 0 40G 0 lvm
├─vmvg-pop_os20 254:14 0 25G 0 lvm
├─vmvg-debian10 254:15 0 20G 0 lvm
└─vmvg-ubuntu-real 254:16 0 20G 0 lvm
├─vmvg-ubuntu 254:17 0 20G 0 lvm
└─vmvg-ubuntusnap 254:19 0 20G 0 lvm
sdc 8:32 1 3.6T 0 disk
└─sdc1 8:33 1 3.6T 0 part
└─media-photo_raw 254:21 0 2.7T 0 lvm
sdd 8:48 1 3.6T 0 disk
└─sdd1 8:49 1 3.6T 0 part
└─media-movies 254:20 0 3.4T 0 lvm /run/timeshift/backup
sde 8:64 1 10.9T 0 disk
└─sde1 8:65 1 10.9T 0 part
└─md0 9:0 0 10.9T 0 raid1
├─photos-photo_stripe 254:22 0 5.7T 0 lvm
└─photos-tmp_stripe 254:23 0 800G 0 lvm
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 465.8G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
└─nvme0n1p2 259:2 0 465.3G 0 part
├─host-swap 254:0 0 16G 0 lvm [SWAP]
├─host-root 254:1 0 30G 0 lvm /
├─host-home 254:2 0 150G 0 lvm /home
└─host-data 254:4 0 100G 0 lvm /media/heiko/data
nvme1n1 259:3 0 931.5G 0 disk
└─nvme1n1p1 259:4 0 931.5G 0 part
├─vmvg-win10 254:3 0 270G 0 lvm
├─vmvg-workdrive 254:5 0 400G 0 lvm
└─vmvg-ubuntusnap-cow 254:18 0 15.8G 0 lvm
└─vmvg-ubuntusnap 254:19 0 20G 0 lvm

After the upgrade to kernel 5.10, at first the vmvg (VG) LVs on drive sdb1 didn’t show up. I had to activate them manually. Somehow I managed to fix that deleting some remnant thin-provisioned LVs that I didn’t need.

Now, when I boot, the two LVs under “media” (VG) are not auto-activated. I need to manually activate using:
vgchange -aay media

Anyway, it’s lost at the next boot.

Here the relevant messages:

journalctl -xb | grep lvm2
Jul 23 20:07:12 manjaro systemd[1]: Created slice Slice /system/lvm2-pvscan.
Jul 23 20:07:13 manjaro systemd[1]: lvm2-pvscan@8:17.service: Main process exited, code=exited, status=5/NOTINSTALLED
░░ An ExecStart= process belonging to unit lvm2-pvscan@8:17.service has exited.
Jul 23 20:07:13 manjaro systemd[1]: lvm2-pvscan@8:17.service: Failed with result 'exit-code'.
░░ The unit lvm2-pvscan@8:17.service has entered the 'failed' state with result 'exit-code'.
░░ Subject: A stop job for unit lvm2-pvscan@8:17.service has finished
░░ A stop job for unit lvm2-pvscan@8:17.service has finished.
Jul 23 20:07:13 manjaro audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=lvm2-pvscan@8:17 comm="systemd" exe="/init" hostname=? addr=? terminal=? res=failed'
░░ Subject: A start job for unit lvm2-pvscan@8:33.service has begun execution
░░ A start job for unit lvm2-pvscan@8:33.service has begun execution.
░░ Subject: A start job for unit lvm2-pvscan@8:49.service has begun execution
░░ A start job for unit lvm2-pvscan@8:49.service has begun execution.
Jul 23 20:07:13 woody systemd[1]: lvm2-pvscan@8:33.service: Main process exited, code=killed, status=15/TERM
Jul 23 20:07:13 woody systemd[1]: lvm2-pvscan@8:33.service: Failed with result 'signal'.
Jul 23 20:07:13 woody systemd[1]: lvm2-pvscan@8:49.service: Main process exited, code=killed, status=15/TERM
Jul 23 20:07:13 woody systemd[1]: lvm2-pvscan@8:49.service: Failed with result 'signal'.
Jul 23 20:07:13 woody audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=lvm2-pvscan@8:33 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jul 23 20:07:13 woody audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=lvm2-pvscan@8:49 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Booting to kernel 5.4 solves the issues.

I found this somewhat dated Arch Linux bug report: https://bugs.archlinux.org/task/57275. Haven’t tried aqua’s workaround yet. Wanted to see if anyone here experienced similar issues with LVM.

For completeness, here the inxi output:

inxi --admin --verbosity=7 --filter --no-host --width
System:
  Kernel: 5.10.52-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 root=/dev/mapper/host-root 
  rw quiet apparmor=1 security=apparmor udev.log_priority=3 amd_iommu=on 
  amd_iommu=pt default_hugepagesz=1G hugepagesz=1G hugepages=48 
  vfio-pci.ids=10de:1e84,10de:10f8,10de:1ad8,10de:1ad9 
  Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm 4.16.1 
  dm: LightDM 1.30.0 Distro: Manjaro Linux base: Arch Linux 
Machine:
  Type: Desktop System: Gigabyte product: X570 AORUS PRO v: -CF serial: N/A 
  Mobo: Gigabyte model: X570 AORUS PRO serial: N/A 
  UEFI: American Megatrends LLC. v: F33 date: 05/21/2021 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 2S 
  serial: <filter> charge: 100% (should be ignored) rechargeable: yes 
  status: Discharging 
  Device-2: hidpp_battery_1 
  model: Logitech K780 Multi-Device Wireless Keyboard serial: <filter> 
  charge: 100% (should be ignored) rechargeable: yes status: Discharging 
Memory:
  RAM: total: 62.79 GiB used: 50.53 GiB (80.5%) 
  Array-1: capacity: 128 GiB slots: 4 EC: None max-module-size: 32 GiB 
  note: est. 
  Device-1: DIMM 0 size: No Module Installed 
  Device-2: DIMM 1 size: 32 GiB speed: 3200 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK64GX4M2E3200C16 serial: N/A 
  Device-3: DIMM 0 size: No Module Installed 
  Device-4: DIMM 1 size: 32 GiB speed: 3200 MT/s type: DDR4 
  detail: synchronous unbuffered (unregistered) bus-width: 64 bits 
  total: 64 bits manufacturer: Corsair part-no: CMK64GX4M2E3200C16 serial: N/A 
CPU:
  Info: 12-Core model: AMD Ryzen 9 3900X socket: AM4 bits: 64 type: MT MCP 
  arch: Zen 2 family: 17 (23) model-id: 71 (113) stepping: 0 
  microcode: 8701021 cache: L1: 768 KiB L2: 6 MiB L3: 64 MiB bogomips: 182131 
  Speed: 2792 MHz min/max: 2200/3800 MHz base/boost: 3800/4650 boost: enabled 
  volts: 1.1 V ext-clock: 100 MHz Core speeds (MHz): 1: 2792 2: 2023 3: 3679 
  4: 2090 5: 2771 6: 2030 7: 2060 8: 4408 9: 2120 10: 2112 11: 2196 12: 2196 
  13: 2194 14: 2196 15: 2113 16: 3238 17: 2151 18: 4396 19: 2034 20: 2114 
  21: 2196 22: 2195 23: 2196 24: 2169 
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1 
  bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy 
  constant_tsc cpb cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc 
  cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid f16c flushbyasid 
  fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibs irperf lahf_lm lbrv lm 
  mba mca mce misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc 
  nopl npt nrip_save nx osvw overflow_recov pae pat pausefilter pclmulqdq 
  pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pni popcnt pse 
  pse36 rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sev sev_es sha_ni 
  skinit smap smca sme smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp 
  succor svm svm_lock syscall tce topoext tsc tsc_scale umip v_vmsave_vmload 
  vgif vmcb_clean vme vmmcall wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr 
  xsaveopt xsaves 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  conditional, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Gigabyte 
  driver: vfio-pci v: 0.2 alternate: nouveau,nvidia_drm,nvidia bus-ID: 0b:00.0 
  chip-ID: 10de:1e84 class-ID: 0300 
  Device-2: NVIDIA GF106GL [Quadro 2000] driver: nvidia v: 390.144 
  alternate: nouveau,nvidia_drm bus-ID: 0c:00.0 chip-ID: 10de:0dd8 
  class-ID: 0300 
  Device-3: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 5-2.1.4:8 chip-ID: 046d:0843 class-ID: 0102 serial: <filter> 
  Display: server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: 
  loaded: nvidia display-ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0") 
  s-diag: 777mm (30.6") 
  Monitor-1: DP-3 res: 2560x1440 hz: 60 dpi: 109 size: 597x336mm (23.5x13.2") 
  diag: 685mm (27") 
  OpenGL: renderer: Quadro 2000/PCIe/SSE2 v: 4.6.0 NVIDIA 390.144 
  direct render: Yes 
Audio:
  Device-1: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK Virtuoso 100 
  driver: snd_virtuoso v: kernel bus-ID: 06:04.0 chip-ID: 13f6:8788 
  class-ID: 0401 
  Device-2: NVIDIA TU104 HD Audio vendor: Gigabyte driver: vfio-pci v: 0.2 
  alternate: snd_hda_intel bus-ID: 0b:00.1 chip-ID: 10de:10f8 class-ID: 0403 
  Device-3: NVIDIA GF106 High Definition Audio driver: snd_hda_intel v: kernel 
  bus-ID: 0c:00.1 chip-ID: 10de:0be9 class-ID: 0403 
  Device-4: AMD Starship/Matisse HD Audio vendor: Gigabyte 
  driver: snd_hda_intel v: kernel bus-ID: 0e:00.4 chip-ID: 1022:1487 
  class-ID: 0403 
  Device-5: Logitech Webcam C930e type: USB driver: snd-usb-audio,uvcvideo 
  bus-ID: 5-2.1.4:8 chip-ID: 046d:0843 class-ID: 0102 serial: <filter> 
  Sound Server-1: ALSA v: k5.10.52-1-MANJARO running: yes 
  Sound Server-2: JACK v: 0.125.0 running: no 
  Sound Server-3: PulseAudio v: 14.2 running: yes 
  Sound Server-4: PipeWire v: 0.3.32 running: no 
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel 
  port: c000 bus-ID: 07:00.0 chip-ID: 8086:1539 class-ID: 0200 
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: bridge0 state: up speed: 1000 Mbps duplex: unknown mac: <filter> 
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter> 
  IP v6: <filter> type: dynamic mngtmpaddr noprefixroute scope: global 
  IP v6: <filter> type: noprefixroute scope: link 
  WAN IP: <filter> 
Bluetooth:
  Message: No bluetooth data found. 
Logical:
  Device-1: VG: host type: LVM2 size: 465.26 GiB free: 169.26 GiB 
  LV-1: data maj-min: 254:4 type: linear dm: dm-4 size: 100 GiB 
  Components: 
  p-1: nvme0n1p2 maj-min: 259:2 size: 465.26 GiB 
  LV-2: home maj-min: 254:2 type: linear dm: dm-2 size: 150 GiB 
  Components: 
  p-1: nvme0n1p2 maj-min: 259:2 size: 465.26 GiB 
  LV-3: root maj-min: 254:1 type: linear dm: dm-1 size: 30 GiB 
  Components: 
  p-1: nvme0n1p2 maj-min: 259:2 size: 465.26 GiB 
  LV-4: swap maj-min: 254:0 type: linear dm: dm-0 size: 16 GiB 
  Components: 
  p-1: nvme0n1p2 maj-min: 259:2 size: 465.26 GiB 
  Device-2: VG: media type: LVM2 size: 7.28 TiB free: 1.13 TiB 
  LV-1: movies maj-min: 254:20 type: linear dm: dm-20 size: 3.42 TiB 
  Components: 
  p-1: sdd1 maj-min: 8:49 size: 3.64 TiB 
  LV-2: photo_raw maj-min: 254:21 type: linear dm: dm-21 size: 2.73 TiB 
  Components: 
  p-1: sdc1 maj-min: 8:33 size: 3.64 TiB 
  Device-3: VG: photos type: LVM2 size: 10.91 TiB free: 4.4 TiB 
  LV-1: photo_stripe maj-min: 254:22 type: linear dm: dm-22 size: 5.73 TiB 
  Components: 
  c-1: md0 maj-min: 9:0 size: 10.91 TiB 
  pp-1: sda1 maj-min: 8:1 size: 10.91 TiB 
  pp-2: sde1 maj-min: 8:65 size: 10.91 TiB 
  LV-2: tmp_stripe maj-min: 254:23 type: linear dm: dm-23 size: 800 GiB 
  Components: 
  c-1: md0 maj-min: 9:0 size: 10.91 TiB 
  pp-1: sda1 maj-min: 8:1 size: 10.91 TiB 
  pp-2: sde1 maj-min: 8:65 size: 10.91 TiB 
  Device-4: VG: vmvg type: LVM2 size: 1.82 TiB free: 772.25 GiB 
  LV-1: centos8 maj-min: 254:6 type: linear dm: dm-6 size: 50 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-2: debian10 maj-min: 254:15 type: linear dm: dm-15 size: 20 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-3: linuxmint maj-min: 254:7 type: linear dm: dm-7 size: 50 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-4: opensuse15.1 maj-min: 254:8 type: linear dm: dm-8 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-5: pop_os20 maj-min: 254:14 type: linear dm: dm-14 size: 25 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-6: ubuntu maj-min: 254:17 type: linear dm: dm-17 size: 20 GiB 
  Components: 
  c-1: dm-16 maj-min: 254:16 mapped: vmvg-ubuntu-real size: 20 GiB 
  pp-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-7: ubuntu1804 maj-min: 254:13 type: linear dm: dm-13 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-8: ubuntusnap maj-min: 254:19 type: linear dm: dm-19 size: 15.77 GiB 
  Components: 
  c-1: dm-16 maj-min: 254:16 mapped: vmvg-ubuntu-real size: 20 GiB 
  pp-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  c-2: dm-18 maj-min: 254:18 mapped: vmvg-ubuntusnap-cow size: 15.77 GiB 
  pp-1: nvme1n1p1 maj-min: 259:4 size: 931.51 GiB 
  LV-9: win10 maj-min: 254:3 type: linear dm: dm-3 size: 270 GiB 
  Components: 
  p-1: nvme1n1p1 maj-min: 259:4 size: 931.51 GiB 
  LV-10: workdrive maj-min: 254:5 type: linear dm: dm-5 size: 400 GiB 
  Components: 
  p-1: nvme1n1p1 maj-min: 259:4 size: 931.51 GiB 
  LV-11: worker1 maj-min: 254:10 type: linear dm: dm-10 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-12: worker2 maj-min: 254:9 type: linear dm: dm-9 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-13: worker3 maj-min: 254:11 type: linear dm: dm-11 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
  LV-14: worker4 maj-min: 254:12 type: linear dm: dm-12 size: 40 GiB 
  Components: 
  p-1: sdb1 maj-min: 8:17 size: 931.51 GiB 
RAID:
  Supported mdraid levels: raid1 
  Device-1: md0 maj-min: 9:0 type: mdraid level: mirror status: active 
  state: clean size: 10.91 TiB 
  Info: report: 2/2 UU blocks: 11718752192 chunk-size: N/A super-blocks: 1.2 
  Components: Online: 
  1: sde1 maj-min: 8:65 size: 10.91 TiB state: active sync 
  2: sda1 maj-min: 8:1 size: 10.91 TiB state: active sync 
Drives:
  Local Storage: total: raw: 31.38 TiB usable: 20.47 TiB lvm-free: 6.45 TiB 
  used: 2.75 TiB (13.4%) 
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung 
  model: SSD 970 EVO Plus 500GB size: 465.76 GiB block-size: physical: 512 B 
  logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> 
  rev: 2B2QEXM7 temp: 51.9 C scheme: GPT 
  SMART: yes health: PASSED on: 34d 17h cycles: 612 
  read-units: 6,894,586 [3.53 TB] written-units: 4,800,504 [2.45 TB] 
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung 
  model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B 
  logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter> 
  rev: 2B2QEXM7 temp: 47.9 C scheme: GPT 
  SMART: yes health: PASSED on: 45d 7h cycles: 611 
  read-units: 38,547,156 [19.7 TB] written-units: 53,005,909 [27.1 TB] 
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST12000NM001G-2MV103 
  family: Exos X16 size: 10.91 TiB block-size: physical: 4096 B logical: 512 B 
  sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SN03 
  temp: 31 C scheme: GPT 
  SMART: yes state: enabled health: PASSED on: 55d 5h cycles: 181 
  read: 6.46 TiB written: 15.4 TiB Pre-Fail: attribute: Spin_Retry_Count 
  value: 100 worst: 100 threshold: 97 
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB 
  family: based SSDs size: 931.51 GiB block-size: physical: 512 B 
  logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: SSD serial: <filter> 
  rev: 1B6Q temp: 27 C scheme: GPT 
  SMART: yes state: enabled health: PASSED on: 347d 16h cycles: 1072 
  written: 7.3 TiB 
  ID-5: /dev/sdc maj-min: 8:32 vendor: HGST (Hitachi) model: HUS726040ALE610 
  family: Ultrastar 7K6000 size: 3.64 TiB block-size: physical: 4096 B 
  logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 7200 
  serial: <filter> rev: T907 temp: 34 C scheme: GPT 
  SMART: yes state: enabled health: PASSED on: 1y 23d 21h cycles: 1258 
  ID-6: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST4000DM000-1F2168 
  family: Desktop HDD.15 size: 3.64 TiB block-size: physical: 4096 B 
  logical: 512 B sata: 3.1 speed: 6.0 Gb/s type: HDD rpm: 5900 
  serial: <filter> rev: CC54 temp: 30 C scheme: GPT 
  SMART: yes state: enabled health: PASSED on: 1y 78d 15h cycles: 1529 
  read: 11.89 TiB written: 12.84 TiB Pre-Fail: attribute: Spin_Retry_Count 
  value: 100 worst: 100 threshold: 97 
  ID-7: /dev/sde maj-min: 8:64 vendor: Seagate model: ST12000NM001G-2MV103 
  family: Exos X16 size: 10.91 TiB block-size: physical: 4096 B logical: 512 B 
  sata: 3.3 speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: SN02 
  temp: 30 C scheme: GPT 
  SMART: yes state: enabled health: PASSED on: 54d 7h cycles: 179 
  read: 11.22 TiB written: 4.49 TiB Pre-Fail: attribute: Spin_Retry_Count 
  value: 100 worst: 100 threshold: 97 
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH22NS70 rev: EX00 
  dev-links: cdrom 
  Features: speed: 48 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
Partition:
  ID-1: / raw-size: 30 GiB size: 29.4 GiB (98.01%) used: 16.97 GiB (57.7%) 
  fs: ext4 block-size: 4096 B dev: /dev/dm-1 maj-min: 254:1 mapped: host-root 
  label: N/A uuid: N/A 
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) 
  used: 320 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 
  maj-min: 259:1 label: N/A uuid: 103B-7EFC 
  ID-3: /home raw-size: 150 GiB size: 146.65 GiB (97.76%) 
  used: 86.09 GiB (58.7%) fs: ext4 block-size: 4096 B dev: /dev/dm-2 
  maj-min: 254:2 mapped: host-home label: N/A uuid: N/A 
  ID-4: /media/heiko/data raw-size: 100 GiB size: 97.93 GiB (97.93%) 
  used: 75.81 GiB (77.4%) fs: ext4 block-size: 4096 B dev: /dev/dm-4 
  maj-min: 254:4 mapped: host-data label: N/A uuid: N/A 
  ID-5: /run/timeshift/backup raw-size: 3.42 TiB size: 3.36 TiB (98.43%) 
  used: 2.58 TiB (76.6%) fs: ext4 block-size: 4096 B dev: /dev/dm-20 
  maj-min: 254:20 mapped: media-movies label: N/A uuid: N/A 
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/dm-0 maj-min: 254:0 mapped: host-swap label: N/A 
  uuid: 6f9c4054-35d9-4445-bc61-e2a50393a112 
Unmounted:
  ID-1: /dev/dm-10 maj-min: 254:10 mapped: vmvg-worker1 size: 40 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-2: /dev/dm-11 maj-min: 254:11 mapped: vmvg-worker3 size: 40 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-3: /dev/dm-12 maj-min: 254:12 mapped: vmvg-worker4 size: 40 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-4: /dev/dm-13 maj-min: 254:13 mapped: vmvg-ubuntu1804 size: 40 GiB 
  fs: N/A label: N/A uuid: N/A 
  ID-5: /dev/dm-14 maj-min: 254:14 mapped: vmvg-pop_os20 size: 25 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-6: /dev/dm-15 maj-min: 254:15 mapped: vmvg-debian10 size: 20 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-7: /dev/dm-16 maj-min: 254:16 mapped: vmvg-ubuntu-real size: 20 GiB 
  fs: N/A label: N/A uuid: N/A 
  ID-8: /dev/dm-17 maj-min: 254:17 mapped: vmvg-ubuntu size: 20 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-9: /dev/dm-18 maj-min: 254:18 mapped: vmvg-ubuntusnap-cow size: 15.77 GiB 
  fs: N/A label: N/A uuid: N/A 
  ID-10: /dev/dm-19 maj-min: 254:19 mapped: vmvg-ubuntusnap size: 20 GiB 
  fs: N/A label: N/A uuid: N/A 
  ID-11: /dev/dm-21 maj-min: 254:21 mapped: media-photo_raw size: 2.73 TiB 
  fs: N/A label: N/A uuid: N/A 
  ID-12: /dev/dm-22 maj-min: 254:22 mapped: photos-photo_stripe size: 5.73 TiB 
  fs: N/A label: N/A uuid: N/A 
  ID-13: /dev/dm-23 maj-min: 254:23 mapped: photos-tmp_stripe size: 800 GiB 
  fs: ext4 label: N/A uuid: 15920ee9-b368-4f83-9975-bdce1bb72e1a 
  ID-14: /dev/dm-3 maj-min: 254:3 mapped: vmvg-win10 size: 270 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-15: /dev/dm-5 maj-min: 254:5 mapped: vmvg-workdrive size: 400 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-16: /dev/dm-6 maj-min: 254:6 mapped: vmvg-centos8 size: 50 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-17: /dev/dm-7 maj-min: 254:7 mapped: vmvg-linuxmint size: 50 GiB fs: N/A 
  label: N/A uuid: N/A 
  ID-18: /dev/dm-8 maj-min: 254:8 mapped: vmvg-opensuse15.1 size: 40 GiB 
  fs: N/A label: N/A uuid: N/A 
  ID-19: /dev/dm-9 maj-min: 254:9 mapped: vmvg-worker2 size: 40 GiB fs: N/A 
  label: N/A uuid: N/A 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-1:2 info: Integrated Express IT8297 RGB LED Controller 
  type: Keyboard driver: hid-generic,usbhid interfaces: 1 rev: 2.0 
  speed: 12 Mb/s power: 100mA chip-ID: 048d:8297 class-ID: 0301 
  Hub-2: 1-6:3 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
  power: 100mA chip-ID: 05e3:0608 class-ID: 0900 
  Device-1: 1-6.1:4 info: Corsair H115i Platinum type: Keyboard 
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s 
  power: 100mA chip-ID: 1b1c:0c17 class-ID: 0300 
  Hub-3: 2-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-4: 3-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Hub-5: 3-6:2 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s 
  power: 100mA chip-ID: 05e3:0608 class-ID: 0900 
  Hub-6: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 speed: 10 Gb/s 
  chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-7: 5-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 5-1:2 info: Canon CanoScan LiDE 110 type: <vendor specific> 
  driver: N/A interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 500mA 
  chip-ID: 04a9:1909 class-ID: ff00 
  Hub-8: 5-2:3 info: Genesys Logic Hub ports: 3 rev: 2.1 speed: 480 Mb/s 
  power: 100mA chip-ID: 05e3:0610 class-ID: 0900 
  Hub-9: 5-2.1:4 info: Genesys Logic USB2.1 Hub ports: 4 rev: 2.1 
  speed: 480 Mb/s power: 100mA chip-ID: 05e3:061a class-ID: 0900 
  Device-1: 5-2.1.3:6 info: Logitech Unifying Receiver 
  type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid interfaces: 3 
  rev: 2.0 speed: 12 Mb/s power: 98mA chip-ID: 046d:c52b class-ID: 0300 
  Device-2: 5-2.1.4:8 info: Logitech Webcam C930e type: Video,Audio 
  driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0 speed: 480 Mb/s 
  power: 500mA chip-ID: 046d:0843 class-ID: 0102 serial: <filter> 
  Hub-10: 5-2.2:5 info: Genesys Logic Hub ports: 2 rev: 2.0 speed: 480 Mb/s 
  power: 100mA chip-ID: 05e3:0610 class-ID: 0900 
  Hub-11: 5-2.2.1:7 info: ASIX AX68004 ports: 7 rev: 1.0 speed: 12 Mb/s 
  power: 100mA chip-ID: 0b95:6804 class-ID: 0900 
  Device-1: 5-2.2.1.1:10 info: Microsoft Wired Keyboard 600 type: Keyboard,HID 
  driver: microsoft,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA 
  chip-ID: 045e:0750 class-ID: 0300 
  Device-2: 5-2.2.2:9 info: HP HP Monitor Z31x/Z27x-G2 type: <vendor specific> 
  driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 90mA 
  chip-ID: 03f0:1f47 class-ID: 0000 serial: <filter> 
  Hub-12: 6-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.1 
  speed: 10 Gb/s chip-ID: 1d6b:0003 class-ID: 0900 
  Hub-13: 6-2:2 info: Genesys Logic USB3.1 Hub ports: 3 rev: 3.1 speed: 5 Gb/s 
  chip-ID: 05e3:0620 class-ID: 0900 
  Hub-14: 6-2.1:3 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.1 
  speed: 5 Gb/s chip-ID: 05e3:062a class-ID: 0900 
Sensors:
  System Temperatures: cpu: 66.6 C mobo: 16.8 C gpu: nvidia temp: 68 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
Info:
  Processes: 429 Uptime: 2h 30m wakeups: 16 Init: systemd v: 248 
  tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 1545 lib: 423 
  flatpak: 0 Shell: Bash (sudo) v: 5.1.8 running-in: xfce4-terminal 
  inxi: 3.3.06

Question to admin / maintainers: Why can’t I add tags like “lvm” to the post. The selectable tags are quite meaningless and definitely don’t fit my case.

Can’t tell. I could create such a tag and added it to your post.


edit: Booted up 5.10.52 kernel and cannot see any problem with lvm (pvscan):

Jul 23 21:39:21 manjaro systemd[1]: Created slice Slice /system/lvm2-pvscan.
-- Subject: A start job for unit system-lvm2\x2dpvscan.slice has finished successfully
-- A start job for unit system-lvm2\x2dpvscan.slice has finished successfully.
-- Subject: A start job for unit lvm2-pvscan@259:2.service has begun execution
-- A start job for unit lvm2-pvscan@259:2.service has begun execution.
-- Subject: A start job for unit lvm2-pvscan@259:2.service has finished successfully
-- A start job for unit lvm2-pvscan@259:2.service has finished successfully.
-- Subject: A stop job for unit lvm2-pvscan@259:2.service has begun execution
-- A stop job for unit lvm2-pvscan@259:2.service has begun execution.
Jul 23 21:39:23 manjaro systemd[1]: lvm2-pvscan@259:2.service: Deactivated successfully.
-- The unit lvm2-pvscan@259:2.service has successfully entered the 'dead' state.
-- Subject: A stop job for unit lvm2-pvscan@259:2.service has finished
-- A stop job for unit lvm2-pvscan@259:2.service has finished.

Could be a result of my unstable branch setup, though.

1 Like

Thanks @freggel.doe. How many PV drives do you have? Also, do you use more than one VG?

Reason I’m asking is because previous bugs are usually related to LVM stretching over multiple drives (like in my case, the VG “media” uses two drives/partitions), or multiple VGs.

I added the inxi output and you will see that I have plenty of drives, four VGs, and I don’t know how many LVs. Some LVs are “unformated” and contain partitions or virtual drives that were formatted by a Windows VM. Anyway, that should not influence their activation.

Note: I rephrased the beginning of my original post as it wasn’t very clear: When the PC boots all LVs are activated except those in VG “media”.

1 vg with 5 lv on my 1 permanently installed drive.
Stil no problem when I attach some external drives with additional vg/lv but those are still all on the same drive.

I’ve tried to reproduce the problem in a vm but could not. I used 1 vg with 32 lv spanning 4 disks.
pvscan showed no problems on kernel 5.10 or 5.13.

I ran the pvscan commands manually and got the following results:

[woody ~]# pvscan --cache --activate ay 8:33
  pvscan[11604] PV /dev/sdc1 online, VG media is complete.
  pvscan[11604] VG media skip autoactivation.
[woody ~]# pvscan --cache --activate ay 8:49
  pvscan[11611] PV /dev/sdd1 online, VG media is complete.
  pvscan[11611] VG media skip autoactivation.

I think I’m getting closer. Need to check lvm.conf and what’s holding back pvscan to autoactivate the drives.

I implemented the fix provided by aqua - see here: https://bugs.archlinux.org/task/57275.

UPDATE: It doesn’t work!

Only once did it activate all LVs - after several reboots now it always left the LVs in VG “media” deactivated.

Back to square one.

[SOLVED]

The culprit was an old /etc/mkinitcpio.conf file that I had modified to make things work with older kernels.

For example, it contained the following lines:

# To load modules in old kernels:
MODULES="vfio vfio_iommu_type1 vfio_pci vfio_virqfd vhost_net"

# My hooks for kernel 5.4 and earlier were:
 HOOKS="base systemd autodetect modconf block keyboard keymap lvm2 filesystems"

I noticed that this file could be the problem when reading Does mkinitcpio.conf survive new kernel? Now that the answer is yes, I checked my mkinitcpio.conf versus mkinitcpio.conf.pacnew that’s installed and updated with upgrades.

All I had to do was replace the .conf file with the .conf.pacnew version and modify as follows:

MODULES=()
...
HOOKS=(base udev autodetect modconf block lvm2 filesystems keyboard fsck)

Note: I added lvm2.

Then run:
mkinitcpio -p linux510

Everything is fine now and all VGs/LVs are activated.

P.S.: I am going to delete irrelevant posts to make this thread shorter and more to the point.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.