WLUG

By thread

wlug@lists.wlug.org

December 2019

13 participants
32 messages

Re: Plex media drive mount point

by Andrew Oprea

I doubt that Plex has some limitation related to browsing 5 directories deep. I'm curious what file system you've used on that 2.7T drive. I know I've written things to ext3 and ext4 drives, reinstalled a linux distro with my usual usernames (but randomly generated UID!) and been unable to browse my reused storage media. This isn't a issue with a VFAT drive, because those files don't have an owner. See if your user account can browse that directory structure? Maybe you will have to chown all the folders and files on that drive. Does Plex run as its own UID, or does it use your usual user one? (This question implies Plex is a server running on this machine, is that the case, or are you using the Plex app on another device?) Maybe you will have to add the Plex user to a group that has access to that drive (or to hot mountable drives generally)? - Drew On Sat, Nov 30, 2019 at 10:51 PM Richard Klein via WLUG <wlug(a)lists.wlug.org> wrote: > > I blew away my Linux Mint installation today and installed Manjaro. All my media for my Plex server was on a separate drive that was mounted at /Media. Now it's at /run/media/richspk/Media/, and Plex can't see anything below richspk. My /etc/fstab is much more spartan than I'd expected. sda is a Windows install, sdb is media, and sdc is the Manjaro install. Should I add /Media (sdb) to /etc/fstab, or should I mount it some other way? This is what /etc/fstab looks like right now: > > # /etc/fstab: static file system information. > # > # Use 'blkid' to print the universally unique identifier for a device; this may > # be used with UUID= as a more robust way to name devices that works even if > # disks are added and removed. See fstab(5). > # > # <file system> <mount point> <type> <options> <dump> <pass> > UUID=26dedffb-3099-4a86-b565-c2e8adec81b2 / ext4 defaults,noatime,discard 0 1 > tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 > > And current block devices: > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID > loop0 7:0 0 89.1M 1 loop /var/lib/snapd/snap/core/8039 > sda 8:0 0 465.8G 0 disk > ├─sda1 8:1 0 500M 0 part B6AAD05DAAD01BA5 > ├─sda2 8:2 0 464.5G 0 part E002D31A02D2F50E > └─sda3 8:3 0 846M 0 part 9294B21894B1FF33 > sdb 8:16 0 2.7T 0 disk /run/media/richspk/Media 946b363e-ec7e-49d1-a5f2-f06caf8e4e21 > sdc 8:32 0 931.5G 0 disk > └─sdc1 8:33 0 931.5G 0 part / 26dedffb-3099-4a86-b565-c2e8adec81b2 > _______________________________________________ > WLUG mailing list -- wlug(a)lists.wlug.org > To unsubscribe send an email to wlug-leave(a)lists.wlug.org

Dec. 1, 2019

Plex media drive mount point

by Richard Klein

I blew away my Linux Mint installation today and installed Manjaro. All my media for my Plex server was on a separate drive that was mounted at /Media. Now it's at /run/media/richspk/Media/, and Plex can't see anything below richspk. My /etc/fstab is much more spartan than I'd expected. sda is a Windows install, sdb is media, and sdc is the Manjaro install. Should I add /Media (sdb) to /etc/fstab, or should I mount it some other way? This is what /etc/fstab looks like right now: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a device; this may # be used with UUID= as a more robust way to name devices that works even if # disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> UUID=26dedffb-3099-4a86-b565-c2e8adec81b2 / ext4 defaults,noatime,discard 0 1 tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0 And current block devices: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID loop0 7:0 0 89.1M 1 loop /var/lib/snapd/snap/core/8039 sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 500M 0 part B6AAD05DAAD01BA5 ├─sda2 8:2 0 464.5G 0 part E002D31A02D2F50E └─sda3 8:3 0 846M 0 part 9294B21894B1FF33 sdb 8:16 0 2.7T 0 disk /run/media/richspk/Media 946b363e-ec7e-49d1-a5f2-f06caf8e4e21 sdc 8:32 0 931.5G 0 disk └─sdc1 8:33 0 931.5G 0 part / 26dedffb-3099-4a86-b565-c2e8adec81b2

Dec. 1, 2019