Bug 1394545

Summary: Failed to mount encrypted btrfs sysroot
Product: [Fedora] Fedora Reporter: Vasilis Keramidas <keramidasceid>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dracut-maint-list, gansalmon, harald, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, zbyszek
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:17:43 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:
Attachments:
Description Flags
rdsosreport none

Description Vasilis Keramidas 2016-11-13 10:25:33 UTC
Created attachment 1220131 [details]
rdsosreport

Description of problem:
When i start my fedora it fails to mount my encrypted btrfs disk

Version-Release number of selected component (if applicable):


How reproducible:
Boot the machine

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Harald Hoyer 2016-11-16 11:19:54 UTC
[   15.141911] localhost systemd[1]: Mounting /sysroot...
[   15.159840] localhost kernel: BTRFS info (device dm-1): disk space caching is enabled
[   15.159845] localhost kernel: BTRFS: has skinny extents
[   15.182638] localhost kernel: BTRFS: detected SSD devices, enabling SSD mode
[  105.348354] localhost systemd[1]: sysroot.mount: Mounting timed out. Stopping.

no clue... luks is decrypted, btrfs kernel module says it's mounting dm-1, but apparently it's not happening.

you could try btrsfsck in the initramfs:

# btrfsck /dev/mapper/luks-87229226-c086-4906-aec1-75c84a169a78


reassigning to component kernel

Comment 2 Justin M. Forbes 2017-04-11 14:44:55 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2017-04-28 17:17:43 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.