FS#30071 - [pmount] can't mount LUKS encrypted devices

Attached to Project: Arch Linux
Opened by Giancarlo Bianchi (hermes14) - Wednesday, 30 May 2012, 09:44 GMT
Last edited by Allan McRae (Allan) - Saturday, 02 June 2012, 11:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Trying to mount a dm-crypt/LUKS encrypted device via pmount no longer works, due to the changed path of cryptsetup (from /sbin to /usr/sbin).

Additional info:
* 0.9.23-3
* The output with an external hard drive (*ext4* fs on top of dm-crypt/LUKS):

Errore: file system «crypto_LUKS» non valido
NTFS signature is missing.
Failed to mount '/dev/sdc1': Argomento non valido
The device '/dev/sdc1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/sdc1': Argomento non valido
The device '/dev/sdc1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Part of the message is in italian, but should be clear anyway.

Steps to reproduce:
1) Have a dm-crypt/LUKS encrypted device, with either a passphrase or a key set.
2) pmount /dev/sdXn <label>

Solution:
* Change the default path for cryptsetup, adding --with-cryptsetup-prog=/usr/sbin/cryptsetup to the configure options. This done, it works flawlessly, as usual.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 02 June 2012, 11:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.9.23-4

Loading...