Server Version#: 1.18.7.2438
Player Version#: 4.22.2
I have followed all steps here: Using EXT, NTFS, or other format drives (internal or external) on Linux
Everything is showing just as the tutorial indicates it would in the terminal and all files show to be mounted. I believe the permissions as correct but they must not be because /disks is not visible when trying to add the libraries from the plex server.
Show me please?
What are the permissions of the /disks directory, and those below it, before mounting the other drives?
woodshack@Plex:/disks$ ls -l /disks
total 16
drwxrwxrwx 10 woodshack woodshack 4096 Apr 12 2019 Plex.1
drwxrwxrwx 11 woodshack woodshack 4096 Jun 22 2019 Plex.2
drwxrwxrwx 9 woodshack woodshack 4096 Jun 22 2019 Plex.3
drwxrwxrwx 3 woodshack woodshack 4096 Mar 18 2019 Plex.4
This is all it returns. I am not sure what I did to screw everything up. The system was running fine. I added some movies that the Plex server did not seem to see (others I added worked fine). after much frustration I uninstalled and re-installed the server. Now nothing is working although it all appears to be correct.
When I get to this step:
[root@lizum chuck]# ls /disks/* # this will produce a lot of output if correct. Be prepared
It produces almost nothing. It only returns the file names within the drive
/disks/Plex.1:
AudioBooks lost+found Movies Music ‘TV Shows’ YouTube
/disks/Plex.2:
AudioBooks.2 Movies.2 ‘TV Shows.2’
lost+found Music.2 Workout YouTube.2
/disks/Plex.3:
Audiobooks.3 Movies.3 ‘TV Shows.3’ YouTube.3
lost+found Music.3
/disks/Plex.4:
lost+found
I need more please. I need the ls -la /disks
I need to see the permissions with the disk unmounted and after mounted
Deleted
# sudo umount /disks/Plex.1
# sudo umount /disks/Plex.2
# sudo umount /disks/Plex.3
# sudo umount /disks/Plex.4
# ls -la /disks
total 24
drwxrwxrwx 6 woodshack woodshack 4096 Mar 20 2019 .
drwxr-xr-x 25 root root 4096 Feb 19 07:32 ..
drwxr-xr-x 2 woodshack woodshack 4096 Mar 20 2019 Plex.1
drwxr-xr-x 2 woodshack woodshack 4096 Mar 20 2019 Plex.2
drwxr-xr-x 2 woodshack woodshack 4096 Mar 20 2019 Plex.3
drwxr-xr-x 2 woodshack woodshack 4096 Mar 20 2019 Plex.4
# sudo mount /disks/Plex.1
# sudo mount /disks/Plex.2
# sudo mount /disks/Plex.3
# sudo mount /disks/Plex.4
# ls -la /disks
total 24
drwxrwxrwx 6 woodshack woodshack 4096 Mar 20 2019 .
drwxr-xr-x 25 root root 4096 Feb 19 07:32 ..
drwxrwxrwx 10 woodshack woodshack 4096 Apr 12 2019 Plex.1
drwxrwxrwx 11 woodshack woodshack 4096 Jun 22 2019 Plex.2
drwxrwxrwx 9 woodshack woodshack 4096 Jun 22 2019 Plex.3
drwxrwxrwx 3 woodshack woodshack 4096 Mar 18 2019 Plex.4
Moderator edit: ``` used on preceding and succeeding lines to improve readability
that looks good so far.
Now for /etc/fstab entries to mount them?
# /etc/fstab:
# Addtions for external and internal drives
# Mount
Plex.1
(ext4) at /disks/
Plex.1
for Plex
UUID=46c08549-d342-4011-87ae-a5f9a6a2a6b0 /
disks/Plex.1 ext4
defaults,rw,auto,nofail 1 2
# Mount Plex.2 (ext4) at /
disks/
Plex.2 for Plex
UUID=299515c8-58c2-470c-91c5-2f74731fdab4 /
disks/Plex.2 ext4 defaults,rw,auto,nofail 1 2
# Mount Plex.3 (ext4) at /
disks/
Plex.3 for Plex
UUID=0f7baa38-fb9f-4146-b9b1-d1480172fa2f /disks/Plex.3 ext4 defaults,rw,auto,nofail 1 2
# Mount Plex.4 (ext4) at /
disks/
Plex.4 for Plex
UUID=e175992e-4758-45f9-9603-0e479517d367 /disks/Plex.4 ext4 defaults,rw,auto,nofail 1 2
You didn’t need be so exotic.
As example, this is just as good. the # is a special formatting character and why we escape it.
# /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>
# / was on /dev/nvme0n1p2 during installation
UUID=91c03589-6f7a-4233-ab4b-0ed14ff61df1 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=5313-EB3E /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p4 during installation
UUID=c6834ad7-1891-42a0-a20c-911c298b15bd /home xfs defaults 0 1
# swap was on /dev/nvme0n1p3 during installation
UUID=5cfff4c3-da09-47c2-8ccd-839459bd37c3 none swap sw 0 0
Is this correct? (how you did the last one is great too (that’s the other way).
UUID=46c08549-d342-4011-87ae-a5f9a6a2a6b0 /disks/Plex.1 ext4 defaults,rw,auto,nofail 1 2
UUID=299515c8-58c2-470c-91c5-2f74731fdab4 /disks/Plex.2 ext4 defaults,rw,auto,nofail 1 2
UUID=0f7baa38-fb9f-4146-b9b1-d1480172fa2f /disks/Plex.3 ext4 defaults,rw,auto,nofail 1 2
In those directories:
/disks/Plex.1
/disks/Plex.2
/disks/Plex.3
/disks/Plex.4
where your “movies”, “tv” and other directories are,
Let’s extend this down further with them mounted (we need to before and after)
Set basic read-only for Plex.
find /disks -type d -exec chmod 755 {} \;
find /disks -type f -exec chmo 644 {} \;
You should now be able to create a library section and nagigate to /disks/Plex.1/…
I am not sure why it came through the way it did but this is what it looks like in the text editor 
Do i need to change or remove anything or will it function properly as is?
I am not sure I understand your last. When I type
into the terminal it returns
find: paths must precede expression: `-’
do i need to put
and
#find /disks/Plex.1 -type f -exec chmo 644 {};
for each drive?
the commands I have, inclusive of the \; are required. The escaped ; is what terminates (completes) the -exec clause.
With the drives mounted, these two commands will address all 4 at once.
One for the directories -type d
One for the files -type f
terminal return:
find: ‘/disks-type’: No such file or directory
find: ‘f’: No such file or directory
tried to add library in plex and still not seeing the drives
I tried restarting the plex server and the terminal returned this:
Failed to restart plexmediaserver.service: Unit plexmediaserver.service not found.
careful! you are losing spaces! 
You can copy and paste what I write directly into the command line.
find /disks -type d -exec chmod 755 {} \;
find /disks -type f -exec chmod 644 {} \;
We will address the failed startup in a moment.
