Bug#492926: [pkg-cryptsetup-devel] Bug#492926: luksOpen fails, "Can not access device"
Hi Jonas, on Wed, Jul 30, 2008 at 16:17:40 +0200, you wrote: > Did you use cryptsetup 2:1.0.5-2 or a more recent version before you > upgraded to 2:1.0.6-4? I have had versions inbetween installed, but I have no idea when I last used cryptsetup... > [...] Did you verify that the device is not mapped already? No, I didn't. Apparently gnome-mount does map devices before it decides to not work and earlier cryptsetup versions were not disturbed by that... # dmsetup ls | grep ^luks luks_crypto_208517b4-b226-483c-bbce-9034b44ee971(253, 5) Maybe cryptsetup should have a more verbose error message, telling that the device is already mapped instead of the same message as for non-existing devices. elmar -- .'"`./"\ | :' : Elmar Hoffmann <[EMAIL PROTECTED]>ASCII Ribbon Campaign \ / `. `'GPG key available via pgp.netagainst HTML email X `-& vCards / \ signature.asc Description: Digital signature
Bug#492926: [pkg-cryptsetup-devel] Bug#492926: luksOpen fails, "Can not access device"
On 30/07/2008 Elmar Hoffman wrote: > luksOpen fails with the following error: > > # cryptsetup luksOpen /dev/sdc foo || echo $? > Command failed: Can not access device > 241 > > The device does exist and isLuks and luksDump do work as expected. > After downgrade to 2:1.0.5-2 luksOpen does work again. Hello Elmar, Did you use cryptsetup 2:1.0.5-2 or a more recent version before you upgraded to 2:1.0.6-4? Could you try version 2:1.0.6-1 from [1]? Are you sure that /dev/sdc is the device in question, and that you really want to luksopen the device directly, not only a partition, i.e. /dev/sdc1? Did you verify that the device is not mapped already? Please provide the output of the following commands: # /lib/udev/vol_id /dev/sdc # cryptsetup luksDump /dev/sdc # strace cryptsetup luksOpen /dev/sdc foo 2>&1 greetings, jonas [1] http://packages.debian.org/lenny/i386/cryptsetup/download signature.asc Description: Digital signature
Bug#492926: luksOpen fails, "Can not access device"
Package: cryptsetup Version: 2:1.0.6-4 Severity: normal luksOpen fails with the following error: # cryptsetup luksOpen /dev/sdc foo || echo $? Command failed: Can not access device 241 The device does exist and isLuks and luksDump do work as expected. After downgrade to 2:1.0.5-2 luksOpen does work again. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.25 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cryptsetup depends on: ii dmsetup 2:1.02.27-3 The Linux Kernel Device Mapper use ii libc62.7-12 GNU C Library: Shared libraries ii libdevmapper1.02.1 2:1.02.27-3 The Linux Kernel Device Mapper use ii libpopt0 1.14-4 lib for parsing cmdline parameters ii libuuid1 1.41.0-3universally unique id library cryptsetup recommends no packages. Versions of packages cryptsetup suggests: ii dosfstools2.11-6 utilities for making and checking pn initramfs-tools | linux-initr (no description available) ii udev 0.124-5/dev/ and hotplug management daemo -- no debconf information -- .'"`./"\ | :' : Elmar Hoffmann <[EMAIL PROTECTED]>ASCII Ribbon Campaign \ / `. `'GPG key available via pgp.netagainst HTML email X `-& vCards / \ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
