Bug 1013397
Summary: | Unable to boot with btrfs root partition after upgrade to 3.10.12-100 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Marcin Zajaczkowski <mszpak> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-01 20:14:18 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Marcin Zajaczkowski
2013-09-29 22:37:45 UTC
Please provide the output of: lsinitrd /boot/initramfs-3.10.12-100.fc18.x86_64.img | grep btrfs and also the output of dmesg on a failing boot. You should be able to save that into the /boot partition from the dracut shell. $ sudo lsinitrd /boot/initramfs-3.10.12-100.fc18.x86_64.img | grep btrfs -rw-r--r-- 1 root root 392 Aug 19 01:31 etc/udev/rules.d/80-btrfs.rules drwxr-xr-x 1 root root 0 Aug 19 01:31 usr/lib/modules/3.10.12-100.fc18.x86_64/kernel/fs/btrfs -rw-r--r-- 1 root root 1290343 Aug 19 01:31 usr/lib/modules/3.10.12-100.fc18.x86_64/kernel/fs/btrfs/btrfs.ko -rwxr-xr-x 1 root root 266720 Aug 19 01:31 usr/sbin/btrfs -rwxr-xr-x 1 root root 203552 Aug 19 01:31 usr/sbin/btrfsck -rwxr-xr-x 1 root root 707 Aug 19 01:31 usr/sbin/btrfs_finished -rwxr-xr-x 1 root root 256 Aug 19 01:31 usr/sbin/btrfs_timeout (Aug 19 01:31 is a date when I rebuilded initramfs - I have problem with time synchronisation) I will try to get the output of dmesg shortly. Hmm, I'm not able to reproduce it anymore. Very strange. I did some kernel related changes in the mean time, but I don't know what could "fix" my problem. I attach a detailed information about my changes, maybe you will have some idea. Everything was done after an initramfs image was regenerated and a try to boot with it failed (with the btrfs error). I tried to install VirtualBox and I downgraded kernel-keaders to 3.9.11-200. I rebuilded vbox modules, but I was unable to load them due to "ERROR: could not insert 'vboxdrv': Required key not available". I disabled secure boot in BIOS and was able to use VirtualBox. Later I tried to reproduce a problem with btrfs but without success. I reanabled secure boot, upgraded kernel-headers, but 3.10.12-100 still boots without problems. I have no idea. If you can't recreate it now, we might as well close the bug. In that case I'm closing the bug. Thanks for your support. |