FS#37346 - [lvm2] lvmetad segfaults in initial ramdisk
Attached to Project:
Arch Linux
Opened by Daniel Mendler (minad) - Tuesday, 15 October 2013, 12:18 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 10 February 2021, 09:33 GMT
Opened by Daniel Mendler (minad) - Tuesday, 15 October 2013, 12:18 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 10 February 2021, 09:33 GMT
|
Details
Description:
I use a setup with software raid 5 and lvm on top of it for the root fs. In the lvm2 early hook lvmetad segfaults which prevents the system from disconvering the root partition and continuing with the boot process. However if I don't start lvmetad and instead use "vgchange -ay" root is found. My hooks: HOOKS="base udev autodetect modconf block mdadm_udev lvm2 filesystems keyboard fsck" Maybe this should be fixed upstream. But I also want to notify you here of the problems. |
This task depends upon
Closed by Christian Hesse (eworm)
Wednesday, 10 February 2021, 09:33 GMT
Reason for closing: None
Additional comments about closing: lvm2 2.03.11-3
Wednesday, 10 February 2021, 09:33 GMT
Reason for closing: None
Additional comments about closing: lvm2 2.03.11-3
Have you reported it upstream?
killall -9 lvmetad
lvm vgchange -ay
Maybe I am doing something stupid here, but at least it works. The initial ram disk worked before using vgchange -ay and after the upgrade to lvmetad a while ago it did not anymore. I observed the segfaults back then. It seems I am the only one having this problem? So I should definitely debug this further. However my debugging capabilities are a bit limited in the busy box and I am also not so happy working with a non-booting system ;)
The first line reads:
#!/usr/bin/ash
But it must be:
#!/usr/bin/bash
Next after a `# mkinitcpio -p linux` my server boots up normal again....I hope it helps.
Booting results in being dropped in a shell. In my case however, it is lvm (not lvmetad) that crashes.
simply running lvm vgchange -a y; exit
is enough to continue the boot process.