Hi,

 

I've finally got my Plex Server back up and able to see my Tower with most of my Movies listed.  But when I try to play any of them (previously working) they fail.  My Movies have been saved to MP4 and/or MKV format.  At the moment my configuration files are:

 

/config = /mnt/user/appdata/plexmediaserver and

/transcode = /mnt/appdata/plexmediaserver/transcode

 

My cache is composed of 2 Evo 850 250 SSD's.

 

At least I'm seeing my Movies, which had disappeared totally until today.  I still don't have all of them, but that's another issue and may be a Plex problem.

 

Any help would be most appreciated.

 

Dave

 

 

Post in the support thread for the version you're using.

Post in the support thread for the version you're using.

 

CHBMB,

 

Love too - don't see the support thread.  Can you move/transfer to the appropriate location?  Version is /needo/Plex:latest.  Version per Plex = Version 1.1.4.2757

 

Dave

To add to my problem, I've logged out and logged into my Plex Server as well as restarted the Plex Docker after turning everything off on my server first.  Now I can't even see my Tower and Movies.

 

Jeez!

 

D

When I search for the Container Support for Plex, I get how to encrypt the container .....

 

Help please, this is very frustrating!

 

D

...

/transcode = /mnt/appdata/plexmediaserver/transcode

...

This location does not exist on any of your disks. Is this really how you have it mapped?

Yes, that's what I found in the Plex directions.  I thought it went to my cache drive, but I may be mistaken.

 

As it currently stands, I can no longer login to my Tower (default server) for Plex and my Movies.

 

Dave

That transcode location is going to be created in RAM and you may have run out of memory.

Certainly possible, but I have 24 GB of ECC Memory and am not using the Server for anything else at this time.

 

D

 

PS, now I getting Plex Media Server Not Found

There is no good reason I can think of to use that incorrect volume mapping for transcoding. If you really wanted to transcode to RAM the more correct way to do so would be to map to /tmp. However, I think it has been determined that transcoding to RAM is not allowed by the application. There are forum posts about this. See search tips in my sig.

 

If you don't understand why that is an incorrect volume mapping then maybe you have some other things set up wrong also. The only things which actually exist in /mnt are /mnt/disk# for each disk, /mnt/cache for the cache disk, and /mnt/user for the user shares (and /mnt/user0 for the user share data excluding any cache), and anything in /mnt/disks if you have something mounted with Unassigned Devices.

 

/mnt/user/appdata exists, /mnt/appdata does not. If you use a path in /mnt that doesn't exist, the directory will be created, but it won't have anything mounted there, so it is just in RAM like all the other unRAID folders that haven't had anything mounted in them.

 

If you don't understand why that is an incorrect volume mapping then maybe you have some other things set up wrong also.

 

Trurl,

 

Correctomundo!!!  Despite having had unRAID since almost the beginning (v3+), I'm truly a neophyte when it comes to proper configuration(s).  I went back to the beginning and your Search system recommendation but still, I'm having problems trying to get my system and all my Dockers setup correctly.

 

At this point its almost become information Overload.  While I absolutely appreciate all the fantastic feedback from so many wonderful, gifted and knowledgeable members, it would be nice if somewhere there were "simple" configurations that are known to work!  The nuances and tweaks that make things work better and provide a greater understanding tend to overwhelm the casual user or in my case the Ole Fart!

 

I've upgraded multiple times and with each upgrade (typically better) I've also suffered multiple failures.  I've tried to add additional capabilities to my unRAID (now v6.2) as they become available but few are just as simple as they seem.  I think that is because we don't have the known parameters that work.  Admittedly everyone has a different system with different capabilities, but generally the basics should work, if not then we can ask for help!

 

I may be out of turn, but I believe that the questions/posts/responses to many things, could be reduced, if we started from a basic assumption - config/set of parameters etc.  I know my life would be easier and I wouldn't be making "dumb" mistakes as you mentioned.  I love unRAID, I just want it to work, the simpler the better!

 

Dave

Do you have Community Applications installed? That is the easiest way to choose and install dockers. Best is to just start with the default settings from the particular docker template and go from there with specific questions. Have you read the Docker FAQ?

 

Also, Community Applications gives a link to the support thread for each docker. That is the best place to research and ask questions about a specific docker you are trying to get to work. A little reading of the specific support thread will probably show you what others are doing.

Trurl,

 

Yes, I have CA and have used it to load my Docker's, but I should go look at the support threads.

 

Yes, I have read the Docker FAQ and have even gone into Midnight Commander and removed my previous installations and started over.

 

I was only trying to point out what some of us feel (or at least me), Dockers and the various programs/apps/ plugins create, wonderful applications but often so complicated, we can rarely get them to work as described.

 

In addition to my Plex, I'm having problems with Crash Plan and MKV-RDP.  It is often simply a case of normal settings/configurations being wrong despite suggestions.  I believe they should have the basics that work for 90% of the cases, tweaks notwithstanding. 

 

