I've googled out that this can have something to do with lvmetad enabled or not. I've enabled lvmetad in /etc/lvm/lvm.conf, reconfigured current kernel package. On boot, there were error messages about failed connection to lvmetad socket, but boot process finished successfully without any waiting for devices. Lvmetad didn't start though. I've decided to revert back to default setup with disabled lvmetad, so I've disabled lvmetad in /etc/lvm/lvm.conf, reconfigured kernel package. And now this bug did not occur over three reboots. No idea why, but enabling/disabling lvmetad seem to help.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
