Following up and to clarify my initial post a bit, I've found the main
issue is with cryptsetup (or related system) expecting LUKS to be
located within a certain boundary and bcache creates an offset on the
backing drive that shifts this boundary outside where cryptsetup looks.
The package should throw an exception or at the least say it didn't find
the partition but it fails silently and that will require further
investigation.
There is other strange behaviour when working with bcache created
partitions where bcache backed drives have been created but are then
accessed from another computer (where bcache-tools have not been
installed). These include some utilities throwing errors that the device
partition doesn't exist (when it clearly does) and the silent fail with
cryptsetup and devicemapper.
The drive can become accessible by mounting these systems using a loopback
offset such as the command below.
losetup -o 8192 /dev/loop8 /dev/sda3 will correct many of these problems.
** Also affects: bcache-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810235
Title:
cryptsetup silently fails in live environment
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1810235/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
