FS#63610 - [lvm2] mount Problems after Update

Attached to Project: Arch Linux
Opened by Martin (happycadaver) - Saturday, 31 August 2019, 11:53 GMT
Last edited by Christian Hesse (eworm) - Friday, 06 September 2019, 15:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

After Insttall Version 2.02.186-1

I have this Message:

password is required to access the luks volume:
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
ERROR: device '/dev/mapper/vg0-root' not found, Skipping fsck.
mount: /new_root: special device /dev/mapper/vg0-root does not exist.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

When i Install Version 2.02.185-1 i have no Problems.
This task depends upon

Closed by  Christian Hesse (eworm)
Friday, 06 September 2019, 15:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  lvm2 2.02.186-2
Comment by loqs (loqs) - Saturday, 31 August 2019, 12:26 GMT
https://bbs.archlinux.org/viewtopic.php?id=248788
https://github.com/lvmteam/lvm2/issues/24
Comment by Arthur (Arthur_W) - Tuesday, 03 September 2019, 10:18 GMT
I had the same problem.
Downgrade to
device-mapper-2.02.185-1-x86_64.pkg.tar.xz
lvm2-2.02.185-1-x86_64.pkg.tar.xz
fixed it. But this error occurs only if you have LVM on LUKS on more than one partition, see: https://bugs.archlinux.org/task/63634
Comment by Arthur (Arthur_W) - Tuesday, 03 September 2019, 10:19 GMT
Description:
Setup: LVM on LUKS (Arch Linux), LVM on LUKS over two partitions or two SSDs
After Upgrade to
core/device-mapper 2.02.186-1 (base) - device-mapper-2.02.186-1-x86_64.pkg.tar.xz
core/lvm2 2.02.186-1 (base) - lvm2-2.02.186-1-x86_64.pkg.tar.xz
system runs into recovery shell after password input.
workaround: Downgrade to
device-mapper-2.02.185-1-x86_64.pkg.tar.xz
lvm2-2.02.185-1-x86_64.pkg.tar.xz
helps and boot is successful.
This Bud does not occur on systems with LVM on LUKS with one partition (tested)
Comment by ryuta (ryuta) - Tuesday, 03 September 2019, 18:04 GMT
For booting to solve the problem, it may be something like :
lvm vgchange -ay # force activation of logical volume
mkdir /new # Maybe it already exists.
mount /dev/mapper/root_logical_volume /new
exit
(Here you should exit the emergency mode and start normally.)

Then in root :
cd /var/cache/pacman/pkg/
yaourt -U device-mapper-2.02.185-1-x86_64.pkg.tar.xz lvm2-2.02.185-1-x86_64.pkg.tar.xz
Comment by Krister Bäckman (ixevix) - Tuesday, 03 September 2019, 19:46 GMT
Exact same problem, downgrading like ryuta suggest fixed the problem for me.
Comment by loqs (loqs) - Tuesday, 03 September 2019, 20:53 GMT
https://bugzilla.redhat.com/show_bug.cgi?id=1748430
Comment by Christian Hesse (eworm) - Friday, 06 September 2019, 14:41 GMT
Please test lvm2 2.02.186-2.
Comment by Martin (happycadaver) - Friday, 06 September 2019, 14:58 GMT
The Version 2.02.186-2 from lvm2 works now, thank you

Loading...