phbigred

Could also be their metadata for your library is causing the ballooning. Also one thing I do is lower the logging level using extra parameters in the docker. --log-opt max-size=50m --log-opt max-file=1 Put the setting in and rebuild your docker image and it should help if it's a logging balloon.

Assuming you mean "plex" media server. Try searching in Community apps for that.

If you "care" about the data you are loading consider a parity drive. Gridrunner put together the basics of what unraid is and how it works. Apple iMacs are able to talk to unraid fine. For what the hopper can see I don't know what app it uses unless it's a upnp server share. It might be worth considering a roku stick too. Plex and kodi both can run docker containers.

Same steps I've used with bouncing between RC and 6.2.4 took some trial and error and I even included an extra reboot at the end.

Think the only way to get that through would to be to do a pass through. Gridrunner has a good video on passing through an individual USB port through to a VM. Look under the KVM section it's one of the top tagged ones.

Delete the image under setting docker advanced. Reboot, recreate docker image, reboot. Should fix the docker service. I had to do this a couple of times bouncing between 6.2.4 and 6.3.

So far so good with 6.3 had an issue with rc6 but upgrade went normal and yet to have a lockup like I did on that rc.

Dumb question have you made sure the IP of the devices with DHCP are in the same range as the static IP device. Let's say you had 192.168.0.X for the original router and your new one uses 192.168.1.X. DHCP devices would continue to work but static would not. Have you also tested pinging from one of the DHCP devices to your server and see if you get a response?

Set the vm to 1 core and try to boot up again. Could be an issue with updates possibly trying to run at the same time.

If you are running a recent version Community Apps does have a backup feature and "previous apps" for recovery in the case of rebuilding your docker image. If you have a "docker" tab at top that means your service is properly running. Recreate your docker image and do a restore with CA. (Assuming you are using it)

Lookup community applications plugin by Squid. The capabilities are pretty awesome for backup/recovery of CA plugins. You can delete your docker image and rebuild your servers in minutes.

Agree with Turl, plex alone can eat 4GB. You'll be much happier with 8.

Assuming that your share is set to cache "yes"? If so assuming your cache isn't full it should be transferring at 70-80MB/s easily likely higher.

This isn't true with the LSIO docker. You can set it to latest and it will pull the newest version every time you restart it. No need for an update to the docker image. You can also specify a specific version number (which is what is required to use beta versions of Plex, i.e. the Plex DVR Beta releases). I strongly recommend running Plex in a docker container. Once you understand how docker volume mappings work (it's really simple once the light bulb clicks on), then it is very easy to install and run docker containers. Agree with above. I converted nearly 2 years ago, wouldn't go back!

So hdhomerun DVR uses the hdhomerun tuners by silicondust. Network based tuners. Silicondust.com is the site with info.

I'm personally loving the hdhomerun DVR. $60 works with cable card and OTA but no DRM as of current. Have the engine running in a docker container available in CA. Part of the $60 is 1 year of guide ($35 I think) and early access. The DVR is supposed to go release candidate soon for non-DRM affected folks. Thus meaning the clock on the 1 year begins. I manage the PVR through Xbox 1, Windows 10, kodi, etc.

Hasn't happen since downgrading to 6.2.4. Grins and chuckles I swapped the servers ram completely. So it's very possible it was RAM before downgrading. Was hoping for a blaring red flag but your thoughts may have confirmed my suspicion. Thanks Squid, btw love your plugins!

Anyone have an idea other than the CA.backup app? I downgraded to 6.2.4 hoping for more stability but would like to bump back up.

Just doing a bump...

Got ca.backup updated, so that's fixed...

https://www.dropbox.com/s/4e58coregfznn0u/unraid-box-diagnostics-20170110-0313.zip?dl=0

I was running troubleshooting mode due to issues in the past week, issue is a hard freeze of the OS, system is pingable only. All dockers, vms, and WebUI goes "dead". Unfortunately the diag at time of crash is 340KB. Recommendations on getting it uploaded for review by people smarter than I?

Common problem http://lime-technology.com/forum/index.php?topic=43644.msg464975#msg464975 This video does a walk through.

Was able to pass through another 2.0 controller on my board. Reading other threads may be directly linked to VIA controller issues.

Running into a similar issue. I'm stuck at TianoCore and VM is unresponsive. I tried both through the flash and manually in the XML, separate tests not at same time. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </source> </hostdev> I've attached diagnostics for those smarter than me, and a screenshot of my VM from VNC unraid-box-diagnostics-20161230-1939.zip