*** This bug is a duplicate of bug 1362884 ***
https://bugs.launchpad.net/bugs/1362884
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 1362884 ***
https://bugs.launchpad.net/bugs/1362884
Here is the dmesg output at the time of the error message:
[8.515396] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid 2
transid 100593 /dev/dm-0
[8.525319] BTRFS info (device dm-0): e
** Package changed: ubuntu => upstart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree failed
To manage notifications a
Today's update to the 3.13.46-77 kernel did not change the behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree failed
To
OK, the workaround from OpenSUSE did NOT work (with the 3.16 kernel).
Same behavior as before. The steps I performed were:
copy /lib/udev.rules.d/64-btrfs.rules to /etc/udev/64-btrfs.rules
The line
IMPORT{builtin}="btrfs ready $devnode"
was already present in the original rules file, so I did n
