19th September 2016, 13:43
(18th September 2016, 3:41)dbyentzen Wrote:(15th September 2016, 22:51)jdevney Wrote: Hi all,
I'm enjoying Maui, but almost had to wipe my installation like the OP.
The upgrade to 4.4.0-36-generic prevented my booting into my LUKS encrypted root partition. I just exited to the busybox ash shell.
Reverting to 4.4.0-34-generic resolved the problem.
Is anyone aware of issues with this kernel and encrypted filesystems?
Cheers, JD.
Hi JD,
I encountered the same problem and after a lot of searching on Google and Ubuntu Forums I was not able to achieve a solution. I use full disk encryption(FDE) and never considered this as contributing to the problem. In the end, I did a fresh install and decided not to update/upgrade via terminal but only use the update manager(advice from Maui's dev team). I hope in the future this problem will be resolved.
Best,
David
Thanks David,
I've done some digging and think I've found the problem: the initial ramdisk isn't compiled with all the required libraries for lvm & crypt.
Using this page: https://wiki.debian.org/InitramfsDebug it's possible to identify the libraries compiled into initramfs. I compared the two versions 0-34 & 0-36. Turns out that in Maui 4.4.0-36 it's missing some crucial ones relating to lvm & crypt. So basically it can't get past the ramdisk initialisation phase as the root filesystem can't be mounted from disk (I'm using lvm & encrypted partitions).
I was assuming that the kernel would be the same as that supplied by ubuntu 16.04 LTS. I guess the Maui build team compile their own kernel and enable/disable stuff as required.
I tried copying a new 4.4.0-36 initrd from kubuntu, but after booting with the kubuntu plymouth screen, this also dropped to the busybox shell - likely for different reasons though.
I've now reconfigured grub to boot from 4.4.0-34 so I'm all good again.
Cheers, JD.