razmajazz

I've had 4 of the Rosewill cages for at least 5 years. I bought them because of the 120 mm fans and because they were cheap. No issues and still working well. I am careful with them because of all plastic construction, but they've held up fine. More than adequate for the few times a year when I remove the drives for cleaning or replacement. My case has a fan speed switch that I connected all 4 fans through and leave on low setting. It's pretty silent. At full speed the fans aren't really loud, but are audible in a quiet room. In my system, low speed keeps the drives sufficiently cool even during parity checks. My most recent drive purchase (Toshiba) did not sit flush in the drive tray. There are guides on the tray for which there was no corresponding opening in the drive. I just cut off the guide nubbin (an advantage of plastic construction 🙂) that was in the way and all is well. These sit behind a case door in my setup. They're not particularly aesthetically pleasing so if they were always visible I might have gone for a nicer looking cage.

Absolutely awesome! and very cool 🆒

Still rocking the Lian Li Lancool K12

I had similar errors after the upgrade to 1.15.0.659. Any playback requiring transcoding (even if just remuxing to a new container), either did not play at all (browser interface) or gave the trancoder crashed message (PMP). Any media which could direct play worked fine. Even remote users could stream if the media could be direct played, but if any transcoding or remuxing was required it didn't work. I have 2 instances of PMS running on Unraid (1 exclusively for home use) and interestingly the other instance worked fine after the upgrade for all media and all players. Before downgrading the unworking instance to the previous version of PMS, but I compared the PMS settings for both server instances. The only major difference I found was the instance that worked well had Enable HTTP Pipelining checked. After checking this in the broken instance and restarting PMS, everything is working again.

As with video, Plex excels at audio sharing and remote streaming. That's the main reason I use it. If you only want an in home music system just use SMB and your favorite audio program (Foobar2000!). The tagging functionality has made great progress in the past year, but fortunately you can instruct Plex to preferably use your embedded tags. My entire collection is in FLAC. Lossless playback happens automatically if the client supports it. Gapless playback is, unfortunately, not well supported. A few clients seem to do well enough, but not all. The main weakness of using Plex as an audio server is that it was developed for video. Plex has limitations that a pure audio server doesn't have. If music is your passion, you may find those limitations too much to overcome and in that case you'll be better off using Subsonic, Ampache or similar. On the other hand, if you just want something that plays music whenever and wherever you are, Plex is a fine choice.

Since Plex Home Theater has been discontinued, OpenPHT was started by the developers of RasPlex, for those that prefer the original PHT interface over the new Plex Media Player. The embedded version of OpenPHT uses a newer version of OE as a backend. The next version will supposedly merge code from RasPlex so development of OpenPHT and RasPlex will proceed concurrently. https://github.com/RasPlex/OpenPHT/releases

I wish it was that easy. Unfortunately, Plex uses a fixed port of 32400 internally no matter how you set the ports in Docker. In my experience each PMS instance requires a different IP address. There is a Pipework Docker which should be able to give a different IP address to another Docker, but I couldn't make it work with Plex. I ended up creating a VM for a second Plex server. If anyone figures out how to create 2 simultaneous instances of Plex using Dockers, I would love to hear how they did it.

Absolutely right if the VM will only be used for streaming. I assumed the VM would used create the stream (i.e. a Steam machine).

Unless you have a particular reason to change them, the defaults loaded with a Docker template usually work well. Changing the volume mappings may be required depending on your particular server configuration and use for the Docker. Tonido doesn't require port forwarding. You make an account at tonidoid.com and use that address to access your docker.

Short answer, no, there is no way to run 2 Plex Media Servers using Dockers. Plex Media Server uses port 32400 internally and it is not configurable. Two PMS Dockers will appear to run but even if you map 32400 to a different port in each Docker, it will only be an external port mapping and the internal port mapping will not allow you to access the servers independently. The only way around this limitation is for each PMS instance to have a different IP address so it will have exclusive access to port 32400. Unfortunately, all unRAID Dockers have the same IP address. Fortunately there is an easy workaround. I also run 2 Plex Media Server instances so I setup a Linux VM (I used Mint but most distros will work) for the 2nd PMS. The VM has it's own IP address and it's own exclusive access to port 32400. I'd prefer to run Dockers for both servers, but one PMS Docker and one PMS VM has worked well for me for quite some time. Another option for you to consider is Plex Home. In theory, you could run a single server and use Plex Home settings to fine tune access for any particular user. Since my 2 PMS solution is working fine, I haven't switched over, but administering a single server has advantages.

