Error mounting an encrypted volume [solved]

Question

On mounting an internal drive, which is encrypted (but isnt a system drive) I received the following error:
[root@kaminari /etc]# cryptsetup luksOpen /dev/sda2 data
Enter passphrase for /dev/sda2:
device-mapper: remove ioctl failed: Device or resource busy
But the device does get opened:
[root@kaminari /etc]# dmsetup ls
base-root (253, 3)
md2crypt (253, 0)
base-usr (253, 2)
base-var (253, 1)
data (253, 5)
base-home (253, 4)
[root@kaminari /etc]# dmsetup info data
Name: data
State: ACTIVE
Read Ahead: 256
Tables present: LIVE
Open count: 0
Event number: 0
Major, minor: 253, 5
Number of targets: 1
So I tried to mount it:
mount: /dev/sda2 already mounted or /mnt/data busy
Yet I cant find it. So thought I would reboot to reset everything as such. and this time it didnt error with "remove ioctl failed", but again I cant actually mount it.
[root@kaminari ~]# cryptsetup luksOpen /dev/sda2 data
Enter passphrase for /dev/sda2:
[root@kaminari ~]# mount -t ext3 /dev/sda2 /mnt/data
mount: /dev/sda2 already mounted or /mnt/data busy
[root@kaminari ~]# dmsetup ls
base-root (253, 3)
md2crypt (253, 0)
base-usr (253, 2)
base-var (253, 1)
data (253, 5)
base-home (253, 4)
Some info:
[root@kaminari ~]# cat /etc/mtab
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=506032,mode=755 0 0
/dev/mapper/base-root / ext3 rw,noatime,commit=0 0 0
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/mapper/base-home /home ext3 rw,noatime,commit=0 0 0
/dev/mapper/base-usr /usr ext3 rw,noatime,commit=0 0 0
/dev/mapper/base-var /var ext3 rw,noatime,commit=0 0 0
/dev/md1 /boot ext3 rw,noatime,commit=0 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
gvfs-fuse-daemon /home/rob/.gvfs fuse.gvfs-fuse-daemon rw,nosuid,nodev,user=noodle 0 0
[root@kaminari ~]# cat /etc/fstab
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/mapper/base-home /home ext3 defaults,noatime 0 1
/dev/mapper/base-root / ext3 defaults,noatime 0 1
/dev/mapper/base-usr /usr ext3 defaults,noatime 0 1
/dev/mapper/base-var /var ext3 defaults,noatime 0 1
/dev/md1 /boot ext3 defaults,noatime 0 1
[root@kaminari ~]# lvscan
ACTIVE '/dev/base/var' [6.84 GiB] inherit
ACTIVE '/dev/base/usr' [19.53 GiB] inherit
ACTIVE '/dev/base/root' [1.95 GiB] inherit
ACTIVE '/dev/base/home' [97.66 GiB] inherit
Knowing me, I am (as usual!) Being daft. Would someone point out where
Last edited by Fruity (2010-11-29 21:36:48)

Answer 1

After some messing it about, I think it may be something to do with naultilus file manager, or the gnome disk utility.
How can I stop this behavior, so the disk is left alone for me to mount and unmount as I wish through the command line.
[solved] Knew I was being dopey, was tying to mount /dev/sda2, rather than referencing the device mapper name, like /dev/mapper/foo
Last edited by Fruity (2010-11-29 21:38:21)