Dear Maintainer,

I upgraded one of my systems from stretch to buster today, and it failed to
complete booting afterwards, dropping to the (initramfs) prompt.

The cause is that only two of the logical volumes in my volume group - those
for / and /boot - are active on boot, and no action is seemingly taken to
activate the remainder, leading to /usr not being found.

Running vgchange -a y or vgchange -ay, then Ctrl-D, allows the system to
continue booting. However, this action will be needed on every reboot until
a permanent workaround, or a fix, is found.

I expected my system to boot normally, as it did before the upgrade, especially
as there was nothing in the release notes to advise me of this problem.

http://paste.debian.net/1091044/ shows the relevant portion of the
initramfs debug.

The problem is caused by scripts-top/lvm2 only activating volumes if
called with one of fe[0-9]*, /dev/root, /dev/mapper/* or /dev/*/*. If
called with a UUID, it doesn't work. By using /dev/mapper references in
fstab, I now have it working, but I am not sure whether this really is
the best thing security-wise.

I just encountered the same problem on an upgrade from 9.x to 10.1,
when using LABEL= directives in /etc/fstab.  I also had to use
"vgchange -ay" in the boot rescue shell.  Changing fstab to use
/dev/vg*/* paths resulted in a system that boots without intervention.

----------------------------------------
reportbug --template lvm2 output includes

Package: lvm2
Version: 2.03.02-3

Debian Release: 10.1
 APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'),
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lvm2 depends on:
ii  dmeventd                  2:1.02.155-3
ii  dmsetup                   2:1.02.155-3
ii  libaio1                   0.3.112-3
ii  libblkid1                 2.33.1-0.1
ii  libc6                     2.28-10
ii  libdevmapper-event1.02.1  2:1.02.155-3
ii  libdevmapper1.02.1        2:1.02.155-3
ii  libreadline5              5.2+dfsg-3+b13
ii  libselinux1               2.8-1+b1
ii  libsystemd0               241-7~deb10u1
ii  libudev1                  241-7~deb10u1
ii  lsb-base                  10.2019051400

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.7.6-2.1
----------------------------------------
Failing /etc/fstab included these lines

LABEL=DEB_ROOT  /                       ext4    noatime                 0 1
LABEL=DEB_USR   /usr                    ext4    noatime                 0 2
LABEL=DEB_VAR   /var                    ext4    noatime                 0 2
LABEL=BOOT      /boot                   ext4    noatime                 0 2
LABEL=TMP       /tmp                    ext4    noatime,nodev           0 2
LABEL=HOME      /home                   ext4    noatime                 0 2
LABEL=ALL       /all                    ext4    noatime                 0 2
LABEL=SWAP      swap                    swap    sw                      0 0

----------------------------------------
Working /etc/fstab includes these lines

/dev/vgfast/deb_root    /                       ext4    noatime
         0 1
/dev/vgfast/deb_usr     /usr                    ext4    noatime
         0 2
/dev/vgfast/deb_var     /var                    ext4    noatime
         0 2
/dev/vgfast/tmp         /tmp                    ext4    noatime,nodev
         0 2
/dev/vgfast/home        /home                   ext4    noatime
         0 2
/dev/vgfast/all         /all                    ext4    noatime
         0 2
/dev/vgfast/swap        swap                    swap    sw
         0 0
LABEL=BOOT              /boot                   ext4    noatime
         0 2

----------------------------------------

Dear Maintainer,

My Debian stable system, running on old i386 hardware, suddenly became unbootable after doing full upgrades via apt.
Via upgrades, the system passed from kernel 4.19.0-6-i686-pae to the corresponding 4.19.0-8-i686-pae.
After the upgrade, when booting with 4.19.0-8, it says:

md/raid0:md0: cannot assemble multi-zone RAID0 with default_layout setting
md/raid0: please set raid0.default_layout to 1 or 2
Failed to start LVMevent activation on device 8:17
See 'systemctlstatus lvm2-pvscan@8:17.service' for details.

If left alone, the system goes in emergency mode after a while.

However, the same system boots normally if, during boot, one chooses manually the 4.19.0-6 kernel in grub's boot menu.

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Can you please provide a solution? Thank you!

Bună seara, vă rog să mă sunați acum sau să răspundeți la mailul pe care vi
l-am trimis de ieri.