On 08/07/2010 Jonas Meurer wrote: > > Last line before prompting for passphrase is like: > > cryptsetup -c -aes-... --key-file=- create cryptofs /dev/sda3 > > After waiting 50 secs, first line is: > > '[' -z /lib/cryptsetup/checks/vol_id ']' > > this verifies, that the delay is caused by cryptsetup binary, not by > anything else from the initscript. you could check the unlocking > by booting into single user runlevel (init=1), and manually invoking > > # cryptsetup -c aes-cbc-essiv:sha256 create cryptofs /dev/sda3 > > simply let the unlocking process fail three times (wrong passphrase), > and the boot process will stop at runlevel 1 with an emergency shell. > there you can test the manual unlocking of encrypted device. > > if this works, and the delay is reproducible at the emergency shell, > please also provide output of 'cryptsetup --debug -c aes-... create ...'
any news? greetings, jonas
signature.asc
Description: Digital signature
