Cannot open Luks encrypted external HDD [Solved]

Questions about applications and software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
KajMagnus

Cannot open Luks encrypted external HDD [Solved]

Post by KajMagnus »

Hi dear Linux Mint people,

I'm trying to mount a Luks encrypted external 500GB HDD, on Linux Mint 17.1. I can mount this disk with Mint 17 (Cinnamon) and some version of Ubuntu: I just plug in the disk, enter the password and then the contents of the disk appear in the file manager.

However, with Linux Mint 17.1 64 bit (and kernel 3.19), Cinnamon, what happens when I plug in the drive is that 1) I input the password in the password dialog that appears 2) the contents of the disk does *not* appear in the file managre's drive device list, and 3) if I click the "500 GB Encrypted" disk, Mint says "Unable to mount 500 GB Encrypted: An operation is already pending."

Why am I unable to mount the encrypted disk and access its contents? (And what operation is pending?)

Here's an old thread (year 2012) that might describe the same problem (no solution suggested):
http://forums.linuxmint.com/viewtopic.p ... g+#p587998


Thanks for any help. Lots of details follow:


1) Mint is installed on a SSD, on two partitions (Windows 8.1 dual boots from some other partitions), one partition for / and one for /home. They're both encrypted already, with Luks. So when booting, I specify 2 password (one for each partition), before Mint starts.


2)

Code: Select all

$ sudo lsblk -f  # the external 500 GB HDD is 'sdb' below
NAME                                               FSTYPE      LABEL       MOUNTPOINT
sda                                                                        
├─sda1                                             ntfs        WINRE_DRV   
├─sda2                                             vfat        SYSTEM_DRV  /boot/efi
├─sda3                                             vfat        LRS_ESP     
├─sda4                                                                     
├─sda5                                             ntfs        Windows8_OS 
├─sda6                                             ntfs        LENOVO      
├─sda7                                             ntfs        PBR_DRV     
├─sda8                                             ext4                    /boot
├─sda9                                             crypto_LUKS             
│ └─sda9_crypt (dm-0)                              ext4                    /
└─sda10                                            crypto_LUKS             
  └─sda10_crypt (dm-1)                             ext4                    /home
sdb                                                crypto_LUKS   <---- the 500 GB HDD
└─luks-06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b (dm-3)                         
loop0                                              ext4                    
└─docker-252:0-4206407-pool (dm-2)                 ext4                    
loop1                                                                      
└─docker-252:0-4206407-pool (dm-2)                 ext4       



3)

Code: Select all

$ ll /dev/mapper/    
total 0        
crw------- 1 root root  10, 236 Mar  9 22:06 control  
brw------- 1 root root 252,   2 Mar  9 22:07 docker-252:0-4206407-pool     
lrwxrwxrwx 1 root root        7 Mar  9 22:06 sda10_crypt -> ../dm-1      
lrwxrwxrwx 1 root root        7 Mar  9 22:06 sda9_crypt -> ../dm-0 


(Why won't the external disk appear in /dev/mapper? The encrypted partitions sda9_crypt and sda10_crypt do appear here.)


4)

Code: Select all

$ sudo cryptsetup status luks-06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b
/dev/mapper/luks-06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b is active.    <-- but not "in use"
  type:    LUKS1
  cipher:  aes-cbc-essiv:sha256
  keysize: 256 bits
  device:  /dev/sdb
  offset:  4096 sectors
  size:    976769071 sectors
  mode:    read/write

5)
And as mentioned, two partitions use Luks already:

Code: Select all

$ sudo cryptsetup status sda9_crypt  # sda10_crypt is similar
/dev/mapper/sda9_crypt is active and is in use.    <--- that one is "in use"
  type:    LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  device:  /dev/sda9
  offset:  4096 sectors
  size:    178706432 sectors
  mode:    read/write
  flags:   discards
(Hmm, Mint says "... and is in use" about sda9 & 10 _crypt, but not about the external HDD, why not?)


6)

Code: Select all

$ sudo blkid
/dev/loop0: UUID="6f8c5fb9-2482-41ac-a8b3-4e9fee9fd6f9" TYPE="ext4" 
/dev/sda1: LABEL="WINRE_DRV" UUID="FA3A12A03A1259C9" TYPE="ntfs" 
/dev/sda2: LABEL="SYSTEM_DRV" UUID="BE14-5DCB" TYPE="vfat" 
/dev/sda3: LABEL="LRS_ESP" UUID="3616-902C" TYPE="vfat" 
/dev/sda5: LABEL="Windows8_OS" UUID="A43A194D3A191E3C" TYPE="ntfs" 
/dev/sda6: LABEL="LENOVO" UUID="14F68D56F68D394E" TYPE="ntfs" 
/dev/sda7: LABEL="PBR_DRV" UUID="C2FE1B13FE1AFEFB" TYPE="ntfs" 
/dev/sda8: UUID="096dcaec-3729-4cd6-af40-94934b91dccc" TYPE="ext4" 
/dev/sda9: UUID="bc97faf5-2b35-4719-86d3-2019f8c72789" TYPE="crypto_LUKS" 
/dev/sda10: UUID="fd2ed302-938b-44a1-9167-92f25ef60259" TYPE="crypto_LUKS" 
/dev/mapper/sda9_crypt: UUID="52ebf4d2-5d24-4787-bcf1-1166cb9bd5b4" TYPE="ext4" 
/dev/mapper/sda10_crypt: UUID="267b52b8-db40-4ec0-8089-f24978dff063" TYPE="ext4" 
/dev/mapper/docker-252:0-4206407-pool: UUID="6f8c5fb9-2482-41ac-a8b3-4e9fee9fd6f9" TYPE="ext4" 
/dev/sdb: UUID="06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b" TYPE="crypto_LUKS"    <--- the external HDD

