USB mount permissions not automatic

Apologies for an extremely basic Linux question.
For years, I have been able to plug in my MP3 player and download podcasts to it, from a variety of programs. But just yesterday, my player shows up in FILES, but with permission to copy or move files denied.
I found the fix to unmount and hen re-mount thus:
sudo mount -o rw,users,umask=000 /dev/sdc /mnt/sdc

However, now when I unmount (eject) and remount (plug it back in), that problem with permissions is there again.

How did I lose those permissions?
How can I make it automatic again?

I can think of some things I did, but none of them seem to make sense.

Like what?





I removed a bad HDD (I think you know about that one) and in the process may have jostled some connectors. I know I had to unplug and replug the power cord because the start button was not working right away, and the same may have happened to the USB cord. Stuff like that.

If you changed the SATA connector used then your UEFI knows about the different SATA ID that your HDD is connected to and that might change some IDs within Linux. I’m not sure how it could be connected to the command you posted, exactly, but if that is the only thing you changed in your computer, especially regarding the same hardware you have problems with, it seems to be likely connected to this situation.

I did not change them, I just unplugged one and removed it.
And I am still on Legacy mode.

But how do I restore the automatic granting of R/W permissions?

This should be a good starting point.

Does that apply to an MP3 player (FAT32) I only plug in on occasion?

I mean that like “take this as a template and customize it to your needs”.
I would turn off the automatic fsck (by changing the 0 1 to 0 0) and apply the different file system. You can look up the differences when handling external file systems, if there are any, just to be sure.

Here is he entry for USB devices in fstab:

/dev/sdc /mnt/sdc auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0

How shall I edit this entry?
Without editing this, it is two steps to mount it as R/W whenever I plug it in.

I generally would recommend using a UUID, to make sure the correct device is selected. Also, before editing /etc/fstab you should always create a backup and before rebooting you should make sure the entry actually works.

That said, you maybe should specifiy the file system manually. I also found this:

Specifically, the comment in the first answer.

As a bonus, some feed for extensive research:

This post, especially the last article, points in (what I hope is) the right direction, but it is definitely overwhelming for me.
While information in /etc/fstab may be informative, the problem lies somewhere in udev, according to the article.
But what happened to the udev rules? The drive is automounted, it just has limited permissions.
I can either look into the syntax of udev rules, or just run an unmount/remount command when I plug it in, if I understand it right.

I think this is the safest way. You might want to randomly look up stuff, but it wont guarantee a solution. So I think you should take the path that seems more complicated at first, but at least it has a goal that you can reach, whereas random searches don’t guarantee anything.

No, the safest way is to run this command after plugging it in.

sudo umount /dev/sdc && sudo mount -o rw,users,umask=000 /dev/sdc /mnt/sdc

The udev syntax route is the most informative.

Using journalctl -f, I got the following:

Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: new high-speed USB device number 6 using ehci-pci
Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: New USB device found, idVendor=0781, idProduct=74e7
Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: Product: Clip Sport
Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: Manufacturer: SanDisk
Aug 09 07:09:14 cliff-desktop kernel: usb 1-1.4: SerialNumber: 974773246CE44042
Aug 09 07:09:14 cliff-desktop mtp-probe[6248]: checking bus 1, device 6: “/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4”
Aug 09 07:09:14 cliff-desktop mtp-probe[6248]: bus: 1, device: 6 was not an MTP device
Aug 09 07:09:14 cliff-desktop kernel: usb-storage 1-1.4:1.0: USB Mass Storage device detected
Aug 09 07:09:14 cliff-desktop kernel: scsi host6: usb-storage 1-1.4:1.0
Aug 09 07:09:14 cliff-desktop kernel: usbcore: registered new interface driver usb-storage
Aug 09 07:09:14 cliff-desktop upowerd[1711]: unhandled action ‘bind’ on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4
Aug 09 07:09:14 cliff-desktop upowerd[1711]: unhandled action ‘bind’ on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0
Aug 09 07:09:14 cliff-desktop colord-sane[6261]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Aug 09 07:09:15 cliff-desktop kernel: scsi 6:0:0:0: Direct-Access SanDisk Clip Sport PQ: 0 ANSI: 0 CCS
Aug 09 07:09:15 cliff-desktop kernel: scsi 6:0:0:1: Direct-Access SanDisk Clip Sport PQ: 0 ANSI: 0 CCS
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:1: Attached scsi generic sg4 type 0
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: [sdc] 8179712 1024-byte logical blocks: (8.38 GB/7.80 GiB)
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: [sdc] Write Protect is off
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: [sdc] Mode Sense: 00 c0 00 00
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:1: [sdd] Attached SCSI removable disk
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: [sdc] Write cache: disabled, read cache: disabled, doesn’t support DPO or FUA
Aug 09 07:09:15 cliff-desktop kernel: sdc:
Aug 09 07:09:15 cliff-desktop kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk

Which line reveals the nature of the problem, if any?