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

On 2 Nov 2024 16:53 -0600, from [email protected] (David J Iannucci):
>> I expect that you have device-mapper udev rules properly installed.
> 
> I'm not sure - how can I check this? This is a fairly bare-bones Gentoo
> install and I'm not a big expert on everything that I should be, so that
> might have slipped through the cracks.
> 
> But...! I just found something... it seems I am running a systemd-udevd,
> which would not have been my choice... I have taken steps to keep
> systemd completely off my machine, so this is a surprise. Will consult
> Gentoo forums about this.
> 
>> Is there anything in syslog?
> 
> This is what comes out in /var/log/messages:
> 
> 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

Just to rule out the possibility of this being caused by something
about your kernel build settings etc., would you be willing to try
booting a binary, general-purpose distribution like a recent Debian or
Fedora and unlocking the volume from within there, and let us know how
that goes?

The error that shows up in your logs certainly matches Milan Broz's
conclusion earlier: that the problem is during the actual mapping
setup, which happens after passphrase validation.


> p.s. I note that simple reply on this list goes only to the sender
>      rather than back to the list, which is maybe the way the list
>      prefers it? Though in my experience most tech lists like to keep
>      this kind of discussion on the list so that more eyes are on
>      things, and solutions are documented, but if that's not the case
>      here, kindly let me know and I'll use simple reply to individuals
>      from now on.

Overriding the preferences of the original sender as well as making
life more difficult for the person replying is generally not a good
idea. "Reply-To munging considered harmful" was an argument made,
what, two decades ago, or more? Use the "group reply" / "reply to all"
or list reply feature provided by your mail client if you want your
reply to go to the list; use the sender reply function if you want
your reply to go only to the sender of the message you're replying to.

-- 
Michael Kjörling
🔗 https://michael.kjorling.se