[Touch-packages] [Bug 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)
In case anyone is looking for a (sort of) workaround: a separate non-LVM boot partition (/boot as mountpoint) circumvents the problem. I'm not sure how easy this is to set up on an existing system. I had the luxury of being able to do a clean install without much trouble. Of course, this "workaround" is a bit heavy-handed, and should not be necessary at all, as grub2 supports booting from LVM. But at least it allows having the rest of the root filesystem on LVM volume(s). -- 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 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 -- 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
[Touch-packages] [Bug 1574333] Re: LVM-based server does not boot with kernel 4.4 (but works with 4.2)
The issue is still present with 4.4.0-42. It's completely preventing me from booting into Ubuntu. The error message is as follows: lvmetad is not active yet, using direct activation during sysinit rootfs: clean, 271911/1831424 files, 1561286/7323648 blocks Here, "rootfs" is my root filesystem (ext4), located on an LVM logical volume. I also tried the following kernels (from http://kernel.ubuntu.com/~kernel-ppa/mainline/) as well: - v4.4.14-xenial (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.14-xenial/) - v4.7.7 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7.7/) - v4.8.1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8.1/) I installed these by booting a live cd and chrooting into the "rootfs" filesystem, and then updating grub. The problem is still present in all of these kernels (with the slight variation that the error message is only shown briefly, and replaced by a blank screen) ** Summary changed: - LVM-based server does not boot with kernel 4.4 (but works with 4.2) + LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2) -- 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 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 -- 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
[Touch-packages] [Bug 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)
I edited the title, as it applies to desktop installs of xenial (such as mine) as well. -- 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 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 -- 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