I tried that at one point and it asked for a password. I tried nothing, but it didn’t work. How can I find out what that is?
You do not need a password if you su as root.
You can do “sudo su” to get a rootshell, in case you do not have a root pwd set and then “su plex”
Got it. I’ll try that tonight after work.
Tried it. I was able to navigate to the folders and run a “file {filename}” on one of the MP4 files to verify that it could actually read a file. I had to give the plex user a shell, but it worked. So that doesn’t explain why it can’t see the files on the media browser.
@Orko & @ChuckPa For kicks and grins…I tried changing the mount point. I set it to /home/ryan/Movies and plex can see it just fine now. I don’t want to leave it that way so I’d appreciate any other suggestions you might have for getting it to see it like it was.
Use the How-To I listed above as an example.
You can use any naming you want provided it isn’t a reserved (existing) directory
Well if the plex user can access the files but the plexmediaserver does not see them at all points to an issue with plex itself (or plex runs under a different user)
I did follow those instructions, down to mounting options selected for that path…nothing helped. Since it’s an LV in a RAID array there is no block ID. So it does not appear that you can use any path outside of reserved or existing directories. As I said, my folder path is /data1/Videos/Movies (not a reserved or existing directory) where Videos is a mounted LV folder. The PMS explorer CANNOT see /data1 at all (let alone Videos or Movies). It’s not listed. I can type the path in, but I get a "Marking media not available in /data1/Videos/Movies" error in the logs. No reason why. Plex user can navigate to the folder (in a shell), but Plex Scanner doesn’t see a blasted thing. I tried creating a /test folder and it did not appear in the explorer either. What really looks odd to me is that there are other folders in the PMS explorer that aren’t actually in the root / path at all! So it’s like there is a whitelisted folder set that limits paths available and it only displays those regardless of presence.
I once created in my mounting folder for PMS and called it Multimedia into which, the plex mounts were placed. Checking the permissions helped also are the disks, local or remote? I found that when setting up remote mountings, for some both needed a static IP address, if there is a permitted IP restriction. This is especially true if using NFS based file sharing for the linkup of the PMS content sharing. Plus check the account mapping setting when utilising ASUSTOR based NAS devices, with the NFS service to ensure that the drive mapping works.
It is noticeable when utilising ASUSTOR based devices when the NFS service is active. Also when browsing switching to root file system is required (for /data1 or /multimedia).
It’s a local EXT4 partition. At Orko’s direction, I checked the path that the plex user could navigate to the folder and it could, so it doesn’t appear to be a permissions issue.
8 posts were split to a new topic: Linux permissions - Using ACLs
Can you screenshot what your pms sees and pastebin what your / looks like?
And also a “ls -dal /data1”
If your plex sees additional folders in your / dir, that are not there on the FS, that would suggest pms is chrooted/jailed/containered in some way. What device are you running pms on, how did you install it?
I took several screen shots and ran several commands. Here’s a Google Drive with the data. Most notable, /meta and /writable are present in the plex explorer, but not in the root tree. Alternately, /data, /data1, and /home1 are present in the root tree, but not plex explorer. I’m running on Ubuntu 20.04 that I just installed last week. I downloaded the deb installer directly from plex and installed using dpkg -i. I am thinking about seeing if PMS on docker would work.
https://drive.google.com/drive/folders/1XuUc-mpaoAhL9ysor_7D3e7h2JudR-ic
This is strange.
It does not seem like those are the same dirs. But i don’t know how this could happen with the .deb package.
I also have no clue where /meta or /writable come from
What happens if you do a “mkdir /etc/removeme” is that then visible in tne pms file explorer thingie?
I am kinda out of ideas, sorry 
maybe @ChuckPa can help.
Edit:
I know you said you used a debian package but just to be sure can you double check snaps? (With “snap list” iirc)
There are a few different conversations going on here (appear to be different users) where one has a solution and one does not.
May I request a fresh thread with the current state, including the existing /etc/fstab and directory listing of the mount points in the OP?
There are not really multiple issues. It’s one issue that at least 2 people have identified. The issue is directories are not appearing in the PMS explorer. Directories that are not listed as restricted (/run & /media). One user found a workaround (mounting to his home directory) and the other user, me, is not willing to use that workaround because it’s stupid and shouldn’t be necessary because as you said, “You can use any naming you want provided it isn’t a reserved (existing) directory”. /data and /data1 both qualify in that criteria. I have expounded the issue because I seem to see that what PMS sees is not what is in the tree…and it sees some things that aren’t there. So are you able to help us get to the bottom of what is going on in PMS?
Yes, I can help work this out.
Please show me:
- /etc/fstab for the mount points
- ls -la of the directory mount points before mount
- ls -la of the directory mount points after mount
The ls commands are in the screenshots at the Google Drive link I shared above. I’ll have to get the fstab record tonight.
Please post here instead. It makes my life infinitely easier if everything is in front of me and I’m not going out to different sites.
I would prefer console output (copy/paste), using code (```) bracketing, of the text. No screenshot required.
example:
```
pasted text
```
becomes
pasted text
This may be the case, but it’s the Snap version which is installed which is actually running and attempting the scans:
Note the “Ubuntu snap x86_64” text in the build line.
I’d suggest removing the Snap version with sudo snap remove plexmediaserver. You may or may not need to uninstall and reinstall the .deb package, but you’ll almost certainly need to claim the server again after starting the correct version.
