linux mint recognizes mp3 and charges but doesnt allow transfer of files

JesseMD · 06-06-2022, 06:37 PM

I plugged in a brand new SanDisk sport plus mp3 player and it quickly changes from the transferring screen to charging screen (on the mp3). The computer doesnt show it when I open files, but I can locate it under system settings - disks. I just want to add songs to the mp3 player that are currently on the computer but cant seem to find a way to do that. Ive tried different cables, restarting the mp3, etc. It only recognizes it as a device thats charging, not something with files that can be opened.

frankbell · 06-06-2022, 07:45 PM

What I found indicates that the problem may be related to the MTP file system, which is the default on this device (and, these days, many others). A web search for "SanDisk sport plus linux" will turn up many links. This article looks like a good place to start.

What version of Mint are you running? I ask because of this: https://community.linuxmint.com/tutorial/view/1185

JesseMD · 06-06-2022, 08:17 PM

I followed one of the links that came up with that search, https://forums.linuxmint.com/viewtopic.php?t=218122, and its seems to be the exact same problem. Only difference is that I have Linux Mint 20.3 Cinnamon 5.2.7
I tried following the steps but came up with different code. Maybe its different for different version?

Also its worth mentioning that I chose Linux because I like the privacy aspects, not for any ability/ desire to mess with the programming of my computer, so its highly likely that I'm doing something wrong instead of what's outlined in the above link.

I apologize in advance for my complete and total ignorance and am very grateful for the help.

frankbell · 06-06-2022, 08:28 PM

I don't have a device of that type to test with, but, if you post the exact steps you followed and the error messages you received, someone else might be able to help. Be sure to surround any terminal output with "code" tags, which become available when you click the "Go Advanced" button beneath the compose/edit post window.

JesseMD · 06-06-2022, 08:39 PM

Ok thank you. So far I've tried pasting:

Code:

dmesg | tail -n 20

and

Code:

lsusb

into the terminal as outlined in this article: https://forums.linuxmint.com/viewtopic.php?t=218122

and the code I get back is

Code:

user@linux-laptop:~$ dmesg | tail -n 20
[791287.289180] sd 2:0:0:0: [sdc] Write Protect is off
[791287.289184] sd 2:0:0:0: [sdc] Mode Sense: 00 c0 00 00
[791287.291323] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[791287.444697] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[791316.140220] usb 3-3: USB disconnect, device number 31
[791547.955621] usb 3-3: new high-speed USB device number 32 using xhci_hcd
[791548.129913] usb 3-3: New USB device found, idVendor=0781, idProduct=d001, bcdDevice= 1.00
[791548.129922] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[791548.129925] usb 3-3: Product: Clip Sport Plus 
[791548.129928] usb 3-3: Manufacturer: SanDisk 
[791548.129930] usb 3-3: SerialNumber: 1AE4418644A4E86C
[791548.131728] usb-storage 3-3:1.0: USB Mass Storage device detected
[791548.132412] scsi host2: usb-storage 3-3:1.0
[791549.145426] scsi 2:0:0:0: Direct-Access     SanDisk  Clip Sport Plus       PQ: 0 ANSI: 0 CCS
[791549.145850] sd 2:0:0:0: Attached scsi generic sg0 type 0
[791549.146275] sd 2:0:0:0: [sdc] 62333952 512-byte logical blocks: (31.9 GB/29.7 GiB)
[791549.146459] sd 2:0:0:0: [sdc] Write Protect is off
[791549.146462] sd 2:0:0:0: [sdc] Mode Sense: 00 c0 00 00
[791549.146618] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[791549.193377] sd 2:0:0:0: [sdc] Attached SCSI removable disk

and

Code:

user@linux-laptop:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 04f2:b6f9 Chicony Electronics Co., Ltd Chicony USB2.0 Camera
Bus 003 Device 004: ID 04f3:0c63 Elan Microelectronics Corp. ELAN:Fingerprint
Bus 003 Device 032: ID 0781:d001 SanDisk Corp. Clip Sport Plus 
Bus 003 Device 003: ID 8087:0029 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And after that I don't know what else to do except check home folder to see if its recognized the mp3 player yet, which it hasn't.

ondoho · 06-07-2022, 12:16 AM

The dmesg output suggests the storage is sdc, and no errors.
Show us

Code:

sudo fdisk -l
mount

JesseMD · 06-08-2022, 04:56 PM

Ok, again I apologize for my ignorance on the subject, but I don't know what sdc means (in reference to the storage). Show you what exactly? Try pasting that code into the terminal?

boughtonp · 06-08-2022, 05:57 PM

Quote:

Originally Posted by JesseMD

Ok, again I apologize for my ignorance on the subject, but I don't know what sdc means (in reference to the storage).

You can consider the sd prefix to indicates a "storage device" - i.e. a disk - and sdc is the third such device identified. (The first would be sda, the second sdb.)

