SuperW2

I was/am using custom network which I've always run my dockers on a unique network/VLAN segmented from my primary unraid host network. As soon as I moved the Gluetun docker back to "bridge" mode from my custom network, it then let me add the container port as expected...

Installed GluetunVPN (qmcgaw/gluetun) app from Community Application... have it configured and running and seems to be connecting to PIA as expected... Issue seems to be I am unable to add new ports for my existing dockers that I want to route through Gluetun. When adding a new port on the docker config, there is no input for "container port" so unable to access any of those dockers obviously.

It had been working perfectly without error for almost a year, and I created the pool initially with the same Truenas instance I'm not sure if likely related or not.

Have been running ZFS on my UNRaid now for most of this year with no issues. Completed update to 6.11.5 (had previously been applying all point releases fairly quickly after release)... After the last update I'm getting a PANIC at boot directly after "Starting Samba: on 4th line "/usr/sbin/winbindd -D". If I start Unraid in safe mode it boots just fine... I renamed the unRAID6-ZFS .PLG file and it boots normally as expected... Has anyone else run into any issues with the ZFS plugin and newer 6.11 versions of UnRaid? Any ideas? I completely removed the ZFS plugin and reinstalled and get the error messages in the live SysLog... I've imported my pool into a TRUENAS boot that I've used to add vdevs and it appears healthy and no issues that I can identity. Scrub completed normally. I also downgraded to previous 6.11 versions (I was running 6.11.4 before with no issue) and no change, same PANIC error. Any Ideas or anyone else with similar issues? SW2

Thanks...didn't help...now get the PANIC with either 6.11.3 or 6.11.5. I CAN boot into Safe Mode in both so maybe I had some type of hardware failure that just happened at the same time... unfortunantly almost zero info anywhere with the error i'm seeing.

Attempted upgrade from 6.11.4 to 6.11.5 and getting a PANIC and hang... no other changes to hardware or any recent hardware issues that I know about and have been upgrading at every point release... Guess I can try to downrev my USB Boot stick but not sure how to proceed and or troubleshoot since it never finishes a boot. This is occurring directly after "Starting Samba: on 4th line "/usr/sbin/winbindd -D" VERIFY3(size <= rt-›rt_space) failed (281442933186560 <= PANIC at range_tree.c:436 :range_tree_remove _impiO)

I see that PIA is "unsupported" and not recommended, but seems to be several folks that had previously made the converted PIA files via scripts from various GitHub projects... I've tried a couple of those converted CONF files with the new RC5 options without any luck. If anyone finds a way to make those work with the "VPN tunneled access for docker" option in RC5, I'd be all ears to hear how (even if not fully supported). I don't really want to switch to a new provider at the moment.

WOW!!! That's a lot of disks

I have the exact same issue with my server...

I think you need to click through the "macOS installer" (2nd icon from left) 3 or 4 more times before it finishes and the OS starts

Exact same on mine, first attempt yesterday, on 6.9RC1 - Completely removed everything, rebooted and getting the same thing on 2nd Try (attempting to install BigSur).

Far from an Expert... but are you passing through a Graphics ROM BIOS? I have a GTX1080 that I had setup to passthru to my Win10 VM. I installed the Card in a standalone Win10PC, downloaded the GPU BIOS ROM file with CPU-Z (following one of the processes in SIO Windows VM Videos), then reinstalled back into my unRAID server... I used that same GPU Rom file to the High Sierra VM... before I added the ROM to the VM Config, it wouldn't boot at all with NVidia Card added to Mac VM, once I added that, it booted and I was able to install the nVidia drivers per the SIO Video. Doubt that helps much, but the ROM file did it for me.

I'm going to make a backup copy of the entire VM and try to update again... I did confirm it was the iTunes/OS Security updates... not exactly sure how to update the Clover or kext, I'm just using whatever versions SIO included in the video links.

Thanks again for this great stuff... I re-setup my High Sierra VM with the new video and passed through my Nvidia card and everything was working good...then the OS did an update (iTunes, 10.13.6 security stuff, etc), which I think crashed the whole setup...when it went to reboot just had the circle with slash through it after the Clover boot screen. So I blew it all away and started over (didn't yet have any data). My question is what is everyone doing for system/os updates? Should I be able to do them (not upgrading to Mojave from the App Store) but anything else that Apple tries to push down. Should I disable all updates (which doesn't sound terribly "safe"). what is everyone else doing for OS/SW updates on the VM's? -Wade

Thanks for the update @1812, I have Mojave working now too... interestingly enough this is the exact settings/setup I was trying with High Sierra nd it was failing on the first reboot every time.