FS#63634 - LVM on LUKS over two partitions runs into recovery shell - error device not found skipping fsck
Attached to Project:
Arch Linux
Opened by Arthur (Arthur_W) - Tuesday, 03 September 2019, 07:42 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 07 September 2019, 11:21 GMT
Opened by Arthur (Arthur_W) - Tuesday, 03 September 2019, 07:42 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 07 September 2019, 11:21 GMT
|
Details
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) Additional info: * package version(s) ** core/device-mapper 2.02.186-1 (base) ** core/lvm2 2.02.186-1 (base) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: * LVM on LUKS over two partitions or two SSDs * Upgrade core/device-mapper 2.02.185-1 to core/device-mapper 2.02.186-1 and core/lvm2 2.02.185-1 to core/lvm2 2.02.186-1 * System runs into recovery shell after input of the correct password |
This task depends upon
Closed by Antonio Rojas (arojas)
Saturday, 07 September 2019, 11:21 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#63610
Saturday, 07 September 2019, 11:21 GMT
Reason for closing: Duplicate
Additional comments about closing:
It seams it is a duplicate of https://bugs.archlinux.org/task/63610?