I'll back up Tjalling's work-around. I already had my boot partition on
a separate non-LVM partition at the front of my drive. My system started
booting normally on 4.4.0-38, and continues to do so on 4.4.0-42.

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

  LVM-based filesystem does not boot with kernel 4.4 (but works with

Status in lvm2 package in Ubuntu:

Bug description:
  I‘ve updated my home-made NAS from wily to xenial and it stopped

  Selecting the 4.2 kernel on the grub menu makes it work again.

  The working kernel is 4.2.0-35-generic

  The failing kernel is 4.4.0-21-generic.

  When the booting sequence freezes, I can have a terminal with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
  /dev/mapper/clio-root on /home type btrfs 

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to