7)

Code: Select all

$ sudo fdisk -l
Disk /dev/sda: 512.1 GB, 512110190592 bytes     (<--- the OS is installed on this disk)
255 heads, 63 sectors/track, 62260 cylinders, total 1000215216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa4957ab6

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1  1000215215   500107607+  ee  GPT

Disk /dev/mapper/sda9_crypt: 91.5 GB, 91497693184 bytes
255 heads, 63 sectors/track, 11123 cylinders, total 178706432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/sda9_crypt doesn't contain a valid partition table

...

Disk /dev/sdb: 500.1 GB, 500107861504 bytes   <--- the external HDD
255 heads, 63 sectors/track, 60801 cylinders, total 976773167 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x08040000

Disk /dev/sdb doesn't contain a valid partition table
... But nothing at all about 'luks-06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b', which is a child of sdb according to 'lsblk'.


8)
Here are the 'dmesg' log lines that appeared when I plugged in the external HDD:

Code: Select all

[ 8687.582627] usb 1-1: new high-speed USB device number 7 using xhci_hcd
[ 8687.810919] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd
[ 8687.830155] usb 2-1: New USB device found, idVendor=0bc2, idProduct=ab10
[ 8687.830158] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8687.830160] usb 2-1: Product: BUP Slim SL
[ 8687.830162] usb 2-1: Manufacturer: Seagate 
[ 8687.830163] usb 2-1: SerialNumber: NA4T76WB
[ 8687.844511] scsi host7: uas
[ 8687.845634] scsi 7:0:0:0: Direct-Access     Seagate  BUP Slim SL      0938 PQ: 0 ANSI: 6
[ 8687.847083] sd 7:0:0:0: Attached scsi generic sg1 type 0
[ 8687.901211] sd 7:0:0:0: [sdb] 976773167 512-byte logical blocks: (500 GB/465 GiB)
[ 8687.902218] sd 7:0:0:0: [sdb] Write Protect is off
[ 8687.902220] sd 7:0:0:0: [sdb] Mode Sense: 2b 00 10 08
[ 8687.902966] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 8689.316074]  sdb: unknown partition table
[ 8689.336413] sd 7:0:0:0: [sdb] Attached SCSI disk
[ 8703.815765] sd 7:0:0:0: [sdb] uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
[ 8703.815771] sd 7:0:0:0: [sdb] CDB: 
[ 8703.815773] ATA command pass through(12)/Blank: a1 08 2e 00 01 00 00 00 00 ec 00 00
[ 8726.882385] sd 7:0:0:0: [sdb] uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[ 8726.882389] sd 7:0:0:0: [sdb] CDB: 
[ 8726.882391] Read(10): 28 00 00 00 10 00 00 00 08 00
[ 8726.882434] scsi host7: uas_eh_bus_reset_handler start
[ 8726.994922] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd
[ 8727.011476] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880446780848
[ 8727.011481] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804467808d8
[ 8727.011483] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880446780800
[ 8727.011484] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880446780890
[ 8727.012686] scsi host7: uas_eh_bus_reset_handler success

9)

Code: Select all

$ sudo mount /dev/sdb /mnt/luks
mount: unknown filesystem type 'crypto_LUKS'

sudo mount -U 06c8a6a1-24e8-4bb6-821c-3809d6d0aa9b /mnt/luks
mount: unknown filesystem type 'crypto_LUKS'

Thanks for any help and best regards,
KajMagnus
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
KajMagnus

Re: Cannot open Luks encrypted external HDD

Post by KajMagnus »

gmilo2 wrote:I see the external drive has a different cipher and key size. Maybe the automatic unlock/mount capabilities in Mint 17.1 assume a certain size and/or cipher? I'd look into seeing how to unlock it and mount from the command line. I believe the options are -c and -s but I'm not up to speed on writing the command line to unlock it. Then you'ld have to mount it.
Thanks, that solved my problem; this worked:

Code: Select all

07:15:11 6 ~$ sudo cryptsetup --cipher cbc-essiv:sha256 luksOpen /dev/sdc luks2
07:16:05 8 ~$ sudo mount /dev/mapper/luks2 /mnt/luks/
Locked

Return to “Software & Applications”