Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

On 10/11/17 23:33, Bastian Blank wrote:

On Fri, Nov 10, 2017 at 11:22:11PM +1300, Ben Caradoc-Davies wrote:

installation of 2.02.176-3 (etc) *fails* in
/usr/share/initramfs-tools/hooks/lvm2. Installed debs hot off incoming:

I see.  This is added error checking that now shows another problem.


Bastian,

thanks very much. That looks good to me. I was able to use "dpkg -i" to 
install the -4 debs from incoming. I needed an "apt-get install -f", 
likely because of the earlier failure with the -3 debs. Other than that, 
everything seems fixed. I was able to boot normally. The debs I used were:


dmeventd_1.02.145-4_amd64.deb
dmsetup_1.02.145-4_amd64.deb
libdevmapper-event1.02.1_1.02.145-4_amd64.deb
libdevmapper1.02.1_1.02.145-4_amd64.deb
liblvm2app2.2_2.02.176-4_amd64.deb
liblvm2cmd2.02_2.02.176-4_amd64.deb
lvm2_2.02.176-4_amd64.deb

Thanks again for your prompt response to these issues.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#881314: lvm2 upgrade causes boot failure

[Bastian Blank]

Hi Ben

On Fri, Nov 10, 2017 at 11:22:11PM +1300, Ben Caradoc-Davies wrote:
> installation of 2.02.176-3 (etc) *fails* in
> /usr/share/initramfs-tools/hooks/lvm2. Installed debs hot off incoming:

I see.  This is added error checking that now shows another problem.

Bastian

-- 
... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
-- McCoy, "The Omega Glory", stardate unknown

Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

Bastian,

installation of 2.02.176-3 (etc) *fails* in 
/usr/share/initramfs-tools/hooks/lvm2. Installed debs hot off incoming:


dmeventd_1.02.145-3_amd64.deb
dmsetup_1.02.145-3_amd64.deb
libdevmapper-event1.02.1_1.02.145-3_amd64.deb
libdevmapper1.02.1_1.02.145-3_amd64.deb
liblvm2app2.2_2.02.176-3_amd64.deb
liblvm2cmd2.02_2.02.176-3_amd64.deb
lvm2_2.02.176-3_amd64.deb

dpkg -i output:

(Reading database ... 159531 files and directories currently installed.)
Preparing to unpack .../dmeventd_1.02.145-3_amd64.deb ...
Unpacking dmeventd (2:1.02.145-3) over (2:1.02.145-1) ...
Preparing to unpack .../dmsetup_1.02.145-3_amd64.deb ...
Unpacking dmsetup (2:1.02.145-3) over (2:1.02.145-1) ...
Preparing to unpack .../libdevmapper-event1.02.1_1.02.145-3_amd64.deb ...
Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.145-3) over 
(2:1.02.145-1) ...

Preparing to unpack .../libdevmapper1.02.1_1.02.145-3_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.145-3) over (2:1.02.145-1) ...
Preparing to unpack .../liblvm2app2.2_2.02.176-3_amd64.deb ...
Unpacking liblvm2app2.2:amd64 (2.02.176-3) over (2.02.176-1) ...
Preparing to unpack .../liblvm2cmd2.02_2.02.176-3_amd64.deb ...
Unpacking liblvm2cmd2.02:amd64 (2.02.176-3) over (2.02.176-1) ...
Preparing to unpack .../tmp/lvm2_2.02.176-3_amd64.deb ...
Unpacking lvm2 (2.02.176-3) over (2.02.176-1) ...
Setting up libdevmapper1.02.1:amd64 (2:1.02.145-3) ...
Setting up dmsetup (2:1.02.145-3) ...
update-initramfs: deferring update (trigger activated)
Setting up libdevmapper-event1.02.1:amd64 (2:1.02.145-3) ...
Setting up liblvm2app2.2:amd64 (2.02.176-3) ...
Setting up liblvm2cmd2.02:amd64 (2.02.176-3) ...
Setting up dmeventd (2:1.02.145-3) ...
Setting up lvm2 (2.02.176-3) ...
update-initramfs: deferring update (trigger activated)
Syntax: /usr/bin/deb-systemd-invoke   [ ...]
Processing triggers for libc-bin (2.24-17) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for systemd (235-2) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.13.0-1-amd64
E: /usr/share/initramfs-tools/hooks/lvm2 failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.13.0-1-amd64 with 1.
dpkg: error processing package initramfs-tools (--install):
 installed initramfs-tools package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
 initramfs-tools

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

On 10/11/17 20:02, Bastian Blank wrote:

On Fri, Nov 10, 2017 at 06:37:36PM +1300, Ben Caradoc-Davies wrote:

Severity: critical
Justification: breaks the whole system

Nope, it only breaks itself.


Well, it only breaks systems that use it.


upgrading to lvm2 2.02.176-2 (and related packages) results in boot failure.
Photo of boot message attached.

Not pretty useful.


