mr-hexen

Lan range is set in the docker edit window in the unraid webgui.

You'd need a current (Kaby Lake) or past (Skylake) i5 processor at least. That's pretty much your whole $300 budget right there.

I have 5 data + 2 parity + 2 cache in my Q25 with an eSATA port out the back for whatever. I've used my PCIe slot for a GPU (Plex Media Player VM), so I'm stuck at 6 SATA ports.

This statement of course begs a comment that "a 2nd copy on the same system is NOT a backup !!" ... however, you clearly understand that, based on your follow-up comment: ... and it is true, of course, that having a 2nd copy on a different disk helps reduce the likelihood of data loss on the UnRAID server. Do you have dual parity on that server? (That would actually be better protection than a 2nd copy of the data -- although you could of course do both) 3 data drives + 1 parity currently (+ 1 cache disk). Dont think I'll be going to dual parity as its not worth the investment and my Q25 would then be out of SATA ports....

I do this only for a few shares that I KNOW will not be large (i.e. pictures and documents). I restrict them to a specific disk so that I can create a backup share (i.e. pictures_backup) on a different disk and rsync the contents weekly. This gives me a pseudo hot backup. Obviously they are backed up off system as well.

Not really.. I have them set up as separate myself. Some of the shares will need to be spanned due to size (i.e. movies, tv shows, music), but others can live on a single disk, which is how I have things setup.

Front panel connectors shorting?

Have you tried force flashing the BIOS as described here: https://forums.servethehome.com/index.php?threads/x9dr7-ln4f-boot-hang.6133/

Are you sure about that? I thought they reverted to manual weekly builds. Still better than LT which doesn't have a defined update schedule. Just tested it myself. I was still on 1.3.4, restarted the docker and am now on 1.4.1

The linuxserver.io plex docker updates to latest upon restarting the docker, unlike the LT docker which needs to be rebuilt.

Yes I get that, but not both screens at once, you'd have to switch back and forth. Meaning you can't use both machines simultaneously.

Pass through the hardware to the primary VM, and run the second headless VM full screen in an RDP session on the second monitor. While that would work for display, it won't for input (i.e. keyboard / mouse)...right (or am I missing something)?

Because that's what the AUTO setting set it to. If you want to pump it up to mem spec you'll have to do it manually, but i wouldnt bother as you're likely to sacrifice stability for 0.001% faster memory access.

Just look four posts up, or click here: https://lime-technology.com/forum/index.php?topic=42149.msg537330#msg537330

Did you add the right port? Do you have the VPN turned on? Did you set the Lange_range variable properly? I've got siphon working just fine with delugeVPN.

Or one of these:

Read the log, pay attention to the line starting with [crit] Sent from my SM-G900F using Tapatalk

I ran into this when I downgraded from 6.3.0 back to 6.2.4. To resolve do the following: 1. Stop docker (even if it's stopped, you want the webgui to show it as disabled too). 2. Delete your docker.img. 3. Reboot machine. 4. Enable dockers 5. Re-install your dockers, look for the my-* templates to retain all settings.

I've seen both. But if you get molex -> SATA splitters or adapters make sure to get the crimped style, not the molded style....here's why: https://www.technibble.com/forums/threads/fire-hazard-molex-to-sata-power-adaptor.70322/

Take your usb to a windows system and run a file system check. Maybe its corrupt and is why the webgui update wouldnt work.

I see where you're coming from now. You should know that core / transcode isn't the best way to determine CPU requirements.. Plex has always recommended 2,000 passmarks per 1080p transcode. 2,000 passmarks does not translate into a single core. If the OP could use the handbrake docker instead, then all CPU horsepower is available to all process whenever its needed. An i7 would do nicely in this situation.

Also, the only VM you have planned can actually be run via docker, as there is a handbrake docker already. @ashman, 8 cores for what exactly? I dont follow your logic here?

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. My guess is the docker version in 6.3.x upgrades the IMG file in some way and it becomes incompatible with earlier versions of docker, so when we revert back to 6.2.4 it doesn't work. Still confused as to why a reboot is required to get it going, even if the docker.img is deleted... above my head though.

Can do Jon... any idea how I can get Dockers back on 6.2.4? EDIT: Fixed it. If anyone else runs into this issue I had to 'stop' docker, delete the image, reboot, re-start docker and it's showing running again.

Rolled back to 6.2.4 and VM performance via VNC has returned to normal. Definately something up with 6.3.0 and VNC. EDIT: Dockers won't work at all now. Docker service is enabled, says "stopped", Disable/enable does nothing. Reboot doesnt fix it either. Tried deleting docker image, nothing.