• Posts

  • Joined

  • Last visited

Everything posted by Leifgg

  1. Yes, I am seeing the same on my system. Some more details: at least 50 % decrease in performance. Jumped directly from 6.8.2 to 6.9.0-rc2.
  2. Have a look in your appdata share and open your Plex folder. Browse to Library/Application Support/Plex Media Server/Crash Reports/ Here you have folders for each version you have had installed and the name of the folder is the same as version number string. So just use this name to specify what version you would like to use.
  3. Sorry I misunderstood, I was assuming you meant that the UPS itself needed to have an Ethernet interface…
  4. It’s not a ”must have”, cool yes but not needed. USB will work, it will be the “master” server that connects to the other servers and initiates the power down, it’s not done by the UPS. Just remember that the router and switch need to be on the UPS as well.
  5. I am using Sandisk Cruzer Fit (the USB 2.0 version) in my servers without any problems.
  6. I am using same version as you (Plex inc) without any difficulties. Only setting I have that is different is the mapping to the appdata folder, I am using /mnt/cache/appdata/Plex/ where you have /mnt/user/appdata/PlexMediaServer/ I don't believe that it makes any difference but you could try changing from /user/ to /cache (from user share to disk share, assuming you are using a cashe disk). I has been mentioned for other containers that this could make a difference.
  7. What I would recommend as first step is to setup transcoding to disk. If you have cash disk use that one (any type, don't need to be an SSD), if not do it to the array. Ask if you need help. You shouldn't try transcoding to RAM until you have Plex working first. You can read more about transcoding to RAM here:
  8. Not sure I understand what you would like to do, if it’s transcoding to disk or to RAM. If you have the Transcoder temporary directory in Plex set to /transcode then you should also have a folder mapping with a Container Path: set to /transcode If the Transcoder temporary directory in Plex is set to something else then the folder mapping for the Container Path: should be set to the same. If they aren’t the same, you will transcode to disk and in this case the docker image. Depending on the size of the docker image you could run out of space when transcoding. The setting that configures the transcoding location is the Host Path: If it’s set to /tmp you will transcode to RAM and hopefully you have enough RAM to do this. If you prefer transcoding to disk, you need to configure Host Path: with the location (folder) that you would like to use. Could be something like /mnt/user/appdata/transcode or similar. Preferably a folder located on an SSD disk but that’s up to you.
  9. Here is an example…. I don’t use binhex container right now, but it shouldn’t be to much different. I have configured Plex to use the folder /transcode (this is what the Plex app in the container can see). Then I have a folder mapping for the Plex container that maps /transcode inside the container (Container Path:) to a location outside the container (Host Path:) In this case I have mounted an unassigned disk (not belonging to the array and not a cash disk). When browsing unassigned disks will show up at /mnt/disks I have labelled my unassigned disk to Unassigned (otherwise I think it will show up with its s/n). I have also created a folder Plex_transcode on that disk that I will use. The Access Mode: should also be set to RW/Slave /Leif
  10. Do you get out of memory errors when using Plex? If that is the case it might be related to transcoding and how the folder mapping is set for the /transcode folder
  11. And not to forget, having a Plex Pass also support the developers to keep a great product getting even better….
  12. Have a look here: https://www.plex.tv/features/ Basically Plex pass gives some more features as well as Beta releases...
  13. Edit the container like described here: Should look like this:
  14. Updated to the latest image and everything is back to normal. Once again, Thanks!
  15. Updated my CrashPlan Pro Docker today but it did not start up, GUI only shows a black screen and log is repeating "app starting CrashPlan...". Any ideas on whats happening?
  16. I am using same Plex docker as you are and have previously used transcoding to disk so that should work as long as there is enough space. Currently I am transcoding to RAM and that works fine as well but I have around 20 GByte available for Plex. Have also been using the linuxserver Plex docker and that has been working fine as well.
  17. One thing to check with Plex is how transcoding is setup. Is it to RAM or to disk?
  18. I have 32 GB as well and a Windows 10 VM running (4 GB) as well as a few dockers and I am able to do transcoding to RAM but my Samsung TV plays most formats natively. Also have remote friends but they have bandwidth limitations so files are likely to decrees in size after transcoding.
  19. Was just waiting for that one coming…. There are so many parameters involved so it’s hard to predict. There are typically three reasons for transcoding, the video stream, audio stream and subtitles. In addition, transcoding might be needed due to the bit rate (to high). All above need to be within what the client player can handle so obviously it will be different for different clients. The number of simultaneous clients playing can increase the required space needed as well. It should also be noted that Plex does the transcoding “on the fly” in smaller data block and they are kept for a while (probably the whole session) so that you can stop playing and revers back in the movie and start playing again. I haven’t checked actual file sizes for a transcoded video, but I believe that a “worst case scenario” would be the total size of the actual movie, but once again I never checked it myself. My suggestion is that you start with transcoding to a folder first and play a full video and look at the files in the transcoder folder to get a feel for what it actually does when using different formats and clients. Let that decide the way to go and keep in mind that running out of memory eventually could crash Plex but potentially the server as well.
  20. That should be correct, also make sure that the "Transcoder temporary directory" in Plex is set to /transcode Transcoding can require a lot of space and there might be risk of running out of RAM.
  21. The boards are C2750D4I and E3C226D2I. Both of them have the latest BIOS as well as BMC firmware. Booting the normal boot menu and using Firefox browser 57.0.1 (32 bit) and Java 8 Update 152. Edit: Wait! Think I added the mod at the wrong place in the cfg file. Should be at the label unRAID OS i guess. Let me try again.... Edit2: Both boards are now working as expected (note to self: read instructions carefully next time....)
  22. Did try this on my two ASRock boards but without luck...
  23. You could install the plugin Unassigned Devices on Tower2 and mount a share using SMB on Tower 1. I am not using it for Plex myself, but it might work.
  24. Go to the appdata share and look in Plex\Library\Application Support\Plex Media Server\Crash Reports You will find folders for your previous versions named as the release version.