[Bug 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)
Frédéric Grosshans
frederic.grosshans at gmail.com
Sun Oct 23 16:11:37 UTC 2016
For 4.4.0-45, it only works in recovery mode, one hit on the return key
+ two confirmations to resume normal boot.
Everything works fine withe the 4.8.0-26 kernel of Yaketty Yak (Ubuntu
16.10)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1574333
Title:
LVM-based filesystem 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
More information about the foundations-bugs
mailing list