Indeed, nothing to see here. There is one outstanding report in BTS of 
this message being present and causing no harm. It may be entirely 
useless. My initial quick report is fodder for apt-listbugs to protect 
my fellow crash test dummies. The scene is now secure and waiting for 
forensics to arrive.


I will reproduce and try to get better information. There is nothing 
else in the logs; they would be in the VG that allegedly could not be 
found. First stop will be booting without quiet and splash. If I spot 
anything relevant I will report back.


Other system information:
- /boot is plain partition with ext4
- VG (vg) is in a LUKS partition in one LVM PV
- / and /home in


Upgrade was:

Please provide the dpkg log.


Excerpt from /var/log/apt/term.log:

Log started: 2017-11-10  17:59:51
(Reading database ... 159529 files and directories currently installed.)
Preparing to unpack .../libquadmath0_7.2.0-14_amd64.deb ...
Unpacking libquadmath0:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../libitm1_7.2.0-14_amd64.deb ...
Unpacking libitm1:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../gcc-7-base_7.2.0-14_amd64.deb ...
Unpacking gcc-7-base:amd64 (7.2.0-14) over (7.2.0-12) ...
Setting up gcc-7-base:amd64 (7.2.0-14) ...
(Reading database ... 159529 files and directories currently installed.)
Preparing to unpack .../libstdc++6_7.2.0-14_amd64.deb ...
Unpacking libstdc++6:amd64 (7.2.0-14) over (7.2.0-12) ...
Setting up libstdc++6:amd64 (7.2.0-14) ...
(Reading database ... 159529 files and directories currently installed.)
Preparing to unpack .../00-libmpx2_7.2.0-14_amd64.deb ...
Unpacking libmpx2:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../01-libgomp1_7.2.0-14_amd64.deb ...
Unpacking libgomp1:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../02-libatomic1_7.2.0-14_amd64.deb ...
Unpacking libatomic1:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../03-libasan4_7.2.0-14_amd64.deb ...
Unpacking libasan4:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../04-liblsan0_7.2.0-14_amd64.deb ...
Unpacking liblsan0:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../05-libtsan0_7.2.0-14_amd64.deb ...
Unpacking libtsan0:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../06-libubsan0_7.2.0-14_amd64.deb ...
Unpacking libubsan0:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../07-libcilkrts5_7.2.0-14_amd64.deb ...
Unpacking libcilkrts5:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../08-cpp-7_7.2.0-14_amd64.deb ...
Unpacking cpp-7 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../09-libcc1-0_7.2.0-14_amd64.deb ...
Unpacking libcc1-0:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../10-g++-7_7.2.0-14_amd64.deb ...
Unpacking g++-7 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../11-gcc-7_7.2.0-14_amd64.deb ...
Unpacking gcc-7 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../12-libgcc-7-dev_7.2.0-14_amd64.deb ...
Unpacking libgcc-7-dev:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../13-libstdc++-7-dev_7.2.0-14_amd64.deb ...
Unpacking libstdc++-7-dev:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../14-libgfortran4_7.2.0-14_amd64.deb ...
Unpacking libgfortran4:amd64 (7.2.0-14) over (7.2.0-12) ...
Preparing to unpack .../15-libgcc1_1%3a7.2.0-14_amd64.deb ...
Unpacking libgcc1:amd64 (1:7.2.0-14) over (1:7.2.0-12) ...
Setting up libgcc1:amd64 (1:7.2.0-14) ...
(Reading database ... 159529 files and directories currently installed.)
Preparing to unpack .../00-dmsetup_2%3a1.02.145-2_amd64.deb ...
Unpacking dmsetup (2:1.02.145-2) over (2:1.02.145-1) ...
Preparing to unpack .../01-libdevmapper1.02.1_2%3a1.02.145-2_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.145-2) over (2:1.02.145-1) ...
Preparing to unpack 
.../02-libdevmapper-event1.02.1_2%3a1.02.145-2_amd64.deb ...
Unpacking libdevmapper-event1.02.1:amd64 (2:1.02.145-2) over 
(2:1.02.145-1) ...

Preparing to unpack .../03-liblvm2cmd2.02_2.02.176-2_amd64.deb ...
Unpacking liblvm2cmd2.02:amd64 (2.02.176-2) over (2.02.176-1) ...
Preparing to unpack .../04-dmeventd_2%3a1.02.145-2_amd64.deb ...
Unpacking dmeventd (2:1.02.145-2) over (2:1.02.145-1) ...
Preparing to unpack .../05-libavutil55_7%3a3.4-2_amd64.deb ...
Unpacking libavutil55:amd64 (7:3.4-2) over (7:3.3.4-2+b3) ...
Preparing to unpack .../06-libswresample2_7%3a3.4-2_amd64.deb ...
Unpacking libswresample2:amd64 (7:3.4-2) over (7:3.3.4-2+b3) ...
Preparing to unpack .../07-libavcodec57_7%3a3.4-2_amd64.deb ...
Unpacking libavcodec57:amd64 (7:3.4-2) over (7:3.3.4-2+b3) ...
Preparing to 

Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

