Uh, start timeout is bad. And lvm that remains running also is not good (it should be short call, should not remain running after qubesd stops). I guess something about LVM itself went wrong. Can you check just sudo journalctl about that time if you seem some LVM-related errors (or generally some other errors before that start timeout)? Maybe something from the kernel about device-mapper (“dm” in short)?
1 Like