On 05/18/2016 07:46 AM, Dick Steffens wrote:
> On 05/17/2016 10:06 PM, Dick Steffens wrote:
>> On 05/17/2016 06:56 PM, David wrote:
>> While an obnoxious step most of the time, this is hook related and the
>> kernel may not respond well (in rare instances) when packages are added.
>>
>> You'll probably have to reboot to clear the lsusb issue if you can't
>> find which process is keeping it bound up.
>> I'll give that a try in the morning.
>
> I powered down and restarted. Then I installed usbmount. Then I
> restarted. Then I plugged in my card reader and got this message:
>
> ----------------------------------------------------------------------------------------
> Unable to mount EOS_DIGITAL
>
> Device /dev/sdd1 is already mounted at `/media/usb0'.
> ----------------------------------------------------------------------------------------
>
> lsusb works now and shows this:
>
> ----------------------------------------------------------------------------------------
> rsteff@Enu-1:~$ lsusb
> Bus 002 Device 002: ID 8087:8000 Intel Corp.
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 001 Device 002: ID 8087:8008 Intel Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 003 Device 006: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
> Bus 003 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
> Bus 003 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
> Bus 003 Device 004: ID 05f3:00ff PI Engineering, Inc. VEC Footpedal
> Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> ----------------------------------------------------------------------------------------
>
> Sure enough, the card reader is mounted at /media/usb0. So some
> progress, but why that error message?
>
> In Nautilus there's a little triangle to the right of the device name
> that one clicks on to umount a device. When I click on it I'm required
> to provide a password. The password box has this wording:
>
> ----------------------------------------------------------------------------------------
> Authenticate
>
> Authentication is required to unmount Generic USB CF Reader(/dev/sdd1)
> mounted by another user

This indicates that something else has mounted your device. The below is 
just asking for an administrator password.

> A application is attempting to perform an action that requires privileges.
> Authentication is required to perform this action.
>
> Password: [                    ]
>
> Details
> Action: org.freedesktop.udisks2.filesystem-unmount-others
> Vendor: The udisks Project
> ----------------------------------------------------------------------------------------
>
> Upon entering the password I get this message:
>
> ----------------------------------------------------------------------------------------
> Volume is busy.
>
> One of more applications are keeping the volume busy.
> rsteff@Enu-1: /media/usb0/DCIM
> [Cancel] [Eject Anyway]
> ----------------------------------------------------------------------------------------

You can try to find out what is holding the device open with lsof, and 
that might hint at what was used to mount it, and then troubleshoot 
things from there. Eject Anyway could lead to a dirty umount or a broken 
shell / utility when it can't see the device any longer.

> I hit [Cancel], switched to a different directory in Nautilus and tried
> again. Same error message as before. This time I hit [Eject Anyway].
> EOS_DIGITAL disappeared from the left hand pane of the Nautilus window.
> I jostled the USB plug when reaching to unplug it. Very briefly,
> EOS_DIGITAL appeared in the left hand pane of the Nautilus window, went
> away, and the "Unable to mount EOS_DIGITAL error message appeared:
>
> ----------------------------------------------------------------------------------------
> Unable to mount EOS_DIGITAL
>
> Device /dev/sdd1 is already mounted at `/media/usb0'.
> ----------------------------------------------------------------------------------------
>
> So this is a work-around, but it seems screwy.
>

Yeah, screwy sums it up nicely. Keep plugging at it. You may also want 
to continue to do web searches on resolution with other means, and 
possibly confirm which group associations your user needs to be a member 
of for this to all work properly.

dafr

_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to