usb mp3 player not recognized

English Multimedia
#1

so I plug in my mp3 player but not that ti don’t mount correctly, but it won’t mount at all.

 dmesg | tail
[32955.273829] usb-storage 2-1:1.0: USB Mass Storage device detected
[32955.274948] scsi16 : usb-storage 2-1:1.0
[32955.275098] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.275154] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.275174] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.275190] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.275206] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.275221] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use
[32955.277425] usb 2-1: usbfs: process 4306 (ThreadWeaver::T) did not claim interface 0 before use
[32955.277534] usb 2-1: usbfs: process 4303 (ThreadWeaver::T) did not claim interface 0 before use

I suppose it’d be in the /dev/sdb or /sdc but to my suprise it wasn’t anywhere no vfat, fat-xx filesystem anywhere
I tried mount -t vfat and I also’ve dosfstools, mtools instaled

#2

… be brief & clear, just post code where suitable and don’t skip steps so every noob understands

When you live up to this, you wouldn’t have said “I tried to mount …”, but you would have posted that action: the prompt, the command, the output and the next prompt between CODE tags in your post. Now we have only a vague description on which my only reaction can be:
I do not understand that action. How can you try to mount when you say you do not even have the most important parameter: the device file.

#3

I’ve created entry in fstab for that like that

    LABEL=GoGearVIBE     /run/media/robert/MP3                    vfat   user        0 2

the label is that dolphin gave me so I try to mount it. and the dmesg| tail I posted was after I pluged the device in the usb port

#4

DON’T!
Your system will not boot if the mp3 player is not connected or it fails to mount otherwise.

At least add the “nofail” option.

But why would you want to mount an mp3 player on boot?

You say dolphin gave you the label, so can you mount it in dolphin or not?
Of not, why do you think you can mount it in fstab then?

Try on the command line first:

sudo mount LABEL=GoGearVIBE /mnt

(/run/media/robert/MP3 probably won’t exist, so you cannot mount it there with “mount”)
This way you will see at least whether it works or not, and not break your boot immediately.

#5

no I can’t mount it it just appeared in dolphin put says that directory … don’t exist, recently I “mounted” it some way thru devices on the control panel but the full path dolphin is showin is pretty strange

 camera:/Philips%2520GoGear%2520Vibe%252F02@usb:002,004/store_00010001/Music/selico/24.1

and I can’t write to it nor execute

#6

Apparently dolphin tries to open it as camera. Can you access it in this way?

