Didn't wait long enough - eventually got a "couldn't stat the resume device file ' ...
then got the option to continue boot and it worked. After boot verified the existence of the file noted above that couldn't be stat'ed - no obvious problem there. On next boot, problem re-occurred. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based server does not boot with kernel 4.4 (but works with 4.2) Status in lvm2 package in Ubuntu: Confirmed Bug description: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. 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 (rw,relatime,nospace_cache,subvolid=256,subvol=/@) /dev/mapper/clio-root on /mnt/clio-root type btrfs (rw,relatime,nospace_cache,subvolid=5,subvol=/) /dev/mapper/clio-root on /home type btrfs (rw,relatime,nospace_cache,subvolid=257,subvol=/@home) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+subscriptions -- 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
