Happy new year!
I've been running Tumbleweed on a laptop since last August. The
encrypted LVM partition on the SSD is split into two logical volumes,
root and home. Until I upgraded lvm2 two days ago from 2.02.152 to
2.02.165, the system would boot normally. Since the upgrade, the system
starts the emergency shell after attempting to mount home fails
(displaying "A start job is running for dev-macbook-home.device" until
the timer expires). If I type "vgchange -ay" in the shell and exit, boot
resumes normally.
As I was checking the snapshot diff before and after the upgrade of
lvm2, I noticed that lvm.conf includes extra settings about
auto_activation_volume_list etc. Does anyone have any idea how to make
lvm behave normally again?
--
Regards,
Peter
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
