Shelby, It is something related to timing or something that is not correctly initialized. I have not seen the problem for sometime now. I'm using 18.04. Did you test it?
I don't know if it is fixed or not in recent releases. Maybe it's just that something changed that misaligned the planets needed to this bug to happen. Did you try to unplug/swap USB devices? -- 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: Expired 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 : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