Dave

 

PS - Trurl, you've been very helpful to me personally and I appreciate it very much!

I was only trying to point out what some of us feel (or at least me), Dockers and the various programs/apps/ plugins create, wonderful applications but often so complicated, we can rarely get them to work as described.

By and large the hardest part with docker apps is wrapping your head around the volume mappings.  And unfortunately its one of those subjects that is actually dirt simple, but a real pain to describe.  (And I have a couple of attempts in the FAQ attempting it)

 

While I don't actually recommend it, the simplest way around volume mappings is doing what JustinChase describes in the FAQ here: http://lime-technology.com/forum/index.php?topic=40937.msg387919#msg387919 (tldr: map /mnt/ to /mnt/)  Beyond that, docker has opened up a new world of available applications to unRaid, and the actual setup and usage of those applications are subjects that are sometimes best on the app's own forums (within CA you'll see that as the Project Page), although the forum members here do an amazing job of support for the actual apps themselves.  (better in some cases than the support on the Project Pages)

It is often simply a case of normal settings/configurations being wrong despite suggestions.  I believe they should have the basics that work for 90% of the cases, tweaks notwithstanding. 

Unfortunately that is sometimes true, although it isn't always possible to set the application's defaults to something that makes sense.

Since you mention Midnight Commander, you might take some time to explore your unRAID to get an idea of what is happening "under the hood".

 

If you go to /mnt, you will see each of the disks, and a user folder, and if you have a cache drive, there will also be a user0 folder. In /mnt/user, you will see each of the user shares. /mnt/user0 is just the user shares excluding anything on cache. It is used by mover. Mover works by moving folders from /mnt/cache to /mnt/user0.

 

The user shares are simply the aggregate of all top level folders from cache and the array disks. If you create a user share, unRAID creates top level folders on one or more disks as needed according to the settings you make for the user share. If you create a top level folder on a disk, it is automatically a user share with default settings.

 

If you go to /boot, you will see the contents of your flash drive. Many of the files on flash are plain text so you can read them to see what is in them. In config, you will see .cfg files that contain webUI settings. In config/shares, you will see settings for individual shares. In config/plugins, you will see the .plg files and folders the plugins have created to hold their things. Keep drilling down and you will see the docker settings stored there by the docker manager, a built-in plugin.

 

Etc.

 

It can really make the whole system a lot less mysterious if you explore it a little.

 

And if you understand volume mappings, most of the mystery of setting up dockers is solved.

 

And if you understand parity, how to rebuild disks and change or add disks makes a lot more sense too.

 

I know there is a lot of stuff, but there really isn't any way to condense it into a short page. The forum and wiki are how we all learn this stuff too.

 

And if you haven't already (maybe I already pointed you to it before), see the How to Search link in my sig.

Thanks to both of you - Squid/Trurl

 

I recognize your expertise and appreciate your time to respond!!!  My problem tends to be the frustration that occurs after reading and trying to implement the suggestions when they continue to fail. 

 

Right now, notwithstanding the Transcode issue that prompted this thread, I was able to see my Tower and the Movies I had stored. 

 

After adding the "wrong" transcode config, updating the Plex Docker, restarting the Plex Docker and logging off Plex and logging into Plex, I no longer see my Movies on Tower. 

 

Transcode isn't an issue if the Movies can't be seen - hence all of my FRUSTRATION! 

 

Dave

Thanks to both of you - Squid/Trurl

 

I recognize your expertise and appreciate your time to respond!!!  My problem tends to be the frustration that occurs after reading and trying to implement the suggestions when they continue to fail. 

 

Right now, notwithstanding the Transcode issue that prompted this thread, I was able to see my Tower and the Movies I had stored. 

 

After adding the "wrong" transcode config, updating the Plex Docker, restarting the Plex Docker and logging off Plex and logging into Plex, I no longer see my Movies on Tower. 

 

Transcode isn't an issue if the Movies can't be seen - hence all of my FRUSTRATION! 

 

Dave

What I'm thinking is that the incorrect mounting for the transcode has basically filled up your RAM, which can cause some very weird issues since random processes can get killed to free up the memory.

 

Personally, I would

- Post your diagnostics

- Reboot the server

- See if you still can't access the Movies share, and if you can't, post another set of diagnostics

 

/config = /mnt/user/appdata/plexmediaserver and

/transcode = /mnt/appdata/plexmediaserver/transcode

After rebooting, stop your plex docker if it is running, then change your transcode mapping to this:

 

/transcode = /mnt/user/appdata/plexmediaserver/transcode

 

 

 

/config = /mnt/user/appdata/plexmediaserver and

/transcode = /mnt/appdata/plexmediaserver/transcode

After rebooting, stop your plex docker if it is running, then change your transcode mapping to this:

 

/transcode = /mnt/user/appdata/plexmediaserver/transcode

You're correct here, trurl...