this post was submitted on 23 May 2024
23 points (100.0% liked)

Linux

48328 readers
641 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

Hello all, I've been reading this community from the outside for some time, and I finally decided to dip my toe into Linux a bit. I have an old PC I was using to run Plex through a Windows install, but this is now a Linux Mint Cinnamon machine.

I have Plex Media Server installed and running, however I am having a hell of a time getting it to see my external drive where my media is located.

Trying a bunch of research, it seems like it is a permissions issue that I cannot seem to shake. Plex is able to see the drive, though nothing in it. I've googled as much as I can, but none of the suggestions seem to help me. I've tried to run the command chown, though I get an operation not successful error in return.

ls -la never shows the plex user or group listed, and I've tried for about 2 hours trying various things and have had no success.

Additionally, the other two drives I have connected are stuck in read only as well.

Anything I may have overlooked?

top 7 comments
sorted by: hot top controversial new old
[–] Maxy@lemmy.blahaj.zone 6 points 6 months ago (1 children)

To change the ownership of the files, you should only have to run sudo chown -R user:group directory. -R makes chown run recursively, so it will modify the directory and all subdirectories and files. Do note that changing the ownership to plex:plex or something similar would leave your user unable to normally modify the files. My solution to this was to add both my regular user and the plex (in my case jellyfin) user to the same group. That way both users can easily see and modify the files, as long as the group has read/write permissions (the 2nd column of rwx in ls -Al). If necessary, you can add group permissions with sudo chmod -R g+rw directory.

On a side note: have you considered using jellyfin? It’s a completely free alternative to plex, which recently received a truly massive update with tons of new features. Some people prefer plex’ overall experience, but I’ve been running jellyfin with almost no complaints.

Small disclaimer: I’m writing from mobile, so the commands might not be 100% correct. Run at your own risk, and NEVER POINT A CHMOD/CHOWN COMMAND AT SYSTEM DIRECTORIES LIKE / OR /USR. That’s one of the easiest ways to completely break your system.

[–] korny@lemmy.world 3 points 6 months ago

Thank you! I'll give this a try later tonight and report back!

[–] ClemaX@lemm.ee 2 points 6 months ago

Mount the drive with the user or group as plex. See mount options uid and gid. You can also set precise permissions on the mount point (using options at mount time) to let plex access a subdirectory.

[–] rand_alpha19@moist.catsweat.com 2 points 6 months ago (1 children)

Check out this guide. I used it, it's pretty good at describing stuff for new people.

[–] korny@lemmy.world 1 points 6 months ago* (last edited 6 months ago) (1 children)

I like this guide! However, I keep running into an Operation not permitted error when attempting to change the ownership to the plex.plex group. I've run into this a few times and cannot seem to get around it.

EDIT: Got it working, though still running into an operation not permitted error. Though, I unmounted and remounted the drives changing the uid to a new mount point. Plex is able to see the files now!

Now to start messing with docker...

EDIT 2: Short lived, changes revert after reboot and have to remount again with changes.

[–] rand_alpha19@moist.catsweat.com 1 points 6 months ago

I think your drives may not be mounted correctly (they are not in your fstab so the mount doesn't persist after reboot); this comes up in the comments of the guide. Maybe this comment will help you.

[–] applepie@kbin.social 1 points 6 months ago

Is it flatpakm