[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)
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=. 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
[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)
I found out that it wasn't the fact that I changed root=UUID=... that workaround the bug but the fact that I edited grub. It does not matter if I change or not settings. Just open the built-in editor and let it boot. -- 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=. 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
[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)
Maybe, this is the same https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547559 -- 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=. 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
[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)
I got again the same bug problem even still on 4.11.0-041100rc8-generic. It keeps failing even after a reboot. Again, I just changed root=UUID=... to root=/dev/sda6 and the system booted nicely. I'll attach a photo of the screen. It looks like two dumpstacks (interrupt during panic?) The error msg is: VFS: Unable to mount root fs on unknown-block(0,0) I guess the main stack is: dump_stack panic mount_block_root ? set_debug_rodata prepare_namespace kernel_init_fresable ? rest_init kernel_init ret_from_fork ** Attachment added: "screen photo" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686837/+attachment/4881676/+files/DSC_0153.JPG -- 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=. 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
[Kernel-packages] [Bug 1686837] Re: ubuntu fails to boot with btrfs root (unable to mount root)
I'm running now with 4.11.0-041100rc8-generic and until now, I was not able to reproduce the problem. Before using the upstream kernel, it was very frequent for me, happening after every reboot (and requiring me to boot rescue before a normal boot). It's very probable that upstream kernel is not affected. I updated the status and added the tag as requested. If I hit this problem again in the future, I'll make sure to update it back here. I can also test fixes if needed. ** Tags added: kernel-fixed-upstream -- 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=. 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
[Kernel-packages] [Bug 1686837] [NEW] ubuntu fails to boot with btrfs root (unable to mount root)
Public bug reported: 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=. 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. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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: New 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=. 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
[Kernel-packages] [Bug 1307105] Re: Kernel install fails due PAE checks
Ubuntu, just add forcepae for if used in install -- 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/1307105 Title: Kernel install fails due PAE checks Status in “linux” package in Ubuntu: Triaged Bug description: [TRIAGE NOTE] When a user boots Ubuntu Live/Install media with 'forcepae' option, the option should automatically be added to /etc/default/grub, or kernel upgrades will refuse to install when they do not see pae capability in cpuinfo. [ORIGINAL REPORT] On Thinkpad T42 with Pentium M processor linux image upgrade fails with message "This kernel does not support a non-PAE CPU.". System was installed from ubuntu-14.04-beta2-desktop-i386.iso with "forcepae" kernel option. After install, system works, but cannot be upgraded to laters kernel. root@t42:/boot# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-3.13.0-24-generic : Depends: linux-image-3.13.0-24-generic but it is not installed linux-image-generic : Depends: linux-image-3.13.0-24-generic but it is not installed E: Unmet dependencies. Try using -f. root@t42:/boot# apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: linux-image-3.13.0-24-generic Suggested packages: fdutils linux-doc-3.13.0 linux-source-3.13.0 linux-tools The following NEW packages will be installed: linux-image-3.13.0-24-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/14.6 MB of archives. After this operation, 32.3 MB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 196089 files and directories currently installed.) Preparing to unpack .../linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-24-generic /boot/vmlinuz-3.13.0-24-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.13.0-24-generic_3.13.0-24.46_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307105/+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
[Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
@l-colin, 14.04 works flawlessly in Celeron/Pentium M processor systems. You just need to add forcepae do the kernel command line (at boot) On a livecd, press anykey as soon as it loads (the first purple screen). Use the F6 option to add the forcepae. You'll have something like: "...initrd.lz quiet splash -- forcepae" The only problem is that 14.04 is not released yet. It might be released on April 17th. However, you can download the current development version at: http://cdimage.ubuntu.com/daily-live/current/trusty-desktop-i386.iso If you update packages after the 14.04 release date, it will update them to match the stable version. It will be some dozens of MB but, besides that, no greater side effect. -- 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/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux Status in “linux” package in Ubuntu: Fix Released Status in “syslinux” package in Ubuntu: Invalid Status in Baltix GNU/Linux: Triaged Bug description: Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error message about missing PAE feature in CPU, but *the same* *Ubuntu 12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB with GRUB boot loader, like Multisystem (http://liveusb.info/dotclear/index.php?pages/install ) is used! The error message is: "This kernel requires the following features not present on the CPU: pae. Unable to boot - please use a kernel appropriate for you CPU." THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in syslinux (or something related) forbids Ubuntu 12.04 installation. This bug is reproducible on lots of computers, there are several log files and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen this bug. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied MachineType: IBM 2373PPU dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373PPU dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373PPU dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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