Cryptsetup hangs like this:
$ sudo cryptsetup -v --debug luksOpen /dev/sdb sdb
... (stuff omitted)
Enter passphrase for /dev/sdb:
# Trying to open key slot 0 [ACTIVE_LAST].
# Reading key slot 0 area.
# Using userspace crypto wrapper to access keyslot area.
Key slot 0 unlocked.
# Calculated device size is 405504 sectors (RW), offset 4096.
# dm versions OF [16384] (*1)
# Device-mapper backend running with UDEV support enabled.
# dm create sdb CRYPT-LUKS1-f2a0b33c4cc846899c500848022f0e6a-sdb OF [16384]
(*1)
# dm reload sdb OF [16384] (*1)
# dm resume sdb OF [16384] (*1)
# sdb: Stacking NODE_ADD (253,0) 0:6 0660 [verify_udev]
# sdb: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4d949d (semid 0) decremented to 1
# Udev cookie 0xd4d949d (semid 0) waiting for zero
Installing debug symbols and attaching gdb to the cryptsetup process
reveals the following callstack:
#0 0x00007fb5ca2b0c47 in semop () at ../sysdeps/unix/syscall-template.S:84
#1 0x00007fb5c9d5c54c in _udev_wait (cookie=223188125) at libdm-common.c:2533
#2 dm_udev_wait (cookie=223188125) at libdm-common.c:2551
#3 0x00007fb5ca78df8b in _dm_create_device (name=name@entry=0x2265700 "sdb",
type=<optimized out>, type@entry=0x7fb5ca79998e "LUKS1", device=0x2265520,
flags=flags@entry=0, uuid=0x2265cb8 "f2a0b33c-4cc8-4689-9c50-0848022f0e6a",
size=405504,
params=0x2267478 "aes-xts-plain64
89e00160708f00e2323202aab3e1a7d115844b5da7d207a2e3576caa3abe4d44 0 /dev/sdb
4096", reload=0) at libdevmapper.c:621
#4 0x00007fb5ca78e476 in dm_create_device (cd=cd@entry=0x2265bd0,
name=name@entry=0x2265700 "sdb", type=type@entry=0x7fb5ca79998e "LUKS1",
dmd=dmd@entry=0x7fffe6e3e280, reload=reload@entry=0) at libdevmapper.c:665
#5 0x00007fb5ca7942a7 in LUKS1_activate (cd=cd@entry=0x2265bd0,
name=name@entry=0x2265700 "sdb", vk=<optimized out>, flags=flags@entry=0)
at keymanage.c:1124
#6 0x00007fb5ca787b67 in crypt_activate_by_passphrase (cd=0x2265bd0,
name=0x2265700 "sdb", keyslot=0, passphrase=0x0, passphrase_size=<optimized
out>,
flags=0) at setup.c:1997
#7 0x000000000040864c in ?? ()
#8 0x0000000000402fd0 in ?? ()
#9 0x00007fb5ca1c8830 in __libc_start_main (main=0x402b40, argc=6,
argv=0x7fffe6e3e648, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffe6e3e638) at
../csu/libc-start.c:291
#10 0x0000000000403759 in ?? ()
... so it's clearly waiting on a semaphore. Without looking at the code,
my guess is that it's waiting for udev to create a node for the device.
And that for some reason does not happen.
While cryptsetup is in this state, there is nothing in /dev/mapper
except for /dev/mapper/control. But dmsetup ls sees the device:
$ sudo dmsetup ls
sdb (253:0)
... so it really seems to me like the whole trouble is in the creation
of the appropriate /dev special file.
When I install cryptsetup, the issue goes away.
Interestingly, the issue also goes away when I mount the disk via the
GUI at least once (There is an encrypted disk icon in the panel.
Clicking it triggers a popup asking for the password. After I enter the
password, the disk is opened correctly.). After that, for some magical
reason, cryptsetup tool also works even w/o cryptsetup package. Event
after reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589083
Title:
crypsetup hangs when only cryptsetup-bin is installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
