From: Milan Broz <gmazyland@gmail.com>
To: David J Iannucci <pelcgfrghczy@punchcutter.ml1.net>,
cryptsetup@lists.linux.dev
Subject: Re: device-mapper: reload ioctl ... failed: No such file or directory
Date: Wed, 30 Oct 2024 08:10:43 +0100 [thread overview]
Message-ID: <1b63da83-8290-4d15-8f58-adf5ca6d903a@gmail.com> (raw)
In-Reply-To: <444a19f7-c557-4b7e-aad9-202a3f2e4876@app.fastmail.com>
Hi,
On 10/30/24 5:12 AM, David J Iannucci wrote:
> Hello,
>
> I'm using cryptsetup 2.7.5 on Gentoo to try to open an old TrueCrypt volume that I haven't
> looked at in at least a few years. Yes, I have the passphrase :=) Below is a trace of what's
> happening. Without --debug, all I see is the error message:
>
> device-mapper: reload ioctl on coreswp (254:0) failed: No such file or directory
>
> Any help in figuring this out would be much appreciated.
The log shows, that TrueCrypt part works, you have correct password.
The issue is only in the last step - activation through kernel dm-crypt.
I expect that you have device-mapper udev rules properly installed.
Is there anything in syslog? Kernel dm-crypt kernel module, is available?
Where it is mounted? (/mnt path) - some remote nfs/samba?
Could you try to copy the container to local fs and open it from there?
Also, try to open it read-only (-r flag).
(There were some issues with detecting direct-io, this tries to avoid them.)
Thanks,
Milan
...
> # Device-mapper backend running with UDEV support enabled.
> # dm status coreswp [ opencount noflush ] [16384] (*1)
> # Allocating a free loop device (block size: 512).
> # Trying to open and read device /dev/loop0 with direct-io.
> # Direct-io is supported and works.
> # Attached loop device block size is 512 bytes.
> # Calculated device size is 209714688 sectors (RW), offset 256.
> # Trying to activate TCRYPT device coreswp using cipher aes-xts-plain64.
> # DM-UUID is CRYPT-TCRYPT-coreswp
> # Udev cookie 0xd4dfe53 (semid 65598) created
> # Udev cookie 0xd4dfe53 (semid 65598) incremented to 1
> # Udev cookie 0xd4dfe53 (semid 65598) incremented to 2
> # Udev cookie 0xd4dfe53 (semid 65598) assigned to CREATE task(0) with flags DISABLE_LIBRARY_FALLBACK (0x20)
> # dm create coreswp CRYPT-TCRYPT-coreswp [ opencount flush ] [16384] (*1)
> # dm reload (254:0) [ opencount flush securedata ] [16384] (*1)
> device-mapper: reload ioctl on coreswp (254:0) failed: No such file or directory
> # Udev cookie 0xd4dfe53 (semid 65598) decremented to 1
> # Udev cookie 0xd4dfe53 (semid 65598) incremented to 2
> # Udev cookie 0xd4dfe53 (semid 65598) assigned to REMOVE task(2) with flags DISABLE_LIBRARY_FALLBACK (0x20)
> # dm remove coreswp [ opencount flush securedata ] [16384] (*1)
> # Uevent not generated! Calling udev_complete internally to avoid process lock-up.
> # Udev cookie 0xd4dfe53 (semid 65598) decremented to 1
> # DM create task failed, dm_task errno: 0.
> # dm versions [ opencount flush ] [16384] (*1)
> # dm status coreswp [ opencount noflush ] [16384] (*1)
> # Device status returned -19.
> # Data device /mnt/disk1/core.swp is OK.
> # No referenced device missing, some device in use.
> # Udev cookie 0xd4dfe53 (semid 65598) decremented to 0
> # Udev cookie 0xd4dfe53 (semid 65598) waiting for zero
> # Udev cookie 0xd4dfe53 (semid 65598) destroyed
> # Releasing crypt device /mnt/disk1/core.swp context.
> # Releasing device-mapper backend.
> # Closing read only fd for /mnt/disk1/core.swp.
> # Closed loop /dev/loop0 (/mnt/disk1/core.swp).
> Command failed with code -5 (device already exists or device is busy).
>
> ----end----
>
next prev parent reply other threads:[~2024-10-30 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1730260948-20104-mlmmj-67cc752c@lists.linux.dev>
2024-10-30 4:12 ` device-mapper: reload ioctl ... failed: No such file or directory David J Iannucci
2024-10-30 7:10 ` Milan Broz [this message]
2024-11-02 22:53 ` David J Iannucci
2024-11-02 23:34 ` Milan Broz
2024-11-09 23:31 ` David J Iannucci
2024-11-02 23:36 ` Michael Kjörling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b63da83-8290-4d15-8f58-adf5ca6d903a@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=pelcgfrghczy@punchcutter.ml1.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox