Re: Possible to utilise drives from broken OS?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jul 26, 2006 at 09:50:42AM -0500, Default User wrote:
> Arno,
> 
> Thank you for your prompt reply.  Unfortunately, I've not had any success.
> Please see below.  I've googled for almost the entire night, and haven't
> been able to find anything that sets off any flags that meet the conditions
> of my system for why this isn't working.
[...]
> dm-crypt is enabled in the kernel, as is the cipher used.
> I've removed the old packages, and reinstalled in the following order, the
> packages below:
> devmapper-1.02.07.orig, libgpg-error-1.3, libgcrypt-1.2.2, and
> cryptsetup-0.1
> The only configuration I've given to these packages is --prefix.
>
> >I've installed the requisite packages, but when I attempt to `cryptsetup
> >> create name /dev/device` I get the error "Command failed: Invalid
> >argument".
> >
> >That is not a password error. I don't know what causes the error,
> >but maybe your cryptsetup is a bit old? Or you do not have the
> >/dev/mapper directory? Or you are attemting this not as root?
> 
> 
> 
> 
> /dev/mapper exists, as does console inside of it.
> I am running as root.  I've also tested this on a spare partition, and
> receive the same result.

Ok, devinitvely an issue with the cryptsetup installation or
the kernel. Maybe you need to load some module(s) with the
kernel you are using? I don't use kernel modules, since
I like monolitic kernels, so I would not know....
 
> Any other ideas, per chance?  I appreciate your help.
> 

I am running with a 2.6.17.5 Kernel and cryptsetup-luks-1.0.1.
No issues. Here is what /dev/mapper looks like on my system.
Have a look at the ownership and permissions:

oot /dev/mapper>ll
total 32
drwxr-xr-x  2 root root    4096 Jul 26 16:50 ./
drwxr-xr-x 13 root root   28672 Jul 26 16:43 ../
brw-r-----  1 root root 253,  0 Jul 26 16:50 c1
crw-------  1 root root  10, 63 Jul 26 16:43 control
root /dev/mapper>

/proc/crypto lists

name         : aes
driver       : aes-generic
module       : kernel
priority     : 100
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32

and 

name         : aes
driver       : aes-i586
module       : kernel
priority     : 200
type         : cipher
blocksize    : 16
min keysize  : 16
max keysize  : 32

One more idea: If you give cryptsetup the '-v' option,
does it tell you more?

Arno


-- 
Arno Wagner, Dipl. Inform., CISSP --- CSG, ETH Zurich, wagner@xxxxxxxxxxxxxx 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
Windows is the "under-3" toy of the OS world. -- Matthew D. Fuller

---------------------------------------------------------------------
 - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux