Package: cryptmount
Version: 6.2.0-2
Followup-For: Bug #1072996
Dear Maintainer,
FWIW I am also observing this, but with a slightly different symptom:
$ cryptmount crypted
e2fsck 1.47.1 (20-May-2024)
/dev/mapper/crypted: clean, 456/28672 files, 58320/114688 blocks
[cryptmount-mount]: /home/l/crypted: fsconfig system call failed:
/dev/mapper/crypted: Can't lookup blockdev.
dmesg(1) may have more information after failed mount system call.
unable to stat() device node
Failed to remove device-mapper target "crypted"
dmesg said only:
[9999.9999] loop2: detected capacity change from 0 to 262144
So the system has been able to detect the size of the device, though it
still failed.
Adding "flags=nofsck" to cmtab also fixed my case.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (520, 'testing'), (510, 'stable'), (150, 'unstable'), (120,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.8.12-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cryptmount depends on:
ii libc6 2.38-13
ii libcryptsetup12 2:2.7.2-2
ii libdevmapper1.02.1 2:1.02.196-1+b1
ii libgcrypt20 1.10.3-3
ii libudev1 256.1-2
Versions of packages cryptmount recommends:
ii e2fsprogs 1.47.1-1
ii udev 256.1-2
Versions of packages cryptmount suggests:
ii dmsetup 2:1.02.196-1+b1
-- Configuration Files:
/etc/cryptmount/cmtab changed:
syncrypted {
dev=$(HOME)/crypted.vol
dir=$(HOME)/crypted
fstype=auto
flags=nofsck
keyformat=luks
}
-- no debconf information
