Hi,
Just a quick note that the failure mode still exists after upgrading to
bookworm (testing). If anyone has any pointers on how to diagnose mount
failures during initrd I'd happily run some experiments.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
I've hit what I think is a thin related issue on upgrading to
bullseye/testing. My boot hangs on fsck timing out on the 3 thin
provisioned partitions. I manually did a vgchange -ay to active them but it
didn't solve the problem. If I drop into maintenance mode and manually
"mount -a" things do
Package: lvm2
Version: 2.02.168-2
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Not sure about the severity; as luck would have it my system can boot,
but many volumes were rendered entirely unavailable so for some this
would be
3 matches
Mail list logo
