Re: [dm-crypt] problems with a encrypted partition in fedora 12

[Richard <rz@linux-m68k.org>]

On Fri, Feb 18, 2011 at 12:38:00AM +0100, nettizen@gmail.com wrote:
> hi again,
> 
> i have got any information about my system,
> 
 
> ----------------------------------------------------------------------------------------------------------------------------
> 
> root@Microknoppix:~# cryptsetup --debug luksOpen /dev/sda3 vg_toshport_lv_root

this does not seem to be your main problem but if cryptsetup would succeed
you would still need to do a few other steps before having the volume group.
So instead of using "vg_toshport_lv_root" as arg to cryptsetup I would use 
another name, eg "dmsda3".


> # cryptsetup 1.1.3 processing "cryptsetup --debug luksOpen /dev/sda3
> vg_toshport_lv_root"
> # Locking memory.
> # Allocating crypt device /dev/sda3 context.
> # Trying to open and read device /dev/sda3.
> # Initialising device-mapper backend, UDEV is enabled.
> # Detected dm-crypt target of version 1.7.0.
> # Timeout set to 0 miliseconds.
> # Password retry count set to 3.
> # Iteration time set to 1000 miliseconds.
> # Password verification disabled.
> # Trying to load LUKS1 crypt type from device /dev/sda3.
> # Initializing crypto backend (using secure memory).
> # Reading LUKS header of size 1024 from device /dev/sda3
> # Activating volume vg_toshport_lv_root [keyslot -1] using [none] passphrase.
> # dm status vg_toshport_lv_root  OF   [16384]
> Enter passphrase for /dev/sda3:
> # Trying to open key slot 0 [3].
> # Reading key slot 0 area.
> # DM-UUID is CRYPT-TEMP-temporary-cryptsetup-11903
> # Udev cookie 0xd4d0a32 (semid 2064384) created
> # Udev cookie 0xd4d0a32 (semid 2064384) incremented
> # Udev cookie 0xd4d0a32 (semid 2064384) incremented
> # Udev cookie 0xd4d0a32 (semid 2064384) assigned to dm_task type 0
> with flags 0xe
> # dm create temporary-cryptsetup-11903
> CRYPT-TEMP-temporary-cryptsetup-11903 OF   [16384]
> # temporary-cryptsetup-11903: Stacking NODE_ADD (253,0) 0:6 0660
> # dm reload temporary-cryptsetup-11903  OF   [16384]
> # dm resume temporary-cryptsetup-11903  OF   [16384]
> # temporary-cryptsetup-11903: Stacking NODE_READ_AHEAD 256 (flags=1)
> # Udev cookie 0xd4d0a32 (semid 2064384) decremented
> # Udev cookie 0xd4d0a32 (semid 2064384): Waiting for zero
> # Udev cookie 0xd4d0a32 (semid 2064384) destroyed
> # temporary-cryptsetup-11903: read ahead is 256
> # temporary-cryptsetup-11903: Setting read ahead to 256
> # Udev cookie 0xd4dfe23 (semid 2097152) created
> # Udev cookie 0xd4dfe23 (semid 2097152) incremented
> # Udev cookie 0xd4dfe23 (semid 2097152) incremented
> # Udev cookie 0xd4dfe23 (semid 2097152) assigned to dm_task type 2
> with flags 0x0
> # dm remove temporary-cryptsetup-11903  OF   [16384]
> # temporary-cryptsetup-11903: Stacking NODE_DEL (replaces other stacked ops)
> # Udev cookie 0xd4dfe23 (semid 2097152) decremented
> # Udev cookie 0xd4dfe23 (semid 2097152): Waiting for zero
> # Udev cookie 0xd4dfe23 (semid 2097152) destroyed


no idea why it failed here.


Richard

---
Name and OpenPGP keys available from pgp key servers