This app is working great for me except for one issue. When I try to download a whole directory the download fails immediately. I believe Tonido tries to zip the folder and fails at that point. Any help appreciated.

I had similar issues and switched to Tonido (http://lime-technology.com/forum/index.php?topic=39065.0). Not as many features as ownCloud, but all the ones I need and easier to setup/use.

I followed this procedure as well to move from Linux VM to Docker. Key point is to disable automatic Trash emptying in your current Plex installation before copying that installation's database. This ensures the database is preserved while you update the location references in the Library of the docker installation. Additionally, verify ownership for the library after copying. I needed to execute chown to match the ownership expected by Plex docker since it was different than the owner of my Linux VM installation of Plex.

Or this November buy a $50 Steam Link and play on your TV... http://store.steampowered.com/app/353380

Seconded. OpenELEC installation instructions: http://kodi.wiki/view/Chromebox

KVM has been the default for virtualization for quite some time. Initially Tom chose Xen for virtualization (early 6.0 betas). That decision was changed after a few beta releases in favor of KVM. As I recall, the primary reason provided is passthrough, in particular video passthrough, is more reliable. For those with working Xen VMs from the early betas, Tom continues to support Xen as a boot option. For those without legacy Xen VMs, KVM is the recommended virtualization engine to use.

You could create a Windows VM on the unRAID server and pass through your video card. Install Steam on the VM and use Steam In-Home Streaming to play games on any computer in the house http://store.steampowered.com/streaming/. This is supposed to work even for non-Steam purchased games.

Not using cache drive. appdata is on a SSD mounted outside of the array. Running PMS, Crashplan, nzbget, sonarr, couchpotato, btsync 9GB used, with the PMS database taking most of the space 10GB docker image, 3 VMs and temporary storage for downloads are on the same drive but not in appdata

The default owner in needo's docker is 999:users. When I migrated my library, changing the permissions to match the default solved my problems. Maybe it will work for you too.

Another inexpensive choice for OE is a re-purposed Chromebox. I don't have personal experience yet but the reports are pretty positive. http://kodi.wiki/view/Chromebox#Device_Preparation OEPlex can be installed if you're a Plex user. https://forums.plex.tv/index.php/topic/88788-oe-install-and-package-status-thread/ https://forums.plex.tv/index.php/topic/130238-asus-chromebox-perfect/

I had the same issue trying to run 2 Plex dockers. Inexplicably Plex hard codes port 32400 so a separate IP address is required for outside connectivity. There is a solution in Pipework, but it was too complicated for me to set up. According to this article other options may be in progress but aren't ready for prime time. The easy solution for me was to run the second Plex server in a VM.

I recently had a very similar occurrence with parity drive (ST4000D) throwing off a huge number of read errors, but no sync errors during parity check. I replaced the drive and ran multiple preclear cycles on it. Although pending sectors decreased with each preclear cycle, they never went to zero. Reallocated sector count continued to increase. After the preclear cycles I ran a full badblock cycle, expecting to find a lot of problems, but interestingly, it found no errors at all. Like you, I'm not sure if the drive was really bad, but since it was still under warranty, I decided to RMA it.

I prefer Foobar2000 (http://www.foobar2000.org/) with the Masstagger plug-in (http://www.foobar2000.org/components/view/foo_masstag). It's Windows only. Foobar is a Swiss army knife of functionality (player, tagger, organizer, converter, etc.). It works well for everything except embedded album art. For that I prefer mp3tag mentioned earlier.

I haven't found a downside. I switched all my Linux and Windows VMs to vmvga and have not had any issues. Besides the increase in supported resolution settings, vmvga solved some annoying issues with transparency and toolbar flickering in my Linux VMs (maybe that's the same issue you had with your mythbuntu VM). I was actually going suggest that you change from cirrus as the default for new VMs created by your plugin.