Page 1 of 1

mga8 not booting: delayed lvm activation?

PostPosted: Apr 30th, '21, 15:35
by magfan
After upgrading from mga7 -> mga8 my workstation does not boot normally. I have to start in rescue mode, run "init 3" and finally login as root to run "init 5". It seems to me there should be some kind of delay during the boot process so that all lvm-partitions are activated. But where can I set this delay?

Last lines from rdsosreport.txt:
Code: Select all
[  161.878470] dracut: Scanning devices nvme0n1p1  for LVM logical volumes vg_system/lv_root
[  161.917604] dracut: inactive '/dev/vg_system/lv_opt' [64.00 GiB] inherit
[  161.917743] dracut: inactive '/dev/vg_system/lv_var' [128.00 GiB] inherit
[  161.917861] dracut: ACTIVE '/dev/vg_system/lv_root' [256.00 GiB] inherit
[  161.917973] dracut: inactive '/dev/vg_system/lv_home' [256.00 GiB] inherit
[  237.134115] dracut Warning: Could not boot.
[  237.144105] dracut Warning: /dev/disk/by-uuid/a2ba326c-21f0-447a-866f-cbfca4d4ac91 does not exist

Re: mga8 not booting: delayed lvm activation?

PostPosted: Apr 30th, '21, 17:20
by doktor5000
Problem is not the LVM activation but that the NVME controller takes too long to provide the underlying physical devices.

Either try to add a wait time before initrd loads as e.g. in https://unix.stackexchange.com/question ... -rootdelay
Or check if you need to add some modules for your nvme controller to the initrd as e.g. in https://bbs.archlinux.org/viewtopic.php?id=251762

It might help if you check journal logs for messages from your NVME controller.

Re: mga8 not booting: delayed lvm activation?

PostPosted: May 3rd, '21, 10:53
by magfan
SATA mode is set to AHCI in BIOS, vmd-module is already included in initrd, nvme_load=YES has been added to the kernel boot line. Additionally I tried several values for rootdelay. Attached is the output of dmesg with rootdelay=10. Still I have to boot in emergency mode -> init 3 -> init 5.

Re: mga8 not booting: delayed lvm activation?

PostPosted: May 3rd, '21, 15:44
by magfan
This time I saved an rdsosreport with debug information. But I still cannot find the problem.

Re: mga8 not booting: delayed lvm activation?

PostPosted: May 3rd, '21, 16:50
by doktor5000
When you boot in emergency mode and then to runlevel 3, have a look at the status of the lvm services, and also of the .device units for the devicemapper devices.
You could try to manually add a delay/dependencies as mentioned in the bottom half of e.g. https://unix.stackexchange.com/a/513991/83329

Also, you seem to be missing a blank after "nvme_load=YES" in your kernel options.
And you should also try with rootwait, as rootdelay seems to be silently ignored sometimes: https://bugs.mageia.org/show_bug.cgi?id=10484

Re: mga8 not booting: delayed lvm activation?

PostPosted: May 3rd, '21, 22:12
by magfan
When you boot in emergency mode and then to runlevel 3, have a look at the status of the lvm services, and also of the .device units for the devicemapper devices.

In which logfiles should I look for messages?

Re: mga8 not booting: delayed lvm activation?

PostPosted: May 4th, '21, 16:38
by doktor5000
In the normal journal logs. systemctl --all | grep -i device and systemctl status name_of_device.device -al should show the logs too and also the status for the devices.