Cannot paste files from USB to mounted drive

[dmt]

The lock means you can’t modify it, because it’s mounted.

As @TheHappyHobbit says you need to change ownership.

# $USER is an environment variable 
# which contains the current username
# so you don't have to change it
sudo chown $USER:$USER  /run/media/user/storage # or use a better mountpoint

However I suggest using a mountpoint in /media, rather than auto mounting via a file manager (if you’re already using fstab/systemd then don’t use /run). Read the links below for further information.

For a permanent mountpoint, I'd do this

sudo mkdir -p /media/storage
lsblk -f # Copy the UUID for the partition you want to mount

# Edit /etc/fstab and add the line below
# making sure to replace <uuid> with the UUID
UUID=<uuid> /media/storage ext4 defaults,relatime 0 2

# unmount the partition, if it's already mounted
sudo umount UUID=<uuid>

# Mount it using the fstab entry
sudo mount -a

# run lsblk to see if it worked
lsblk

# if it's not mounted
# then post any errors and the contents of fstab
# don't reboot without first commenting out the bad entry
# by placing a # at the beginning of the line
# a bad fstab entry will cause issues during boot

Click here for some useful links

https://wiki.archlinux.org/title/Fstab

[root tip] [How To] Mount partition using fstab

Make a permanent mountpoint. Linux Foundation Refererence The FHS document has a limited scope: Local placement of local files is a local issue, so FHS does not attempt to usurp system administrators. FHS addresses issues where file placements need to be coordinated between multiple parties such as local sites, distributions, applications, documentation, etc. So for the sake of this article there is no standard as we are talking about Local placement of local files is a local issue and…

[root tip] [How To] Use systemd to mount ANY device

Difficulty: ★☆☆☆☆ Disk device recognition Manjaro uses udev (see Arch Wiki) to load devices at boot time. The loading of devices is arbitrary and therefore you cannot predict which device will be available at a given path. But static device names do exist and you can assign specific locations to your device and thus ensure e.g. scripts will work as expected. What to learn Overview of system mount units Structure and Content of a mount unit Mount at boot (immediate mount) Mount on demand (m…

[Tutorial] Understanding and working with UNIX filesystems and permissions

Difficulty: ★★★☆☆ Note: This post is meant as a tutorial. Please do not post on this thread regarding any problems you’re having with permissions, but start a new thread instead. Thank you. PREAMBLE: THE HISTORICAL BACKGROUND If you are new to the world of GNU/Linux ─ and especially if you come from the Microsoft Windows ecosystem ─ then you will undoubtedly have already noticed that GNU/Linux handles permissions and storage volumes quite differently from what you might be used to …

@TheHappyHobbit

@TheHappyHobbit

To find the path, open a second terminal and run cd .. twice then cd media/ then run ls which should show your username, run cd username/ run ls again and now you should see the name of the partition(s) you need to chown.

So start in /home/$USER then cd .. twice to /, then cd to /media which by default doesn’t exist. Why not just cd /media? It won’t work any better but it’s easier.

The OP has the drive mounted at /run/media/user/storage (presumably /run/media/$USER/storage) which can be seen by using a simple command such as lsblk -f (or reading their post ).