Bug ID 912170
Summary Boot fails with BTRFS RAID1 array as /home - open ctree failed
Classification openSUSE
Product openSUSE Distribution
Version 13.2
Hardware 64bit
OS openSUSE 13.2
Status NEW
Severity Major
Priority P5 - None
Component Kernel
Assignee kernel-maintainers@forge.provo.novell.com
Reporter RyanSKingsbury@alumni.utexas.net
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

I recently did a clean install of OpenSUSE 13.2 into a system with three drives
- 1 SSD containing the / partition (btrfs format with default subvolumes), and
2 identical HDD's containing /home in an encrypted BTRFS RAID1 array.
Initially, I was using only one of the HDD's as /home (still encrypted BTRFS).
Once I added the second drive and started the RAID1 mirroring, my system will
no longer boot without manual intervention. I get dropped into "emergency
mode", but then all I have to do is exit (Ctrl+D) to continue booting and
everything works normally.

The last entry in the system log before Emergency Mode is invoked is:
Code:

BTRFS: open_ctree failed

It appears that a similar (maybe the same) bug was reported on ArchWiki:
https://wiki.archlinux.org/index.php/Btrfs#BTRFS:_open_ctree_failed

But the solution refers to mkinitcpio rather than dracut that OpenSUSE uses, so
I'm unsure how to apply it to my system.


Some relevant system information:

excerpt from /etc/fstab:
----
# encrypted RAID1 array containing /home
UUID=e91f611f-524a-43f5-bde5-8ebb9672f146 /home btrfs defaults 0 0
----

/etc/crypttab:
----
encrypted-home-sdb UUID=9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1 none luks, retry=1
encrypted-home-sdc UUID=b82e5894-cea2-4fe7-a0a5-80f918e9db61 none luks, retry=1
----

excerpt from fdisk -l:
----
Device     Start        End    Sectors   Size Type
/dev/sdb1   2048 1953523711 1953521664 931.5G Microsoft basic data

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: CAC38602-D5A5-4F28-8344-65B559124514

Device     Start        End    Sectors   Size Type
/dev/sdc1   2048 1953525134 1953523087 931.5G Linux filesystem

Disk /dev/mapper/encrypted-home-sdc: 931.5 GiB, 1000201723392 bytes, 1953518991
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/encrypted-home-sdb: 931.5 GiB, 1000200994816 bytes, 1953517568
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
----

Device UUID's:
----
/dev/sda1: UUID="04e20317-f554-43cf-a95d-b0385ebd22bb"
UUID_SUB="cb9dc431-1855-466b-ae9a-5c0ddcd7f95a" TYPE="btrfs" PTTYPE="dos"
PARTLABEL="primary" PARTUUID="860c637a-83c8-4399-8dc4-5b5ab66c0f06" 
/dev/sdb1: UUID="9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1" TYPE="crypto_LUKS"
PARTLABEL="primary" PARTUUID="532a7bd2-6774-422e-90c0-31f19796098d" 
/dev/sdc1: UUID="1ca9d3ba-c409-4127-91f5-e3d9c21242bd" TYPE="crypto_LUKS"
PARTLABEL="Linux filesystem" PARTUUID="5a6830cc-9064-476c-aa79-6189dd0964bd" 
/dev/mapper/encrypted-home-sdc: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146"
UUID_SUB="6007c4c7-5119-4b0f-ab21-134832c4774c" TYPE="btrfs" 
/dev/mapper/encrypted-home-sdb: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146"
UUID_SUB="020bae26-b64f-413e-8263-a6e832ccb224" TYPE="btrfs"
----


You are receiving this mail because: