I have all partitions including root on lvm. I use initramfs generated by genkernel. I have lvm and lvmetad in boot runlevel. I try to use lvmetad. lvmetad starts after lvm So I get a lot of errors: * Setting up the Logical Volume Manager ... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory /run/lvm/lvmetad.socket: connect failed: No such file or directory When I reboot my pc theese errors appear again. I've also noticed that lvmetad needs /run/lvm directory, which is created by device-mapper init script. So device-mapper should be started before lvmetad. The right order fixing this issue should be: 1) device-mapper (creates /run/lvm) 2) lvmetad 3) lvm I was not able to make lvmetad and device-mapper start before lvm correcting init.d scripts with different combination of "after", "before" and "need". The only workaround that makes boot errors gone away to put lvmeta in sysinit and don't forget to make /run/lvm before it is started.
*** This bug has been marked as a duplicate of bug 500732 ***
