I ran into the same hitch, and concluded that, well, maybe because it misses something, possibly the proper info to open the encrypted partition; luks (especially when combined with lvm like in my case) is more than just a password...
Below the script I use for one particular encrypted external drive for connection; note the names 'lukssdc1'; '4Tvg' were all generated when that luks-partition/volume group was created and registered with the machine it runs on, so don't copy. Best to read the Slackware/README_CRYPT.txt and Slackware/README_LVM.txt and follow the steps that suit and assemble these in a script that works.
After my drive is inserted and the icon shows I click the xfce-dialog for the password away and instead run this script from a terminal with 'start' as option (and the same with 'stop' before pulling the drive out..), then giving the password works....
Code:
# !/bin/bash
# steps to mount external DATA_ANALYSIS_4 drive
#
# /usr/local/sbin/DATA_ANALYSIS_4.sh
#
# start/stop
case "$1" in
'start')
#cryptsetup luksOpen /dev/sdc1 lukssdc1
cryptsetup luksOpen UUID="3b76d01f-7aae-4385-8260-0b1445aefddf" lukssdc1
lvchange -a y 4Tvg
mount /dev/4Tvg/working_4Tb
;;
'stop')
umount /home/working/DATA_ANALYSIS_4
lvchange -a n 4Tvg
cryptsetup close lukssdc1
;;
*)
echo "Usage: $0 {start|stop}"
;;
esac
the script is combined with this line in /etc/fstab, so that the drive always loads at the same mount point (handy for making backups etc):
Code:
/dev/4Tvg/working_4Tb /home/working/DATA_ANALYSIS_4 ext4 defaults 1 2
hth
