[dm-crypt] Accesing dm-crypt volume after failed resizing with mdadm/RAID1, dm-crypt/LUKS, LVM: debug output with new drive and eader from old drive

Paul Menzel pm.debian at googlemail.com
Thu Aug 4 08:19:46 CEST 2011


Dear dm-crypt folks,


with the restored LUKS header from the old drive on the new one, I get
the following output.

# cryptsetup --verbose --debug luksOpen /dev/sda2 sda2_crypt
# cryptsetup 1.3.0 processing "cryptsetup --verbose --debug luksOpen
/dev/sda2 sda2_crypt"
# Running command luksOpen.
# Locking memory.
# Allocating crypt device /dev/sda2 context.
# Trying to open and read device /dev/sda2.
# Initialising device-mapper backend, UDEV is enabled.
# Detected dm-crypt version 1.10.0, dm-ioctl version 4.19.1.
# Trying to load LUKS1 crypt type from device /dev/sda2.
# Initialising gcrypt crypto backend.
# Reading LUKS header of size 1024 from device /dev/sda2
# Timeout set to 0 miliseconds.
# Password retry count set to 3.
# Iteration time set to 1000 miliseconds.
# Activating volume sda2_crypt [keyslot -1] using [none] passphrase.
# dm status sda2_crypt  OF   [16384]
# Interactive passphrase entry requested.
Enter passphrase for /dev/sda2:
# Trying to open key slot 0 [ACTIVE_LAST].
# Reading key slot 0 area.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-4572
# Udev cookie 0xd4db0d4 (semid 0) created
# Udev cookie 0xd4db0d4 (semid 0) incremented
# Udev cookie 0xd4db0d4 (semid 0) incremented
# Udev cookie 0xd4db0d4 (semid 0) assigned to dm_task type 0 with flags 0xe
# dm create temporary-cryptsetup-4572
CRYPT-TEMP-temporary-cryptsetup-4572 OF   [16384]
# dm reload temporary-cryptsetup-4572  OF   [16384]
# dm resume temporary-cryptsetup-4572  OF   [16384]
# temporary-cryptsetup-4572: Stacking NODE_ADD (253,0) 0:6 0660
# temporary-cryptsetup-4572: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4db0d4 (semid 0) decremented
# Udev cookie 0xd4db0d4 (semid 0): Waiting for zero
# Udev cookie 0xd4db0d4 (semid 0) destroyed
# temporary-cryptsetup-4572: read ahead is 256
# temporary-cryptsetup-4572: Setting read ahead to 256
# Udev cookie 0xd4d7682 (semid 32768) created
# Udev cookie 0xd4d7682 (semid 32768) incremented
# Udev cookie 0xd4d7682 (semid 32768) incremented
# Udev cookie 0xd4d7682 (semid 32768) assigned to dm_task type 2 with flags 0x0
# dm remove temporary-cryptsetup-4572  OF   [16384]
# temporary-cryptsetup-4572: Stacking NODE_DEL (replaces other stacked ops)
# Udev cookie 0xd4d7682 (semid 32768) decremented
# Udev cookie 0xd4d7682 (semid 32768): Waiting for zero
# Udev cookie 0xd4d7682 (semid 32768) destroyed
# Trying to open key slot 1 [INACTIVE].
# Trying to open key slot 2 [INACTIVE].
# Trying to open key slot 3 [INACTIVE].
# Trying to open key slot 4 [INACTIVE].
# Trying to open key slot 5 [INACTIVE].
# Trying to open key slot 6 [INACTIVE].
# Trying to open key slot 7 [INACTIVE].
# No key available with this passphrase.
# Interactive passphrase entry requested.
[…]

For completeness please find the output of all three iterations attached.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 20110804--cryptsetup--luksOpen--on-new-drive-with-header-from-old-drive.debug
Type: application/octet-stream
Size: 7567 bytes
Desc: not available
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20110804/70a812b7/attachment.obj>


More information about the dm-crypt mailing list