[pkg-cryptsetup-devel] Bug#586120: Bug#586120: device-mapper: reload ioctl failed: Invalid argument

[Clayton]

On Sat, 26 Jun 2010 12:32:02 +0200
Jonas Meurer <jonas at freesources.org> wrote:

> On 16/06/2010 clayton wrote:
> > # cryptsetup create backcrypt /dev/sda2
> > Enter passphrase:
> > device-mapper: reload ioctl failed: Invalid argument
> Can you post dmsetup table when this fails?

Hi Jonas,

Sad to say, I think the original symptom I reported may have been due to
finger problems associated with the recent shuffling of device names.
The encrypted partition is on USB drive that used to be assigned sda
when it was plugged in. Now the internal hard drive is assigned sda,
and the USB drive gets assigned sdb. Not sure how I missed that....

So now: cryptsetup create backcrypt /dev/sdb2
works.

BUT!!: when I try to mount the partition, this happens:

# mount /media/backcrypt/
mount: wrong fs type, bad option, bad superblock on /dev/dm-0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

(Nothing at all is showing up in /var/log/messages associated with this
event....)

/etc/fstab contains:
/dev/mapper/backcrypt  /media/backcrypt  ext3  rw,,user  0 0

# ll /dev/mapper/backcrypt
lrwxrwxrwx 1 root root 7 Jun 27 11:50 /dev/mapper/backcrypt -> ../dm-0

Again, the fstab entry has not changed for years, and this is a monthly
routine that has worked consistently for years. There is also another,
unencrypted, ext3 partition on this USB drive that continues to mount
just fine.

Clayton