OK this is really strange now. Kernel 4.4.0-16 does boot now. I did some troubleshooting after i opened this bug. I edited /etc/default/grub to disable splash + quiet mode, disabled recovery mode, increased the waittime before the default grub entry gets active and played with some "root=..." parameters. After every change i used "sudo update-grub" to make the change active. But the issue still exist. So i continued to use Kernel 4.4.0-15.
Some hours later i updated tzdata and still continued to use Kernel 4.4.0-15. 1 or 2 days later i forgot to manually choose Kernel 4.4.0-15 in the grub menu and Kernel 4.4.0-16 booted but this time successfull. There was no other change than the tzdata update. - related history.log entries ... Start-Date: 2016-03-30 18:54:38 Commandline: apt-get dist-upgrade Requested-By: steven (1000) Install: linux-image-extra-4.4.0-16-generic:amd64 (4.4.0-16.32, automatic), linux-headers-4.4.0-16-generic:amd64 (4.4.0-16.32, automatic), linux-headers-4.4.0-16:amd64 (4.4.0-16.32, automatic), linux-image-4.4.0-16-generic:amd64 (4.4.0-16.32, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.15.16, 4.4.0.16.17), linux-image-generic:amd64 (4.4.0.15.16, 4.4.0.16.17), linux-generic:amd64 (4.4.0.15.16, 4.4.0.16.17) End-Date: 2016-03-30 18:55:30 Start-Date: 2016-03-30 20:25:28 Commandline: apt-get upgrade Requested-By: steven (1000) Upgrade: tzdata:amd64 (2016c-0ubuntu1, 2016c-1) End-Date: 2016-03-30 20:25:30 ... Due to work i couldn't continue the troubleshooting until now. I rolled back the /etc/default/grub changes but i couldn't reproduce the issue anymore. Kernel 4.4.0-16 still boots successfull. So i didn't test the latest mainline/upstream kernel. I think we can close the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563998 Title: Ubuntu 16.04 Kernel 4.4.0-16 doesn't boot, cannot open root device Status in linux package in Ubuntu: Incomplete Bug description: - Thinkpad X230, latest Bios, BIOS Legacy Boot active - Ubuntu 16.04 - Kernel 4.4.0-16 - dm-crypt / LUKS full disk encryption setup during install with BTRFS as filesystems - partion layout: steven@thinkpad:~$ blkid /dev/mapper/sdb2_crypt: UUID="DiTDe3-wjSv-YCFz-Lful-KBMl-BCWr-t2Jzry" TYPE="LVM2_member" /dev/mapper/vg_crypt-lv_root: LABEL="ROOT" UUID="0760638f-92f7-4bd9-a5b8-638002a1d699" UUID_SUB="b8c21ae4-99c7-470f-a2a1-24308c5177e7" TYPE="btrfs" /dev/sda1: LABEL="BOOT" UUID="895c6d03-cc2d-4303-b59e-eb8f5b6452f2" UUID_SUB="7e9d110f-7a6f-4c21-8438-e746acf53b9a" TYPE="btrfs" PARTUUID="83f8d594-01" /dev/sda2: UUID="0ce18f8a-9317-40c6-bb1d-cc5608b3b58d" TYPE="crypto_LUKS" PARTUUID="83f8d594-02" /dev/mapper/vg_crypt-lv_swap: UUID="8010fb1a-fdc0-40d6-a241-1d52d2a89f8f" TYPE="swap" - since Kernel 4.4.0-16-generic the system doesn't boot, it shows a "VFS: Cannot open root device "mapper/vg_crypt-lv_root" or unknown-block(0,0): error -6" error - see attached screenshots for more detailed error message - if i boot Kernel 4.4.0-15-generic then the boot is successfull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
