Look at the permissions!
660 ??? On Linux, PMS runs as plex:plex. not users.
I think you want 664
Look at the permissions!
660 ??? On Linux, PMS runs as plex:plex. not users.
I think you want 664
the thing is when we tried to change permissions earlier it didnāt work - even logged in as root trying to chmod 777 just one file, it didnāt work
it just ignored that I tried to do anything. Again, maybe a server issue 
Okay, here I told it to chmod just one file, and it reports that it did it successfully - but when I change that file, it has bounced right back to the 660ā¦

Go to the server side (where the media is). Change the permissions there (the export permissions).
so you mean the where itās actually located on the server, not just the mount location? Going to try thatā¦
Yes.
If you changed it locally and it ābounced right backā, the server is overriding
On the server, be certain to give āeveryoneā permission to āreadā
Okay hereās what Iām seeing in /var - symlink reflecting where greyhole moved the file:
This is what Iām seeing in the greyhole directory:

where is this symlink? what is it pointing to?
You should be accessing the SMB mount point directly and not through a maze of symlinks on the Linux side
this is all what Amahi/greyhole is doing.
So initially, I was working on the files at the location they are mounted, which is
/mnt/samba/Media/Tutorials/Saxon76
Usually, on Amahi their physical location would be
/var/hda/files/media/Tutorials/Saxon76
Because I have greyhole pooling drives, those files actually at the greyhole location you see in the symlinks above
/var/hda/files/drives/201612-3TB/gh/Media/Tutorials/Saxon76
Where is the pooling occurring? The Windows side or the Linux side?
Itās all on the linux side. Iām changing permissions via an SSH tunnel (using putty) to the linux box too. I was just working in the location that the files are mounted on the linux box since Amahi recommends that you only make changes in mounted files (not actual file locations).
I did transfer the files into the mounted directory via Windows, but have done so with all the media weāve added to Plex in the past.
Hereās the Amahi wiki page on greyhole, the drive pooling: https://wiki.amahi.org/index.php/Greyhole
Again, never had any issues before now and Iāve been running this server with pooled drives for probably 2+ years and Plex for at least a year at this point.
While I canāt remember with certainty, I think this is the type problem others have run into. Some things would work and others wouldnāt all without reason/logic.
The addition of Greyhole is a whole layer of application. I did not know Greyhole existed until you mentioned it here. It sounds like a āfusionfsā type mechanism and those are a bear over networks. What it does when coupled with network mounts is a complete unknown. Amahi is the other unknown. My only experience with FC21 was using it to jump directly to 22 (it was that unstable). Unfortunately, Iām not outfitted to setup and learn how greyhole or amahi works.
I think this is where youāre going to have to create alternate mount points of the same source media to experiment with
Youāre beyond what I can help you with. It is clear. The mount permissions (what Greyholeās fusion of the remote shares) generates is not granting the third octet (what Plex needs) to read your media. That octet is your focal point. (the 660 vs 666 ⦠last octal digit)
Probably nothing more than because you should be using an āOther Videosā type library, not a movie library. They arenāt movies. An other videos library uses the Plex Video files scanner
there is nothing wrong with permissions it sees the files fine.
Jan 12, 2018 09:11:50.035 [0x7f81b9bc2800] DEBUG - * Scanning directory /mnt/samba/Media/Tutorials/Saxon76 (parent: yes)
Jan 12, 2018 09:11:50.039 [0x7f81b9bc2800] DEBUG - Adding file for scanner: /mnt/samba/Media/Tutorials/Saxon76/S76_008_Lesson-084.mp4
with names like S76_002_Lesson-003.mp4 it is probably being interpreted as a TV show Season 76 episode 2. TV show files are intentionally ignored in movie libraries. I know you have other files like that but an S means Season to the movie and tv scanners.
DOH! I missed that! Thanks @BigWheel
Yep, BigWheel is correct - I didnāt realize that I had that one set as a Movie directory - and that also explains why this set didnāt import being named S76 for Saxon Math 76; the other set was all A1 for Algebra 1
It is scanning again and seeing the files now.
Anyways, thanks for your help Chuck. I should look into another solution for this server to get it on a supported distro.
I am VERY sorry i missed the scanner. I assumed everything was set the same. I should have verified. Thank goodness for teamwork here ! 
Yes, I would migrate to something mainstream which is supportable as soon as possible/convenient.
When you do, perhaps a more structured mount directory scheme? Itāll allow you to avoid ādrive poolingā .
The drive pooling is to take advantage of the storage capacity of all the HDDs in the machine. The operating system is on a 300gb drive. Then I have a 3tb and a 2tb drives pooled via greyhole. Those act as one seamless storage pool. I like that functionality of pooling the drives because it means I donāt have to keep track of what is on which drive. I just access the mounted shares and could add another drive to the pool if storage gets low. Iām open to looking at other solutions though.
Adding multiple shares (mount points) to a Library is the easiest solution.
I mount nas:/movies and nas:/movies2 in Linux . Those are structured to fit on 8GB external backups.
In PMS, I add both those mount directories and the resultant library is completely unified.
( because i just noticed, you should change your username to not be your email https://app.plex.tv/desktop#!/account )