[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

Uxorious uxorious at acon.dezign.dk
Fri May 27 02:41:47 UTC 2016

I'm not seeing ANY LVM volumes active on system boot.
(I'm not putting any of the necessary boot paths on LVM).

After booting the system, the volume is visible but not active.
If I put one of the drives in sftab, booting Ubuntu breaks.

Is there a workaround to make the system do "vgchange -a y" during boot?

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.

  LVM boot problem - volumes not activated after upgrade to Xenial

Status in lvm2 package in Ubuntu:

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages

  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup....'
  Please type in the full path...

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  Gave up waiting for root device. Common problems: ...
  ALERT! UUID=xxx-xxx.... does not exist.
  Dropping to a shell.

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  # lsb_release -rd
  Description:	Ubuntu 16.04 LTS
  Release:	16.04

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list