(Technically the prefix means either "SCSI disk" or "SCSI mass-storage driver" or something, but that's irrelevant and confuses things.)

It's useful to remember these are not fixed labels, e.g. if you put the same mp3 player into a different machine, it could be sdb or sde or whatever.

Quote:

Show you what exactly? Try pasting that code into the terminal?

Yes, enter those commands into a terminal then copy the result and paste in a new reply (inside "[code]..[/code]", just as you did before).

Also, in general before entering a command - especially one involving either "su" or "sudo" - it's a good idea to have at least an idea what it might do, which you can get by looking at the relevant man page.

In this case, fdisk -l will list partitions for known devices, and mount without arguments will list all mounted filesystems, both useful bits of information for figuring out if/where your device is mounted, and thus where to find/put the songs.

enigma9o7 · 06-08-2022, 08:22 PM

Maybe it's like a smartphone, and doesn't enable MTP mode until you select it on the device after every single time you plug it in?

JesseMD · 06-09-2022, 05:47 PM

Ok thank you for explaining.

Here it is for the first one:

Code:

user@linux-laptop:~$ sudo fdisk -l
[sudo] password for user:         
Disk /dev/nvme0n1: 465,78 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 500GB                   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 16384 bytes / 131072 bytes
Disklabel type: gpt
Disk identifier: DFC67122-5175-46C8-BE7D-C1833EE606DB

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1050623   1048576   512M EFI System
/dev/nvme0n1p2 1050624 976771071 975720448 465,3G Linux filesystem


Disk /dev/sdc: 29,74 GiB, 31914983424 bytes, 62333952 sectors
Disk model: Clip Sport Plus 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x943da830

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sdc1       452608 62333951 61881344 29,5G  b W95 FAT32

And the second one:

Code:

user@linux-laptop:~$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=8020876k,nr_inodes=2005219,mode=755,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1616024k,mode=755,inode64)
/dev/nvme0n1p2 on / type ext4 (rw,relatime,errors=remount-ro,stripe=32)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755,inode64)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
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,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/misc type cgroup (rw,nosuid,nodev,noexec,relatime,misc)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=19147)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1616020k,mode=700,uid=1000,gid=1000,inode64)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/nvme0n1p2 on /run/timeshift/backup type ext4 (rw,relatime,errors=remount-ro,stripe=32)

Quote:

Originally Posted by enigma9o7

Maybe it's like a smartphone, and doesn't enable MTP mode until you select it on the device after every single time you plug it in?

There are mp3 players that work like that, however, this is not one of them. There aren't any USB mode options in any of the menus.

GPGAgent · 06-10-2022, 10:23 AM

USB Mode determines how your player communicates with your computer. Auto
Detect is selected by default. You can also choose to always connect in MTP (Media
Transfer Protocol) or MSC (Mass Storage Class) modes. Windows can use MTP or MSC
mode, but Mac OS will only work with MSC mode.

You need to set your Sandisk player to MSC mode

On the player
1 Go to Setting
2 Go to USB Mode
3 Select MSC
job done

Now it will connect as a drive and you will see all your folders

Code:

/dev/sdd        1.9G  951M  906M  52% /media/jonke/0123-4567

And the attached image in Thunar

boughtonp · 06-10-2022, 10:52 AM

Ok, so here's the relevant part of the fdisk output:

Quote:

Originally Posted by JesseMD

Code:

...
Disk /dev/sdc: 29,74 GiB, 31914983424 bytes, 62333952 sectors
Disk model: Clip Sport Plus 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x943da830

Device     Boot  Start      End  Sectors  Size Id Type
/dev/sdc1       452608 62333951 61881344 29,5G  b W95 FAT32

/dev/sdc1 is the first (and only) partition on the device.

However, there is no /dev/sdc1 mentioned in the output of the mount command, which confirms the partition has not been mounted yet.

To manually mount it, you can do:

Code:

sudo mkdir /mnt/mp3_player
mount /dev/sdc1 /mnt/mp3_player

The directory only needs to be created the first time, and you can change "mp3_player" to any other valid filename.

After mounting, you should be able to access the path /mnt/mp3_player in your file manager, and browse/update the files.

Before physically removing the device, you should run:

Code:

sync
sudo umount /mnt/mp3_player

The sync command forces any cached writes to complete (sometimes the UI claims a copy is complete when it is still in cache).

Also note that umount has only a single n - i.e. it is not unmount.

GPGAgent · 06-10-2022, 01:12 PM

The problem I have with my Sansa Clip is that the mp3 files do not sort correctly

Code:

001_file.mp3
002_file.mp3
003_file.mp3

is how they look on Thunar

But on the sansa clip its ina random order - I can't see how to get the files to sort into the correct order.

boughtonp · 06-10-2022, 04:53 PM

Quote:

Originally Posted by GPGAgent

The problem I have with my Sansa Clip ...

You're asking a different question about a different device - you should start your own thread for that!

(Despite both having "Clip" in their name, the Sansa Clip released in 2007 has both different hardware and different software to the SanDisk Clip Sport Plus released in 2016.)

GPGAgent · 06-11-2022, 11:37 AM

Quote:

Originally Posted by boughtonp

You're asking a different question about a different device - you should start your own thread for that!

(Despite both having "Clip" in their name, the Sansa Clip released in 2007 has both different hardware and different software to the SanDisk Clip Sport Plus released in 2016.)

Yep, sorry, I hijacked this thread - I'll create new one, maybe, it's not strictly linux tho'!