All of lore.kernel.org
 help / color / mirror / Atom feed
* [dm-crypt] problems with a encrypted partition in fedora 12
@ 2011-02-16 17:49 nettizen
  2011-02-17 23:38 ` nettizen
  0 siblings, 1 reply; 4+ messages in thread
From: nettizen @ 2011-02-16 17:49 UTC (permalink / raw)
  To: dm-crypt

hi,

first, sorry for my awful english and thanks in advance for you time!

i have a encrypted partition with fedora 12 (all system is into this
partition that i made with the anaconda installator by default
following the instructions one year ago) and suddenly yesterday i
tried to access to my laptop after to have "hibernated" it and system
doesn't recognize my password. if i put text mode, a message is on the
screen:

[WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d]

[Password for /dev/sda3 (luks-f59...):]

right now, i put my pass as usual, and surprise!

[No key available with this passphrase]

and three times after a new message is on the screen:

[WARNING: Deprecated config file /etc/modprobe.conf, all config files
belong into /etc/modprobe.d/.]

this message is repeated any rows and a new mensaje ...

[No root device found
[drm:drm_mode_rmfb] *ERROR*tried to remove a fb that we didin't own]

[Boot has failed, sleepìng forever]

well, and now a cold chill moved my body...

i have just tried to access to my encrypted partition through a file
manager as root and when i try to access to /sda3 (my full encrypted
system partition) this is the message:

[Error unlocking device: cryptsetup exited with exit code 255:
device-mapper: remove ioctl failed: Device or resource busy No key
avalaible with this passphrase]

i have a boot partition in /sda2 with a 2.6.36-175.fc12.i86.PAE kernel
with an instruction by default [ro
root=/dev/mapper/vg_toshport_lv_root]

obviously, my big big problem is that the file system is into my encrypted /sda3

again, sorry for my poor words and if you have any good idea about my
question, i will be grateful for you forever!

ciao!

ruben

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] problems with a encrypted partition in fedora 12
  2011-02-16 17:49 [dm-crypt] problems with a encrypted partition in fedora 12 nettizen
@ 2011-02-17 23:38 ` nettizen
  2011-02-18  0:07   ` Richard
  0 siblings, 1 reply; 4+ messages in thread
From: nettizen @ 2011-02-17 23:38 UTC (permalink / raw)
  To: dm-crypt

hi again,

i have got any information about my system,

first, LUKS header information

-----------------------------------------------------------------------------------------------------
root@Microknoppix:~# cryptsetup luksDump /dev/sda3
LUKS header information for /dev/sda3

Version:           1
Cipher name:       aes
Cipher mode:       xts-plain
Hash spec:         sha1
Payload offset:    4040
MK bits:           512
MK digest:         c4 c6 95 ef c4 2a 68 5f 11 83 4b 2f 77 4f a9 c6 68 f1 9d be
MK salt:           07 d3 b8 af 90 6d 8a 34 98 42 8c 1a c5 c4 7e 36
                   0a de 12 40 d4 3d 20 8c d0 0e a8 2e 53 06 0d 72
MK iterations:     10
UUID:              f591ec0a-5fee-4e3a-90ad-4d8ae733b616

Key Slot 0: ENABLED
    Iterations:             84638
    Salt:                   05 99 cc ff d8 6b 64 b3 04 54 a3 ed 21 91 06 c8
                              f4 9f 57 34 53 14 31 34 3e 00 99 9c 14 94 d5 98
    Key material offset:    8
    AF stripes:                4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED

=================================================================

and second, cryptsetup --debug

----------------------------------------------------------------------------------------------------------------------------

root@Microknoppix:~# cryptsetup --debug luksOpen /dev/sda3 vg_toshport_lv_root
# 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
# Trying to open key slot 1 [1].
# Trying to open key slot 2 [1].
# Trying to open key slot 3 [1].
# Trying to open key slot 4 [1].
# Trying to open key slot 5 [1].
# Trying to open key slot 6 [1].
# Trying to open key slot 7 [1].
No key available with this passphrase.
Enter passphrase for /dev/sda3:


after 3 times:

No key available with this passphrase.
# Releasing crypt device /dev/sda3 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code 1: No key available with this passphrase.

=============================================================

please, any idea to help me!

thanks a lot

ruben


On Wed, Feb 16, 2011 at 6:49 PM,  <nettizen@gmail.com> wrote:
> hi,
>
> first, sorry for my awful english and thanks in advance for you time!
>
> i have a encrypted partition with fedora 12 (all system is into this
> partition that i made with the anaconda installator by default
> following the instructions one year ago) and suddenly yesterday i
> tried to access to my laptop after to have "hibernated" it and system
> doesn't recognize my password. if i put text mode, a message is on the
> screen:
>
> [WARNING: Deprecated config file /etc/modprobe.conf, all config files
> belong into /etc/modprobe.d]
>
> [Password for /dev/sda3 (luks-f59...):]
>
> right now, i put my pass as usual, and surprise!
>
> [No key available with this passphrase]
>
> and three times after a new message is on the screen:
>
> [WARNING: Deprecated config file /etc/modprobe.conf, all config files
> belong into /etc/modprobe.d/.]
>
> this message is repeated any rows and a new mensaje ...
>
> [No root device found
> [drm:drm_mode_rmfb] *ERROR*tried to remove a fb that we didin't own]
>
> [Boot has failed, sleepìng forever]
>
> well, and now a cold chill moved my body...
>
> i have just tried to access to my encrypted partition through a file
> manager as root and when i try to access to /sda3 (my full encrypted
> system partition) this is the message:
>
> [Error unlocking device: cryptsetup exited with exit code 255:
> device-mapper: remove ioctl failed: Device or resource busy No key
> avalaible with this passphrase]
>
> i have a boot partition in /sda2 with a 2.6.36-175.fc12.i86.PAE kernel
> with an instruction by default [ro
> root=/dev/mapper/vg_toshport_lv_root]
>
> obviously, my big big problem is that the file system is into my encrypted /sda3
>
> again, sorry for my poor words and if you have any good idea about my
> question, i will be grateful for you forever!
>
> ciao!
>
> ruben
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] problems with a encrypted partition in fedora 12
  2011-02-17 23:38 ` nettizen
