how to chmod a drive or folder on a secondary internal drive
-
I have a Plex server setup on Ubuntu 16.04 which happens to be the same server as my fog server, the issue is Plex cannot see anything on the second and third drive other than the drive it self, now If I navigate to kmy homee directory is can see all of it? anyways help please
How do I make these files readable on Plex?
Thanks
-
@dureal99d What is Plex?? Can you please show is a full directory listing of what you see and we probably can help you with this. So
ls -al ...
and possibly as wellmount
-
Sure thing, this is plex >>>> https://plex.tv/ad/getstarted
/dev/sdb /media/dureal99d/Mass\040data\040Volume ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/sdc1 /media/dureal99d/Mass\040Data\0402 ext4 rw,nosuid,nodev,relatime,data=ordered 0 0the 2 drives above are what I’m trying to get the media reconized on how ever all I see is this > 0_1464069314945_cropped 1 plex
notice how none of the folders are showing, however if I go to my home directory you will see this > all the folders show.
its really weird and it has something to do with drive permissions, but I am novice on how to set them
-
What do you see when running this command:
ls -al /media/dureal99d/
My guess: It’s not permissions but the honky spaces in the directory names! While most filesystems (especially ext4) can handle spaces there are a lot of potential pitfalls along the chain of tools and software you are using to try and access those with Plex…
-
total 16 drwxr-x---+ 4 root root 4096 May 22 22:00 . drwxr-xr-x 3 root root 4096 Nov 23 18:27 .. drwxrwxr-x 28 dureal99d dureal99d 4096 May 22 01:49 Mass Data 2 drwx------ 33 dureal99d dureal99d 4096 May 23 14:51 Mass data Volume
this is what I see
Mod edited to use code box.
-
@dureal99d said in how to chmod a drive or folder on a secondary internal drive:
/dev/sdb /media/dureal99d/Mass\040data\040Volume ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/sdc1 /media/dureal99d/Mass\040Data\0402 ext4 rw,nosuid,nodev,relatime,data=ordered 0 0What’s up with the back slashes?
/media/dureal99d/Mass\
040Data\
0402 -
@Wayne-Workman said in how to chmod a drive or folder on a secondary internal drive:
@dureal99d said in how to chmod a drive or folder on a secondary internal drive:
/dev/sdb /media/dureal99d/Mass\040data\040Volume ext4 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/sdc1 /media/dureal99d/Mass\040Data\0402 ext4 rw,nosuid,nodev,relatime,data=ordered 0 0What’s up with the back slashes?
I noticed that as well and I have no clue as to what, how, why or where they came from. I too am perplexed by those
/media/dureal99d/Mass
\
040Data\
0402 -
@dureal99d said in how to chmod a drive or folder on a secondary internal drive:
\040Data\0402
I bet I know why , its because I have spaces in the drive names . I’m going to rename the drives and see if that solves that backslash issue.
-
@dureal99d just guessing but I think it’s how fstab associates spaced names. In fstab terms,\040 translates to a space.
-
Why do you need Plex to view image files, what is the end goal? And is FOG working?
There are far simpler ways to copy/share the images than Plex.
-
@dureal99d ok renaming the drives solved the back slash issue, also I got the permissions set on the drive but I have no clue as to how I did it. I going to retrace my steps and get back to how I did it here on this forum.
-
@Sebastian-Roth said in how to chmod a drive or folder on a secondary internal drive:
My guess: It’s not permissions but the honky spaces in the directory names! While most filesystems (especially ext4) can handle spaces there are a lot of potential pitfalls along the chain of tools and software you are using to try and access those with Plex…
I told you…
-
@Wayne-Workman Yes fog is working fine, I use plex as a media server on the same system. I use it so I can use the xbox in my room to view many media I have on my drives.
I simply used the gui to set the permissions on the drive.