On 10/11/17 22:22, Ben Caradoc-Davies wrote:

I will reproduce and try to get better information.

Bastian,

you are too quick for me. Instead I will test 2.02.176-3 (etc)  as soon 
as it is built.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: Re: Bug#881314: lvm2 upgrade causes boot failure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #881314 [lvm2] lvm2 upgrade causes boot failure
Severity set to 'serious' from 'critical'

-- 
881314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#881314: lvm2 upgrade causes boot failure

[Bastian Blank]

Control: severity -1 serious

On Fri, Nov 10, 2017 at 06:37:36PM +1300, Ben Caradoc-Davies wrote:
> Severity: critical
> Justification: breaks the whole system

Nope, it only breaks itself.

> upgrading to lvm2 2.02.176-2 (and related packages) results in boot failure.
> Photo of boot message attached.

Not pretty useful.

> Upgrade was:

Please provide the dpkg log.

Bastian

-- 
Death, when unnecessary, is a tragic thing.
-- Flint, "Requiem for Methuselah", stardate 5843.7

Bug#881314: lvm2 upgrade causes boot failure

[Ben Caradoc-Davies]

Package: lvm2
Version: 2.02.176-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

upgrading to lvm2 2.02.176-2 (and related packages) results in boot failure.
Photo of boot message attached.

Upgrade was:

dmeventd:amd64 (2:1.02.145-1, 2:1.02.145-2)
dmsetup:amd64 (2:1.02.145-1, 2:1.02.145-2)
libdevmapper-event1.02.1:amd64 (2:1.02.145-1, 2:1.02.145-2)
libdevmapper1.02.1:amd64 (2:1.02.145-1, 2:1.02.145-2)
liblvm2app2.2:amd64 (2.02.176-1, 2.02.176-2)
liblvm2cmd2.02:amd64 (2.02.176-1, 2.02.176-2)
lvm2:amd64 (2.02.176-1, 2.02.176-2)

Workaround is to downgrade these packages, which results in a normal boot.

Kind regards,
Ben.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lvm2 depends on:
pn  dmeventd  
pn  dmsetup   
ii  libblkid1 2.30.2-0.1
ii  libc6 2.24-17
pn  libdevmapper-event1.02.1  
pn  libdevmapper1.02.1
pn  liblvm2app2.2 
ii  libreadline5  5.2+dfsg-3+b1
ii  libsystemd0   235-2
ii  libudev1  235-2
ii  lsb-base  9.20170808

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.7.4-2

lvm2 suggests no packages.

-- Configuration Files:
/etc/lvm/lvm.conf changed:
config {
# Configuration option config/checks.
# If enabled, any LVM configuration mismatch is reported.
# This implies checking that the configuration key is understood by
# LVM and that the value of the key is the proper type. If disabled,
# any configuration mismatch is ignored and the default value is used
# without any warning (a message about the configuration key not being
# found is issued in verbose mode only).
checks = 1
# Configuration option config/abort_on_errors.
# Abort the LVM process if a configuration mismatch is found.
abort_on_errors = 0
# Configuration option config/profile_dir.
# Directory where LVM looks for configuration profiles.
profile_dir = "/etc/lvm/profile"
}
devices {
# Configuration option devices/dir.
# Directory in which to create volume group device nodes.
# Commands also accept this as a prefix on volume group names.
# This configuration option is advanced.
dir = "/dev"
# Configuration option devices/scan.
# Directories containing device nodes to use with LVM.
# This configuration option is advanced.
scan = [ "/dev" ]
# Configuration option devices/obtain_device_list_from_udev.
# Obtain the list of available devices from udev.
# This avoids opening or using any inapplicable non-block devices or
# subdirectories found in the udev directory. Any device node or
# symlink not managed by udev in the udev directory is ignored. This
# setting applies only to the udev-managed device directory; other
# directories will be scanned fully. LVM needs to be compiled with
# udev support for this setting to apply.
obtain_device_list_from_udev = 1
# Configuration option devices/external_device_info_source.
# Select an external device information source.
# Some information may already be available in the system and LVM can
# use this information to determine the exact type or use of devices it
# processes. Using an existing external device information source can
# speed up device processing as LVM does not need to run its own native
# routines to acquire this information. For example, this information
# is used to drive LVM filtering like MD component detection, multipath
# component detection, partition detection and others.
# 
# Accepted values:
#   none
# No external device information source is used.
#   udev
# Reuse existing udev database records. Applicable only if LVM is
# compiled with udev support.
# 
external_device_info_source = "none"
# Configuration option devices/preferred_names.
# Select which path name to display for a block device.
# If multiple path names exist for a block device, and LVM needs to
# display a name for the device, the path names are matched against
# each item in this list of regular expressions. The first match is
# used. Try to avoid using undescriptive /dev/dm-N names, if present.
# If no preferred name matches, or if preferred_names are not defined,
# the following built-in preferences are applied in order