@ 2011-02-18  0:07   ` Richard
  2011-02-18  0:21     ` nettizen
  0 siblings, 1 reply; 4+ messages in thread
From: Richard @ 2011-02-18  0:07 UTC (permalink / raw)
  To: nettizen; +Cc: dm-crypt

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dm-crypt] problems with a encrypted partition in fedora 12
  2011-02-18  0:07   ` Richard
@ 2011-02-18  0:21     ` nettizen
  0 siblings, 0 replies; 4+ messages in thread
From: nettizen @ 2011-02-18  0:21 UTC (permalink / raw)
  Cc: dm-crypt

thx! richards

i tried your advise and sadly i think is the same output :)

---------------------------------------------------------------------------------------------------------------------------

root@Microknoppix:~# cryptsetup --debug luksOpen /dev/sda3 dmsda3
# cryptsetup 1.1.3 processing "cryptsetup --debug luksOpen /dev/sda3 dmsda3"
# 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 dmsda3 [keyslot -1] using [none] passphrase.
# dm status dmsda3  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-19767
# Udev cookie 0xd4df63e (semid 2457600) created
# Udev cookie 0xd4df63e (semid 2457600) incremented
# Udev cookie 0xd4df63e (semid 2457600) incremented
# Udev cookie 0xd4df63e (semid 2457600) assigned to dm_task type 0
with flags 0xe
# dm create temporary-cryptsetup-19767
CRYPT-TEMP-temporary-cryptsetup-19767 OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_ADD (253,0) 0:6 0660
# dm reload temporary-cryptsetup-19767  OF   [16384]
# dm resume temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4df63e (semid 2457600) decremented
# Udev cookie 0xd4df63e (semid 2457600): Waiting for zero
# Udev cookie 0xd4df63e (semid 2457600) destroyed
# temporary-cryptsetup-19767: read ahead is 256
# temporary-cryptsetup-19767: Setting read ahead to 256
# Udev cookie 0xd4d5bdf (semid 2490368) created
# Udev cookie 0xd4d5bdf (semid 2490368) incremented
# Udev cookie 0xd4d5bdf (semid 2490368) incremented
# Udev cookie 0xd4d5bdf (semid 2490368) assigned to dm_task type 2
with flags 0x0
# dm remove temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_DEL (replaces other stacked ops)
# Udev cookie 0xd4d5bdf (semid 2490368) decremented
# Udev cookie 0xd4d5bdf (semid 2490368): Waiting for zero
# Udev cookie 0xd4d5bdf (semid 2490368) destroyed
# Trying to open key slot 1 [1].
# Trying to open key slot 2 [1].
# Trying to open key slot 3 [1].
# Trying to open key slot 4 [1].
# Trying to open key slot 5 [1].
# Trying to open key slot 6 [1].
# Trying to open key slot 7 [1].
No key available with this passphrase.
Enter passphrase for /dev/sda3:
# Trying to open key slot 0 [3].
# Reading key slot 0 area.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-19767
# Udev cookie 0xd4d4e2f (semid 2523136) created
# Udev cookie 0xd4d4e2f (semid 2523136) incremented
# Udev cookie 0xd4d4e2f (semid 2523136) incremented
# Udev cookie 0xd4d4e2f (semid 2523136) assigned to dm_task type 0
with flags 0xe
# dm create temporary-cryptsetup-19767
CRYPT-TEMP-temporary-cryptsetup-19767 OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_ADD (253,0) 0:6 0660
# dm reload temporary-cryptsetup-19767  OF   [16384]
# dm resume temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4d4e2f (semid 2523136) decremented
# Udev cookie 0xd4d4e2f (semid 2523136): Waiting for zero
# Udev cookie 0xd4d4e2f (semid 2523136) destroyed
# temporary-cryptsetup-19767: read ahead is 256
# temporary-cryptsetup-19767: Setting read ahead to 256
# Udev cookie 0xd4dd25c (semid 2555904) created
# Udev cookie 0xd4dd25c (semid 2555904) incremented
# Udev cookie 0xd4dd25c (semid 2555904) incremented
# Udev cookie 0xd4dd25c (semid 2555904) assigned to dm_task type 2
with flags 0x0
# dm remove temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_DEL (replaces other stacked ops)
# Udev cookie 0xd4dd25c (semid 2555904) decremented
# Udev cookie 0xd4dd25c (semid 2555904): Waiting for zero
# Udev cookie 0xd4dd25c (semid 2555904) destroyed
# Trying to open key slot 1 [1].
# Trying to open key slot 2 [1].
# Trying to open key slot 3 [1].
# Trying to open key slot 4 [1].
# Trying to open key slot 5 [1].
# Trying to open key slot 6 [1].
# Trying to open key slot 7 [1].
No key available with this passphrase.
Enter passphrase for /dev/sda3:
# Trying to open key slot 0 [3].
# Reading key slot 0 area.
# DM-UUID is CRYPT-TEMP-temporary-cryptsetup-19767
# Udev cookie 0xd4ddda0 (semid 2588672) created
# Udev cookie 0xd4ddda0 (semid 2588672) incremented
# Udev cookie 0xd4ddda0 (semid 2588672) incremented
# Udev cookie 0xd4ddda0 (semid 2588672) assigned to dm_task type 0
with flags 0xe
# dm create temporary-cryptsetup-19767
CRYPT-TEMP-temporary-cryptsetup-19767 OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_ADD (253,0) 0:6 0660
# dm reload temporary-cryptsetup-19767  OF   [16384]
# dm resume temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4ddda0 (semid 2588672) decremented
# Udev cookie 0xd4ddda0 (semid 2588672): Waiting for zero
# Udev cookie 0xd4ddda0 (semid 2588672) destroyed
# temporary-cryptsetup-19767: read ahead is 256
# temporary-cryptsetup-19767: Setting read ahead to 256
# Udev cookie 0xd4de561 (semid 2621440) created
# Udev cookie 0xd4de561 (semid 2621440) incremented
# Udev cookie 0xd4de561 (semid 2621440) incremented
# Udev cookie 0xd4de561 (semid 2621440) assigned to dm_task type 2
with flags 0x0
# dm remove temporary-cryptsetup-19767  OF   [16384]
# temporary-cryptsetup-19767: Stacking NODE_DEL (replaces other stacked ops)
# Udev cookie 0xd4de561 (semid 2621440) decremented
# Udev cookie 0xd4de561 (semid 2621440): Waiting for zero
# Udev cookie 0xd4de561 (semid 2621440) destroyed
# Trying to open key slot 1 [1].
# Trying to open key slot 2 [1].
# Trying to open key slot 3 [1].
# Trying to open key slot 4 [1].
# Trying to open key slot 5 [1].
# Trying to open key slot 6 [1].
# Trying to open key slot 7 [1].
No key available with this passphrase.
# Releasing crypt device /dev/sda3 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code 1: No key available with this passphrase.

--------------------------------------------------------------------------------------------------------------------------

ciao!

ruben


On Fri, Feb 18, 2011 at 1:07 AM, Richard <rz@linux-m68k.org> wrote:
> 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
>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-02-18  0:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-02-16 17:49 [dm-crypt] problems with a encrypted partition in fedora 12 nettizen
2011-02-17 23:38 ` nettizen
2011-02-18  0:07   ` Richard
2011-02-18  0:21     ` nettizen

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.