Re: device-mapper: reload ioctl ... failed: No such file or directory

On Sat, Nov 2, 2024, at 17:34, Milan Broz wrote:
>> Nov  2 16:31:36 linux kernel: loop0: detected capacity change from 0 to 209715200
>> Nov  2 16:31:36 linux kernel: device-mapper: table: 254:0: crypt: Error allocating crypto tfm
>> Nov  2 16:31:36 linux kernel: device-mapper: ioctl: error adding target to table
>
> Ok, *this* is the issue. Some kernel module is perhaps missing or misconfigured.
>
> According to log, aes-xts-plain64 should be your image cipher.
>
> Do you have aes, xts (and ecb, which xts internally use) kernel crypto
> modules compiled and available?

Apparently I didn't. I added those modules to my kernel, and then I was
able to open the volume, no problem. Thanks much :=)

> Does "cryptsetup benchmark --cipher aes-xts" work?

It does now!

I was putting together a new message here to ask for help with yet
another old TC volume, but I eventually figured out that I had the
wrong passphrase, and found that passphrase, so we're all good :=}
Seems strange to me that if the passphrase doesn't work, that it
doesn't simply tell you that... or maybe there's something about the
decrypting process that means that even cryptsetup can't necessarily
tell the difference between a wrong phrase and some other problem....
Anyway, no worries.

Thanks again,
Dave