Re: automatic mounting of an encrypted harddrive
On Fri, Nov 06, 2009 at 16:37:11 +0100, Tobias Schula wrote:
> Am Sonntag 25 Oktober 2009 10:28:34 schrieb Florian Kulzer:
[...]
> > That probably means that HAL does not set the crypto-related properties
> > for the device, which would explain why KDE does not know how to handle
> > it.
[...]
> root@siduxbox:~# lshal -u $(hal-find-by-property --key block.device --string '/dev/sdc1')
> udi = '/org/freedesktop/Hal/devices/volume_part1_size_640132383744'
> block.device = '/dev/sdc1' (string)
> block.is_volume = true (bool)
> block.major = 8 (0x8) (int)
> block.minor = 33 (0x21) (int)
> block.storage_device =
> '/org/freedesktop/Hal/devices/storage_serial_WD_6400AAK_External_57442D574D41535936373033363434_0_0' (string)
> info.capabilities = {'volume', 'block'} (string list)
> info.category = 'volume' (string)
An important property is missing here:
info.interfaces = {'org.freedesktop.Hal.Device.Volume.Crypto'} (string list)
[...]
> volume.fstype = '' (string)
> volume.fsusage = '' (string)
> volume.fsversion = '' (string)
These three lines should look like this:
volume.fstype = 'crypto_LUKS' (string)
volume.fsusage = 'crypto' (string)
volume.fsversion = '256' (string)
Udev should set these properties based on the results of running
/sbin/blkid on the device, triggered by 60-persistent-storage.rules. We
have to find out why this does not happen on your system.
Please run
udevadm test $(udevadm info --query=path -n /dev/sdc1)
, make the output available on http://debian.pastebin.com (or a similar
site of your choice) and post the link here.
--
Regards, |
Florian |
Reply to: