Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to mount ISO/loop devices.

See original GitHub issue

First of all, I’m not sure if this is a bug or if I’m not understanding user-space ISO mounting correctly.

I can use udisks2 to successfully mount an ISO via:

$ udisksctl loop-setup -r -f image.iso
$ udisksctl mount -b /dev/loop1p1

Udiskie fails when specifying the ISO with:

DEBUG [2016-02-06 15:06:36,772] udiskie.config: IgnoreDevice(match={'is_block': False}, value=True) created
DEBUG [2016-02-06 15:06:36,773] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) created
DEBUG [2016-02-06 15:06:36,773] udiskie.config: IgnoreDevice(match={'is_ignored': True}, value=True) created
WARNING [2016-02-06 15:06:37,318] udiskie.udisks2: Device not found: /home/bean/Resources/Distros/ubuntu-15.10-server-amd64.iso
ERROR [2016-02-06 15:06:37,318] udiskie.mount: no device found owning "/home/bean/Resources/Distros/ubuntu-15.10-server-amd64.iso"

Udiskie fails when specifying the loop device, created by udisksctl, with:

DEBUG [2016-02-06 14:46:08,372] udiskie.config: IgnoreDevice(match={'is_block': False}, value=True) created
DEBUG [2016-02-06 14:46:08,372] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) created
DEBUG [2016-02-06 14:46:08,372] udiskie.config: IgnoreDevice(match={'is_ignored': True}, value=True) created
DEBUG [2016-02-06 14:46:08,582] udiskie.mount: found device owning "/dev/loop1p1": "/org/freedesktop/UDisks2/block_devices/loop1p1"
DEBUG [2016-02-06 14:46:08,639] udiskie.config: IgnoreDevice(match={'is_external': False}, value=True) used for /org/freedesktop/UDisks2/block_devices/loop1p1
WARNING [2016-02-06 14:46:08,639] udiskie.mount: not mounting /org/freedesktop/UDisks2/block_devices/loop1p1: unhandled device

I have not created any configuration files.

Issue Analytics

State:
Created 8 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

coldfixcommented, Jul 2, 2016

Added handling for loop devices. For convenience, the container will be managed same as the loop file by default:

udiskie-mount image.iso also mounts the loop device unless using the -R (--no-recursive) option
udiskie-umount image.iso also detaches the loop device unless using the -D (--no-detach) option

0reactions

coldfixcommented, Jul 1, 2016

Okay, I’ll likely complete this feature this weekend.

The tray menu should already do recursive unmounts/locks/detaches. Under which circumstances do you experience problems with this? Does it work using the udiskie-umount -f tool? Can you open a separate issue with the corresponding description.

Regarding recursive mounts/unlocks. I disagree that this should be done by default if you have automounting disabled: It might be that there are several partitions in one container and if the user disables auto-mounting, she should still have control which partitions to mount, which not to. I could, however, imagine a separate menu item Recursive unlock or similar, or alternatively allow to configure udiskie to do this.