Hey Markus, hey Milan,

On 08/07/2010 Milan Broz wrote:
> On 07/08/2010 08:22 AM, Markus Melms wrote:
> > r...@playstation:# cryptsetup luksDump /dev/sda3
> > Aufruf fehlgeschlagen: /dev/sda3 is not a LUKS partition 
> > # "Aufruf fehlgeschlagen" means sth. like "Command failed"
> > 
> > r...@playstation:# cat /etc/crypttab 
> > # <target name>     <source device>         <key file>
> > # <options>
> > cryptofs    /dev/sda3               none
> > check,tries=3,cipher=aes-cbc-essiv:sha256,loud
> 
> ok, so it is plain crypt device, not LUKS. So not problem
> with cryptsetup itself - here it simply takes passwords, hash it and
> use as key.

maybe it's a hardware issue?

> I think problem is either in some udev rule or in "check" script,
> which waits for something but this is Debian specific.

Markus, did you change anything in /etc/default/cryptdisks? otherwise
the default check script in 2:1.0.6-7 was 'vol_id', which does nothing
more than '/lib/udev/vol_id -t $dev'. Just give it a try manually:

# /lib/udev/vol_id -t /dev/mapper/cryptofs

Do you have custom udev rules?

Please could you change the shebang line (first script line) of
/etc/init.d/cryptdisks-early to '#!/bin/sh -x' to see where exactly the
long delay happens? be warned that a lot of debugging messages will be
printed to boot screen.

greetings,
 jonas

Attachment: signature.asc
Description: Digital signature

Reply via email to