This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1686837
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1686837
Title:
ubuntu fails to boot with btrfs root (unable to mount root)
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
Failing to mount / as btrfs has been haunting btrfs users on ubuntu
for some time. Coming and going with kernel updates.
After I upgraded to 17.04, it seems that the problem is back.
It seems that a non-clean umount reboot always leads to a non-bootable
system. If I boot into rescue (selecting in grub, not a livecd), kernel can
find the root partition. I can also boot normally if root=... kernel parameter
is set with the device name (/dev/sda6) instead of UUID=xxxx.
So, there might be a bug in kernel that does not allow linux to identify the
boot partition using UUID in some circumstances (probably after a dirt reboot).
Maybe other distros do some magic at initrd that cleans the btrfs
problem because some, like opensuse, do uses btrfs as default root fs.
Anyway, even ubuntu own rescue can boot normally.
This is a tricky bug to debug as I get no logs written and no
emergency shell. Just an ugly kernel error and a backstack.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686837/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
