This is the log from gnome-mount, trying to mount an encrypted SD card, and failing:
gnome-mount -v -b -t -d /dev/sdb1 gnome-mount 0.8 ** (gnome-mount:3706): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_a3b5b86b_2430_4d64_9719_252283c1a1d1' Enter password to unlock encrypted data for /dev/sdb1: ** (gnome-mount:3706): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_a3b5b86b_2430_4d64_9719_252283c1a1d1 for crypto Setup clear-text device for /dev/sdb1. ** (gnome-mount:3706): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_a3b5b86b_2430_4d64_9719_252283c1a1d1.. ** (gnome-mount:3706): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_part_1_size_0 ** (gnome-mount:3706): DEBUG: /org/freedesktop/Hal/devices/volume_part_1_size_0 is backed by /org/freedesktop/Hal/devices/volume_uuid_a3b5b86b_2430_4d64_9719_252283c1a1d1 - will mount Clear text device is /dev/dm-1. Mounting. ** Message: /org/freedesktop/Hal/devices/volume_part_1_size_0 does not have a mountable filesystem I also had "udevadm monitor" running, but there's no difference in the output between a successful mount and a failure. Also, I'm not sure if this is useful, but there's an old Fedora bug describing the same thing, in that case it seems it was an outdated udev rule which led to this problem. See https://bugzilla.redhat.com/show_bug.cgi?id=209590 Perhaps it's time to ping the udev maintainer about this problem? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part
