Could this be solved with different ordering? Luks first, then bcache?
Luks definitely expects its header to be in a certain position:
LUKS EXTENSION
LUKS, the Linux Unified Key Setup, is a standard for disk encryption.
It adds a standardized header at the start of the device, a key-slot area
directly behind the header and the bulk data area behind that. The
whole set is called a 'LUKS container'. The device that a LUKS
container resides on is called a 'LUKS device'. For most purposes, both terms
can be used interchangeably. But note that when the LUKS header is at
a nonzero offset in a device, then the device is not a LUKS device
anymore, but has a LUKS container stored in it at an offset.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to bcache-tools in 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-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
