[Bug 87731] Re: Luks Volumes do not mount
*** This bug is a duplicate of bug 88213 *** https://bugs.launchpad.net/bugs/88213 [Expired for gnome-mount (Ubuntu) because there has been no activity for 60 days.] -- Luks Volumes do not mount https://bugs.launchpad.net/bugs/87731 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Have we confirmed that this is a dupe of 88213 or a new bug based on the information I provided above? Can I provide any other information that might be helpful? Thanks! -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Might be a dup of bug 88213. Please give me the output of those commands: lsmod | grep dm gnome-mount -vbd /dev/sdb ** Changed in: gnome-mount (Ubuntu) Sourcepackagename: pmount = gnome-mount -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Here you go: lsmod | grep dm dm_crypt 14856 1 dm_mod 59084 5 dm_crypt gnome-mount -vbd /dev/sdb: gnome-mount 0.5 libhal-storage.c 1401 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. ** (gnome-mount:14571): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_e1220991_cba5_4d2c_8dd2_e223f6a994ce' ** (gnome-mount:14571): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_e1220991_cba5_4d2c_8dd2_e223f6a994ce for crypto Setup clear-text device for /dev/sdb. ** (gnome-mount:14571): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_e1220991_cba5_4d2c_8dd2_e223f6a994ce.. ** (gnome-mount:14571): WARNING **: Timeout for waiting for cleartext device... Exiting. -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Martin, Attached are both log files, the first device to mount is a normal USB drive, the second is a dmcrypt/luks encrypted volume. Thank you! ** Attachment added: Gnome-Volume-Manager log http://librarian.launchpad.net/6590435/gvm.log -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
and here is the udev log. It looks like it ended abruptly at this point: ID_FS_UUID=f9f2cfdf-1059-4f05-96a4-408d01e06e1a ID_FS_ ** Attachment added: udev log http://librarian.launchpad.net/6590443/udev.log -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Oh and should I move this bug to Gnome-Volume-Manager? -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
Output of lshal ** Attachment added: lshal http://librarian.launchpad.net/6590482/lshal.txt -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
output of dmesg, though it is filled up with some weird keyboard error: keyboard.c: can't emulate rawmode for keycode 0 -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
The remaining items requested: id: uid=1000(darren) gid=1000(darren) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),110(netdev),111(lpadmin),113(powerdev),114(scanner),117(admin),1000(darren) id hal: id: hal: No such user Is this a problem on Fiesty? id haldaemon: uid=107(haldaemon) gid=112(haldaemon) groups=112(haldaemon),24(cdrom),25(floppy),46(plugdev),113(powerdev) uname -a Linux dpa-mini 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux And finally I am attaching the output from running hald in debug mode, the interesting stuff is at the bottom and it shows: 19:59:53.785 [I] osspec.c:226: SEQNUM=2898, ACTION=add, SUBSYSTEM=block, DEVPATH=/sys/block/dm-0, DEVNAME=/dev/mapper/temporary-cryptsetup-28358, IFINDEX=0 19:59:53.786 [I] blockdev.c:638: block_add: sysfs_path=/sys/block/dm-0 dev=/dev/mapper/temporary-cryptsetup-28358 is_part=0, parent=0x 19:59:53.786 [I] blockdev.c:681: Waiting 1000ms to wait for device mapper to be ready key slot 0 unlocked. 19:59:54.793 [I] blockdev.c:686: Looking in /sys/block/dm-0/slaves 19:59:54.794 [I] blockdev.c:698: /sys/block/dm-0/slaves/sdb - /sys/block/sdb 19:59:54.794 [I] blockdev.c:734: Done looking in /sys/block/dm-0/slaves 19:59:54.794 [I] blockdev.c:740: Ignoring hotplug event - no parent 19:59:54.794 [W] blockdev.c:1152: Not adding device object 19:59:54.794 [I] osspec.c:226: SEQNUM=2899, ACTION=change, SUBSYSTEM=block, DEVPATH=/sys/block/dm-0, DEVNAME=/dev/mapper/temporary-cryptsetup-28358, IFINDEX=0 19:59:54.794 [I] osspec.c:226: SEQNUM=2900, ACTION=remove, SUBSYSTEM=block, DEVPATH=/sys/block/dm-0, DEVNAME=/dev/mapper/temporary-cryptsetup-28358, IFINDEX=0 19:59:54.794 [I] blockdev.c:1244: block_rem: sysfs_path=/sys/block/dm-0 19:59:54.795 [W] blockdev.c:1248: Device is not in the HAL database 19:59:54.795 [I] osspec.c:226: SEQNUM=2901, ACTION=add, SUBSYSTEM=block, DEVPATH=/sys/block/dm-0, DEVNAME=/dev/mapper/luks_crypto_d3d0f00b-58ca-4e72-a16c-1ad2978f8c11, IFINDEX=0 19:59:54.795 [I] blockdev.c:638: block_add: sysfs_path=/sys/block/dm-0 dev=/dev/mapper/luks_crypto_d3d0f00b-58ca-4e72-a16c-1ad2978f8c11 is_part=0, parent=0x 19:59:54.796 [I] blockdev.c:681: Waiting 1000ms to wait for device mapper to be ready 19:59:55.801 [I] blockdev.c:686: Looking in /sys/block/dm-0/slaves 19:59:55.802 [I] blockdev.c:698: /sys/block/dm-0/slaves/sdb - /sys/block/sdb 19:59:55.802 [I] blockdev.c:734: Done looking in /sys/block/dm-0/slaves 19:59:55.802 [I] blockdev.c:740: Ignoring hotplug event - no parent 19:59:55.802 [W] blockdev.c:1152: Not adding device object 19:59:55.802 [I] osspec.c:226: SEQNUM=2902, ACTION=change, SUBSYSTEM=block, DEVPATH=/sys/block/dm-0, DEVNAME=/dev/mapper/luks_crypto_d3d0f00b-58ca-4e72-a16c-1ad2978f8c11, IFINDEX=0 19:59:55.804 [I] hald_dbus.c:2965: No more methods in queue The luks volume is unlocked but then it fails to mount it... ** Attachment added: Log from HAL http://librarian.launchpad.net/6590520/hal.log -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87731] Re: Luks Volumes do not mount
NB that Feisty does not use pmount any more. Please do the steps on https://wiki.ubuntu.com/DebuggingRemovableDevices and attach the logs, so that we can find out where the problem is. If you want to use pmount, then you need to specify the real device (e. g. /dev/sda2), not the device mapper device. ** Changed in: pmount (Ubuntu) Status: Unconfirmed = Needs Info -- Luks Volumes do not mount https://launchpad.net/bugs/87731 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
