Hello,
On Sun, Oct 18, 2009 at 10:54 PM, Marc Haber
<mh+debian-b...@zugschlus.de> wrote:
> [...]
> device_whitelist: checking /etc/pmount.allow...
> comparing /dev/mapper/vg0-c_centos against whitelisted
> '/dev/mapper/vg0-c_centos'
> device_whitelisted(): /dev/mapper/vg0-c_centos matches, returning 1
> policy check passed
So far, so good...
> spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks'
> '/dev/mapper/vg0-c_centos'
> spawn(): /sbin/cryptsetup terminated with status 0
> spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'luksOpen'
> '/dev/mapper/vg0-c_centos' '_dev_mapper_vg0-c_centos'
> spawn(): /sbin/cryptsetup terminated with status 234
> Internal error: cryptsetup luksOpen failed mh$
This is a annoying; if I understand you right, it fails before
prompting for a password, doesn't it ?
> (please note the missing carriage return at the end of the error
> message).
This is not a big deal, most of the debugging messages miss the final "\n".
> However, manually invoking cryptsetup works just fine:
> $ sudo cryptsetup luksOpen /dev/mapper/vg0-c_centos _dev_mapper_vg0-c_centos
> [sudo] password for mh on swivel:
> Enter passphrase for /dev/mapper/vg0-c_centos:
> Key slot 0 unlocked.
> $ echo $?
> 0
> $
Could you try invoking isLuks beforehand ? Does it still work with
/sbin/cryptsetup ? (just being paranoid ;-) )
I can't have a look at it for now, I'll try to reproduce the problem home.
Cheers,
Vincent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
