linux mint recognizes mp3 and charges but doesnt allow transfer of files
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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.
Ok, tried that and here's what I got:
Code:
user@linux-laptop:~$ sudo mkdir /mnt/mp3_player
mkdir: cannot create directory ‘/mnt/mp3_player’: File exists
user@linux-laptop:~$ sudo mkdir /mnt/mp3_player2
user@linux-laptop:~$ mount /dev/sdc1 /mnt/mp3_player
mount: only root can do that
user@linux-laptop:~$
So it said file exists which is my I added a "2" to it, then received the message "only root can do that" which goes entirely over my head lol.
Also, for the last time,
Quote:
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
It doesn't work like that:
Quote:
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.
mount: /mnt/mp3_player: special device /dev/sdc1 does not exist.
That's strange because your fdisk output from post #10 clearly states that /dev/sdc1 exists.
Maybe the drive letter has changed?
Check fdisk again before you attempt this.
And please make an effort to understand the commands you are entering. E.g. mkdir means "make directory" - if you issued the command twice, well of course it will complain that the directory already exists.
But in one thing I agree: the real question here is why your desktop environment doesn't recognize your mp3 player and automatically provides a mountpoint and a clickable icon. This web search suggests that there's a lot still left to research. Some are even marked SOLVED.
But in one thing I agree: the real question here is why your desktop environment doesn't recognize your mp3 player and automatically provides a mountpoint and a clickable icon.
I just want to say thank you to everyone who's been helping me troubleshoot this but at this point I think I'm going to return the mp3 and get something that's a little more universally compatible.
I just want to say thank you to everyone who's been helping me troubleshoot this but at this point I think I'm going to return the mp3 and get something that's a little more universally compatible.
I have Sansa Clip and it's set to MSC mode. This appears as a drive and I've posted an image of this in an earlier post, and I've attached it again
SanDisk Clip Sport Plus is set to MSC mode - you cannot change this and this mode will work
You can find out more here https://kb.sandisk.com/app/answerswe...d/1141/kw/1141
And this article has this line: NOTE: SanDisk Clip Sport, Sport Jam, Clip Sport Plus, Clip Voice and Clip Sport Go are MSC-only devices.
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.
Successfully Added Music to SanDisk Clip Sport Plus
I purchased a SanDisk Clip Sport Plus a couple days ago without thinking too much, and ran into this problem of getting it to work with Linux. After some google fu and some guesswork, I was able to mount the disk and add songs. Here's how I solved it.
1. Run `lsblk -f | grep sd` with the player unplugged, then plug it in and run the command again. My player showed as "Storage Device C" (sdc) at the bottom (see below).
When I tried to mount sdc with `sudo mount /dev/sdc` , I got this error:
Code:
NTFS signature is missing.
Failed to mount '/dev/sdb': Invalid argument
The device '/dev/sdb' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
After some research, I tried mounting sdc as vfat (along with some other formats) with `sudo mount -t vfat /dev/sdc ~/SanDisk` and got this error multiple times:
Code:
mount: /home/connor/SanDisk: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error.
2. Since it looked like `sdc` had no partitions, I used `fdisk` ( a tool for creation and manipulation of partition tables) to inspect the device.
Code:
fdisk -l /dev/sdc
The results provided some info on the device and a clue as to why the mount wasn't working.
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: 0xb0c054c3
Device Boot Start End Sectors Size Id Type
/dev/sdc 452608 62333951 61881344 29.5G b W95 FAT32
3. As seen in the results from `fdisk`, there are no partitions, meaning storage is using the whole drive. Also, the storage doesn't start at the beginning of the drive - it starts at 452608 sectors. `mount` has a `-o` flag for options, one of which is an offset. I tried 452608 as an offset, but it didn't work because it takes bytes, not sectors. according to the results, 1 sector is 512, so the offset is 452608 * 512 = 231735296. When I used this offset as shown below, the player mounted right up!
Code:
mkdir ~/SanDisk
sudo mount -t vfat /dev/sdc ~/SanDisk/ -o offset=231735296
I purchased a SanDisk Clip Sport Plus a couple days ago without thinking too much, and ran into this problem of getting it to work with Linux. After some google fu and some guesswork, I was able to mount the disk and add songs. Here's how I solved it.
1. Run `lsblk -f | grep sd` with the player unplugged, then plug it in and run the command again. My player showed as "Storage Device C" (sdc) at the bottom (see below).
When I tried to mount sdc with `sudo mount /dev/sdc` , I got this error:
Code:
NTFS signature is missing.
Failed to mount '/dev/sdb': Invalid argument
The device '/dev/sdb' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
After some research, I tried mounting sdc as vfat (along with some other formats) with `sudo mount -t vfat /dev/sdc ~/SanDisk` and got this error multiple times:
Code:
mount: /home/connor/SanDisk: wrong fs type, bad option, bad superblock on /dev/sdc, missing codepage or helper program, or other error.
2. Since it looked like `sdc` had no partitions, I used `fdisk` ( a tool for creation and manipulation of partition tables) to inspect the device.
Code:
fdisk -l /dev/sdc
The results provided some info on the device and a clue as to why the mount wasn't working.
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: 0xb0c054c3
Device Boot Start End Sectors Size Id Type
/dev/sdc 452608 62333951 61881344 29.5G b W95 FAT32
3. As seen in the results from `fdisk`, there are no partitions, meaning storage is using the whole drive. Also, the storage doesn't start at the beginning of the drive - it starts at 452608 sectors. `mount` has a `-o` flag for options, one of which is an offset. I tried 452608 as an offset, but it didn't work because it takes bytes, not sectors. according to the results, 1 sector is 512, so the offset is 452608 * 512 = 231735296. When I used this offset as shown below, the player mounted right up!
Code:
mkdir ~/SanDisk
sudo mount -t vfat /dev/sdc ~/SanDisk/ -o offset=231735296
Hope this diagnostic process helps y'all.
I just plugged mine in and it was recognised - I'm using Minto 20 - maybe I was just lucky
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.