lvm above raid does not recognized

[alexminder]

I have block device structure:

sda
├─sda1
│ └─md127
│   └─vg_encl_rd1-lv_encl_rd1
└─sda2
  └─vg_encl_rd0-lv_encl_rd0
sdb
├─sdb1
│ └─md127
│   └─vg_encl_rd1-lv_encl_rd1
└─sdb2
  └─vg_encl_rd0-lv_encl_rd0

booster.yaml:

universal: false
modules: sg,scsi_mod,usb_storage,uas,xhci_hcd,xhci_pci,raid0,raid1,raid10,dm_thin_pool,dm_cache_smq,amd_rng,efivarfs,xfs
modules_force_load: sg,scsi_mod,usb_storage,uas,xhci_hcd,xhci_pci,raid0,raid1,raid10,dm_thin_pool,dm_cache_smq,amd_rng,efivarfs,xfs
compression: zstd
strip: false
enable_lvm: true
enable_mdraid: true

booster creates md device and vg_encl_rd0-lv_encl_rd0, but not vg_encl_rd1-lv_encl_rd1. From debug log it looks like lvm scan happens before creating md device. When md device created udev action appears but no further steps by booster happens.

[anatol]

I have block device structure

Could you please also print the version for a booted system using lsblk -v

It is unclear why the boot process is stuck. Could you please add booster.log=debug,console boot parameter, capture the output and print it here?

[alexminder]

$ lsblk -V
lsblk from util-linux 2.39.4

Booster log I can not capture any more. Due to certain circumstances, I no longer have a raid environment.

[anatol]

Hi, I need lsblk -v with lowercase to print the block device hierarchy. You printed -V uppercase to print version of the tool.

Due to certain circumstances, I no longer have a raid environment.

I am not sure I understand it correctly. Are you saying that you don't have the original problem anymore and this issue can be closed now?

[alexminder]

lsblk -v show nothing because the machine don't use virtio driver: -v, --virtio output info about virtio devices

Are you saying that you don't have the original problem anymore and this issue can be closed now?

The problem potentialy exists in booster, but I already move from mdraid and can not provide logs. So the issue may be closed.

[anatol]

D'oh sorry, I meant lsblk output.

ack, let's close the issue. But if in the future you get a stuck boot then having boot logs is very helpful for debugging.