Hide Forgot
Description of problem: When I plug my USB memory stick, it is not mounted although lsusb can see it. $ lsusb -v Bus 002 Device 007: ID 14cd:121f Super Top Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x14cd Super Top idProduct 0x121f bcdDevice 3.00 iManufacturer 1 iProduct 3 iSerial 2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 250mA 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 Here are the entries in /var/log/messages when I plug the stick: kernel: [ 393.235958] usb 2-1.1: new full-speed USB device number 8 using ehci-pci kernel: [ 393.492173] usb 2-1.1: new high-speed USB device number 9 using ehci-pci kernel: [ 393.578909] usb 2-1.1: New USB device found, idVendor=14cd, idProduct=121f kernel: [ 393.578920] usb 2-1.1: New USB device strings: Mfr=1, Product=3, SerialNumber=2 kernel: [ 393.578925] usb 2-1.1: Product: Mass Storage Device kernel: [ 393.578929] usb 2-1.1: Manufacturer: Generic kernel: [ 393.578933] usb 2-1.1: SerialNumber: 121F20110712 kernel: [ 393.579579] usb-storage 2-1.1:1.0: USB Mass Storage device detected kernel: [ 393.580576] scsi8 : usb-storage 2-1.1:1.0 mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1" mtp-probe: bus: 2, device: 9 was not an MTP device kernel: [ 394.584436] scsi 8:0:0:0: Direct-Access Mass Storage Device 1.00 PQ: 0 ANSI: 0 CCS kernel: [ 394.585340] sd 8:0:0:0: Attached scsi generic sg4 type 0 kernel: [ 394.722225] sd 8:0:0:0: [sdd] 7744512 512-byte logical blocks: (3.96 GB/3.69 GiB) kernel: [ 394.722962] sd 8:0:0:0: [sdd] Write Protect is off kernel: [ 394.723642] sd 8:0:0:0: [sdd] No Caching mode page found kernel: [ 394.723649] sd 8:0:0:0: [sdd] Assuming drive cache: write through kernel: [ 394.727442] sd 8:0:0:0: [sdd] No Caching mode page found kernel: [ 394.727449] sd 8:0:0:0: [sdd] Assuming drive cache: write through kernel: [ 394.728600] sdd: sdd1 kernel: [ 394.731272] sd 8:0:0:0: [sdd] No Caching mode page found kernel: [ 394.731282] sd 8:0:0:0: [sdd] Assuming drive cache: write through kernel: [ 394.731288] sd 8:0:0:0: [sdd] Attached SCSI removable disk Version-Release number of selected component (if applicable): $uname -a Linux casalibus.lan 3.11.8-200.fc19.x86_64 #1 SMP Wed Nov 13 16:29:59 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Steps to Reproduce: 1. plug the USB memory stick 2. wait 3. nothing happens Actual results: the drive is not mounted Expected results: the drive should be automatically mounted
The kernel doesn't mount devices by default. That is up to userspace to do. If the kernel detected it as you've shown here, it should be mountable by something. Either via 'mount /dev/sdd1 /mnt' or via some userspace component that does it for you. Moving to distribution component for now. Which desktop environment are you using?
I am using KDE. My system is up to date (yum update). Normally, when I plug anything on a USB port, a window pops-up to propose me various actions like opening the drive with Dolphin. Here, nothing comes and I am not able to use the drive. I just tried the memory stick on a Windows 7 machine and it works nicely. How did you find the device name /dev/sdd1? I will try to mount it when I get back to home tonight. Thanks, Frédéric
Manual mounting does not work: $ mount /dev/sdd /mnt mount: no medium found on /dev/sdd $ mount /dev/sdd1 /mnt mount: special device /dev/sdd1 does not exist I am using KDE 4.11.3.
Can you please post the output of: $ udisksctl dump and $ solid-hardware list
Created attachment 826843 [details] udisksctl dump
Created attachment 826844 [details] solid-hardware list
Here's the culprit (note it's sde, not sdd): /org/freedesktop/UDisks2/drives/Mass_Storage_Device_121F20110712: org.freedesktop.UDisks2.Drive: CanPowerOff: true Configuration: {} ConnectionBus: usb Ejectable: true Id: Mass-Storage-Device-121F20110712 Media: MediaAvailable: false the drive reports no media available, and further more: /org/freedesktop/UDisks2/block_devices/sde: org.freedesktop.UDisks2.Block: Configuration: [] CryptoBackingDevice: '/' Device: /dev/sde DeviceNumber: 2112 Drive: '/org/freedesktop/UDisks2/drives/Mass_Storage_Device_121F20110712' HintAuto: true HintIconName: HintIgnore: false HintName: HintPartitionable: true HintSymbolicIconName: HintSystem: false Id: IdLabel: IdType: IdUUID: IdUsage: IdVersion: MDRaid: '/' MDRaidMember: '/' PreferredDevice: /dev/sde ReadOnly: false Size: 0 Symlinks: /dev/disk/by-id/usb-Mass_Storage_Device_121F20110712-0:0 /dev/disk/by-path/pci-0000:00:1d.0-usb-0:1.1:1.0-scsi-0:0:0:0 ... the block device itself reports size 0 Reassigning to udisks2 for info
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.