From: ganja <ganja@0x63.nu>
To: dm-devel@redhat.com
Subject: Problem with cryptsetup/device-mapper
Date: Thu, 06 Jul 2006 09:52:04 +0200 [thread overview]
Message-ID: <44ACC124.2040609@0x63.nu> (raw)
Hello all, I am having some problems setting up a crypted device, and to
me it seems to have with device mapper to do. I have loaded what modules
I know is necessary as you can see below and I have tried different
devices and pure files (ex /tmp/myimage which I created with dd
if=/dev/urandom).
I am running Debian Unstable and I have tested it with 1-2 week old
packages and fully upgraded. I also talked to google for an hour, be he
wasnt very nice to me, found no valuable information at all.
Any help appreciated.
(please CC me, I am not subscribed)
thor:/tmp# cryptsetup -y -c aes -s 256 create hda1aes /dev/hda1
Enter passphrase:
Verify passphrase:
Command failed: device-mapper: reload ioctl failed: Invalid argument
thor:/tmp# lsmod
Module Size Used by
dm_crypt 10056 0
aes 28736 0
hptmv 198660 14
nvidia 4543700 12
sr_mod 13476 0
dm_mod 50200 3 dm_crypt
raid5 32448 4
xor 16072 1 raid5
raid1 21824 0
raid0 8064 0
md_mod 70612 7 raid5,raid1,raid0
loop 13576 0
sata_promise 9348 12
ata_piix 9668 12
libata 60300 2 sata_promise,ata_piix
uhci_hcd 20552 0
e1000 109624 0
sd_mod 16832 41
thor:/tmp# uname -a
Linux thor 2.6.17 #1 SMP PREEMPT Mon Jun 19 15:51:08 CEST 2006 i686
GNU/Linux
thor:/tmp# dmesg|tail -n3
device-mapper: crypt: Device lookup failed
device-mapper: error adding target to table
device-mapper: device doesn't appear to be in the dev hash table.
thor:/tmp# tail /var/log/messages -n2
Jul 6 09:45:50 localhost kernel: device-mapper: error adding target to
table
Jul 6 09:45:50 localhost kernel: device-mapper: device doesn't appear
to be in the dev hash table.
--
Magnus Månsson
reply other threads:[~2006-07-06 7:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44ACC124.2040609@0x63.nu \
--to=ganja@0x63.nu \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.