Leap 42.2, Cinnamon desktop. Cinnamon version 3.40.
I got 2 new USB sticks from Microcenter, and anytime I insert one or the other, do they do not automount. It will show in Nemo, but clicking on it kicks out ‘Unable to mount volume. Not authorized to perform this operation’.
I have other USB sticks and external drives that mount with no issues.
If I boot up a Win10 VM in Virtualbox, I can attach it to the VM, and move files to it.
I logged in under Plasma, and Dolphin wants root credentials to mount it. If I provide the credentials, it mounts fine.
Sticks are formatted FAT32.
Kinda stumped…any suggestions? I would think that since other USB devices mount fine, these should as well.
This reads like Microcenter devices are being detected as system devices (rather than removable devices). If so then polkit privileges may well be treating them as internal disks. The org.freedesktop.udisks2.filesystem-mount-system privileges could be changed to allow user mounting if this is the case, but it should be possible to alter this behaviour with a suitable udev rule so that the devices are handled as normal removable devices.
First ,check what is reported for the Microcenter devices by the following command
lsusb -v
Report back with the output block pertaining to the device concerned. If you like, do the same for a removable device that does behave as expected as well.
On Sat 20 May 2017 09:36:02 PM CDT, deano ferrari wrote:
mhibist;2823658 Wrote:
> Leap 42.2, Cinnamon desktop. Cinnamon version 3.40.
>
> I got 2 new USB sticks from Microcenter, and anytime I insert one or
> the other, do they do not automount. It will show in Nemo, but
> clicking on it kicks out ‘Unable to mount volume. Not authorized to
> perform this operation’.
>
> I have other USB sticks and external drives that mount with no
> issues.
This reads like Microcenter devices are being detected as system devices
(rather than removable devices). If so then polkit privileges may well
be treating them as internal disks. The
org.freedesktop.udisks2.filesystem-mount-system privileges could be
changed to allow user mounting if this is the case, but it should be
possible to alter this behaviour with a suitable udev rule so that the
devices are handled as normal removable devices.
First ,check what is reported for the Microcenter devices by the
following command
Code:
lsusb -v
Report back with the output block pertaining to the device concerned. If
you like, do the same for a removable device that does behave as
expected as well.
Hi
More likely formatted as exfat, so need exfat-tools and fuse-exfat from
the filesystems repo…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.62-18.6-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Here you go…the output was too long as it wold not allow me to post the whole list. However, the Kingston device is the only USB mass storage listed, so I’m going with that.
Thank you
Bus 001 Device 027: ID 13fe:5500 Kingston Technology Company Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x13fe Kingston Technology Company Inc.
idProduct 0x5500
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3 070A74B5EACCB856
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 300mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000006
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 2
Lowest fully-functional device speed is High Speed (480Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0000
(Bus Powered)
The next step us to create a suitable udev rule using suitable attributes to uniquely identify and handle this device. These can be got using something like…
udevadm info /dev/sdb1
Change the block device node name to suit your device of course. If not sure, run
lsblk
Then create a udev rule eg /etc/udev/rules.d/99-removable.rules