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

JesseMD · 06-11-2022, 12:09 PM

Quote:

Originally Posted by boughtonp

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

/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.

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.

Thank you boughtonp for explaining so thoroughly.

boughtonp · 06-11-2022, 12:29 PM

Quote:

Originally Posted by JesseMD

then received the message "only root can do that" which goes entirely over my head lol.

Sorry, my mistake - in this situation mount needs to be run as user "root" (i.e. the superuser/system admin account).

The easiest way is to prefix the command with "sudo " (same as with mkdir/umount lines, i.e:

Code:

sudo mount /dev/sdc1 /mnt/mp3_player

(One could also login as root in a different console, or use "su -" to switch terminal user to root before running the commands.)

JesseMD · 06-11-2022, 12:41 PM

Ok that one came back as:

Code:

user@linux-laptop:~$ sudo mount /dev/sdc1 /mnt/mp3_player
[sudo] password for user:         
mount: /mnt/mp3_player: special device /dev/sdc1 does not exist.

To be honest if its a lot of trouble to make it work I'll just return the thing and get something else lol.

ondoho · 06-12-2022, 12:39 AM

Quote:

Originally Posted by JesseMD

Code:

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.

JesseMD · 06-12-2022, 07:51 AM

Quote:

Originally Posted by ondoho

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.

GPGAgent · 06-12-2022, 11:14 AM

Quote:

Originally Posted by JesseMD

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.

Did you read post #11?

https://www.linuxquestions.org/quest...5/#post6359950

boughtonp · 06-12-2022, 12:05 PM

Quote:

Originally Posted by GPGAgent

Did you read post #11?

Did you read post #10, or post #16, or consult the user manual?

As JesseMD has stated twice, and the manual confirms: SanDisk Clip Sport Plus does not have a USB Mode setting.

linux-man · 06-12-2022, 10:15 PM

Can we safely conclude that there are some mp3 players that are linux friendly and some that aren't?

GPGAgent · 06-13-2022, 06:50 AM

Quote:

Originally Posted by boughtonp

Did you read post #10, or post #16, or consult the user manual?

As JesseMD has stated twice, and the manual confirms: SanDisk Clip Sport Plus does not have a USB Mode setting.

Awfully sorry, I didn't read that - if that's not irony I don't know what is.

Please accept my apologies.

GPGAgent · 06-13-2022, 07:08 AM

Okay folks my final say on this.

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.

Hope that helps.

GPGAgent · 06-13-2022, 09:55 AM

Quote:

Originally Posted by frankbell

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

Sorry No, this device is MCP only from their own knowledge base:

NOTE: SanDisk Clip Sport, Sport Jam, Clip Sport Plus, Clip Voice and Clip Sport Go are MSC-only devices.

https://kb.sandisk.com/app/answerswe...d/1141/kw/1141

enigma9o7 · 06-13-2022, 04:54 PM

MSC only means mass storage, shouldnt' that just appear as a disk?

GPGAgent · 06-14-2022, 12:21 PM

Quote:

Originally Posted by enigma9o7

MSC only means mass storage, shouldnt' that just appear as a disk?

It does, see post #25

WoodrowCall · 06-16-2022, 09:52 AM

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).

Code:

sda                                                                            
├─sda1 vfat                1980-5D3B                               511M     0% /boot/efi
├─sda2                                                                         
└─sda5 ext4                365b5e54-0948-42f3-bc65-a3f637227b32  340.7G    22% /
sdc

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.

GPGAgent · 06-17-2022, 12:09 PM

Quote:

Originally Posted by WoodrowCall

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).

Code:

sda                                                                            
├─sda1 vfat                1980-5D3B                               511M     0% /boot/efi
├─sda2                                                                         
└─sda5 ext4                365b5e54-0948-42f3-bc65-a3f637227b32  340.7G    22% /
sdc

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