Maybe that mp3 player doesn’t support mass storage mode and can only be accessed via MTP/PTP? (in that case it cannot be “mounted”)
Maybe there’s a setting in the mp3 player for that somewhere? (on my mobile phone f.e. I get asked which USB-mode to use: Nokia’s PC-Suite, Print and Media (in this case it is seen as “camera:/”, or mass storage, there’s also an option in the settings to set one as default)

Do you see it in Systemsettings (Configure Desktop)->Hardware->Digital Cameras?

Do you have “kio_mtp” installed? Which version?

Have you tried to mount it on the command line?
I guess it won’t work anyway as it apparently doesn’t even show up as /dev/sdX.

#7

I can acces it right now but can’t write even as root (dolphin as root) and I don’t even know where it’s mounted

#8

I can acces it right now but can’t write even as root (dolphin as root) and I don’t even know where it’s mounted

 lsusb
Bus 001 Device 008: ID 0471:20e5 Philips (or NXP) 
Bus 001 Device 004: ID 17ef:1004 Lenovo Integrated Webcam
Bus 002 Device 006: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
#9

You say “I don’t even know where it’s mounted”, but you fail to say what you did to find that out. In any case

mount

will show you all mounted file systems, thus it must be in that list (at the end if it was mounted a short time ago).

#10

What did you do to access it?
Use “mount” to find out where it is mounted (and with what filesystem).
But most likely it is not mounted like I said before.
Especially if you cannot even write to it as root. What error message do you get when you try to write, btw?

 lsusb
Bus 001 Device 008: ID 0471:20e5 Philips (or NXP) 
Bus 001 Device 004: ID 17ef:1004 Lenovo Integrated Webcam
Bus 002 Device 006: ID 1949:0004 Lab126, Inc. Amazon Kindle 3/4/Paperwhite
Bus 004 Device 002: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[/QUOTE]
And which one is it?

#11

It’s the phillips device

 lsusb -D /dev/bus/usb/001/008
Device: ID 0471:20e5 Philips (or NXP) 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0471 Philips (or NXP)
  idProduct          0x20e5 
  bcdDevice            0.01
  iManufacturer           1 Philips
  iProduct                2 GoGear ViBE  
  iSerial                 5 1A040000F1B81D0A0002DCF0DDB61D0A
  bNumConfigurations      2
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          3 USB/MSC LCD Player
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4 USB/MSC LCD Player
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           39
    bNumInterfaces          1
    bConfigurationValue     2
    iConfiguration          3 USB/MSC LCD Player
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4 USB/MSC LCD Player
      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
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval              16
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      2
Device Status:     0x0000
  (Bus Powered)

and here’s the mount


mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=1976888k,nr_inodes=494222,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/sda9 on / type ext4 (rw,relatime,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /var/run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmpfs on /var/lock type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda6 on /run/media/root/suse1-root type btrfs (rw,relatime,space_cache)
/dev/sda6 on /var/run/media/root/suse1-root type btrfs (rw,relatime,space_cache)
/dev/sda1 on /run/media/robert/data type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered,user)
/dev/sda1 on /var/run/media/robert/data type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered)
/dev/sda10 on /home type ext4 (rw,relatime,data=ordered)
vmware-vmblock on /var/run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
vmware-vmblock on /run/vmblock-fuse type fuse.vmware-vmblock (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
gvfsd-fuse on /var/run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/sda8 on /run/media/root/suse1-home type btrfs (rw,relatime,space_cache)
/dev/sda8 on /var/run/media/root/suse1-home type btrfs (rw,relatime,space_cache)
#12

We asked for

mount
#13

according to output it apparently is mass storage and I had been
writing to it in recent pass just fine, but maybe after some update it behaves like that

#14

I already post mount but in this post above your’s and I’ve also tried mount | grep “fat” or “ntfs” “sdb” but nothing like that

#15

When was “in recent pass”? How exactly did you access it then?

What updates did you install since then?

You’re right that the lsusb output shows it as mass storage. And your dmesg output from the first post shows that it is indeed recognized as mass storage, but apparently it cannot be accessed.

Have you tried to boot an earlier kernel?

Well, if the output of “mount” doesn’t show it, it is not mounted of course. And according to that dmesg output, not even a device file is created.

I’m not sure what that “ThreadWeaver” stuff does in there, “ThreadWeaver” is a KDE library.
Please login to “IceWM” (should be installed by default), connect the device and post again the output of “demsg | tail”.

#16

I’ve not found how to login to IceWM, but I’ve read this post http://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs but I don’t know what to put udev/rules.d/custom.rules. I.e how to make every usb storage to mount automatically, since I don’t want to choose from “actions for the device…”.

#17

This:

(Sorry, there was a typo, it should have been “dmesg | tail” of course)

As long as your device doesn’t get a device file, autofs won’t help you anyway. Autofs is just there to mount it automatically, but in your case there is apparently nothing to mount.

No idea whether a custom udev rule would help or how that should look like, I don’t know your usb player.
But you did say it worked before, so that shouldn’t be necessary.

And how about answering the other questions?

Or does it work now?
Then why don’t you say so?

I cannot read your mind.

#18 

dmesg | tail
[78749.421031] usb 2-1: usbfs: process 1872 (ThreadWeaver::T) did not claim interface 0 before use
[78749.421043] usb 2-1: usbfs: process 1872 (ThreadWeaver::T) did not claim interface 0 before use
[78749.421054] usb 2-1: usbfs: process 1872 (ThreadWeaver::T) did not claim interface 0 before use
[78749.524080] usb 2-1: reset high-speed USB device number 10 using ehci-pci
[78749.638737] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use
[78749.639453] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use
[78749.639470] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use
[78749.639481] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use
[78749.639492] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use
[78749.639503] usb 2-1: usbfs: process 1877 (ThreadWeaver::T) did not claim interface 0 before use

but isn’t there a way to automatically mount every usb device

#19

No. If you cannot mount it manually, you cannot mount it automatically either.

And of course you cannot mount every usb device. How would you “mount” a mouse or keyboard f.e.?

You still did not tell how you were able to access the device before, and whether you have kio_mtp installed. (and some other questions)

Googling for your error message gives a lot of results related to MTP.
Have a look here f.e.:
http://askubuntu.com/questions/457219/14-04-usb-mp3-player-not-recognized-as-storage-medium-anymore

Do you have any application running that might access the usb device, like Amarok (via the MTP plugin)?
Or maybe try to access it with Amarok. Does that work?

#20

As wolfi323 csays. Maybe should should try to read something about what the words mean: http://en.opensuse.org/SDB%3ABasics_of_partitions,_filesystems,_mount_points