SuperW2

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).

Thanks so much for all that the LinuxServer.Io team does... just got this working on 6.7.0-rc5 with my new 1660 ti and also tested with the Decode patch/script... all appear to be working as expected! Sent a couple chits for donation...will add some more when I get more in my PayPal account! -Sw2

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.

Well, it boots once at least, which I guess is something... I get as far as installing Clover on the macOS shutting down the VM and restarting (@ About 17:30 in the video where you remove the Boot IMG from the XML) and can never get it to reboot again. Just get a static Apple Logo on the VNC Window and nothing ever happens after...maybe I'll just wait to see if SIO does an update for the new OS. -SW2

OK, I deleted and redownloaded everything (including re-downloading the MacOS High Sierra Installer), new USB Stick, re-downloaded Clover 2.4K r4674, and it's actually booting now and beginning the install process. So it's not totally complete yet but a lot further along. I am using Q35-3.0 so far.

Regardless of how I've configured my VM, it isn't booting to the initial boot (I never see the Apple or Clover Screen) so it seems that it's not even recognizing the Primary VDisk boot IMG file made from the Boot USB (which I've recreated several times on multiple USB Sticks). I guess I don't understand where Clover is even involved as there is no mention of it at all through the first 9 minutes of the video (where SIO boots the VM and gets the clover boot screen). It feels like I'm missing something or should have watched another video to do other things to prepare for this one.

Thanks... I did try to use the Q35-2.9 as shown in the video. There is zero mention of any Clover versions in the updated video what-so-ever (at least up to the halfway point where I couldn't get anything to boot), so I'm not sure how or where I can I have any control over that. I also have zero clue where to find a older 10.13.0 macOS installer, so I guess I'll just shelve this for other endeavours. Sig was super old, forgot to update as I've gone through several HW iterations since last updated.

I created the USB Boot with 10.13.6 Macbook and I'm not sure what SIO is or what version of Clover...Following the SpaceInvader One Updated Video with the "unpatched" Clover. Created the IMG from the USB, Created the VM, Edited the XML with the parts from the vm-ackintosh text file, boot VM and can't get anything other than "UEFI Interactive Shell v2.2" screen in the VNC.

Has anyone successfully completed a new setup of High Sierra following this vid with UnRaid 6.6? I wonder if something has changed. I've followed this thing to the letter and booting the VM (after making all the XML updates) will ONLY boot into the UEFI Interactive Shell... never ever see the Clover Boot Manager

Yah that seemed to work after several start/stops and waiting some time after re-starting... I'll just try to keep it running from now on! Thanks!

Updated the other day (maybe a couple weeks ago, whever the last update happened) now cannot start the Handbrake Docker... it had previously been working fine... sparklyballs/handbrake:latest Here is Log error. Fatal server error: Server is already active for display 1 If this server is no longer running, remove /tmp/.X1-lock and start again. Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start. Both had been working flawlessly since install... Binhex Deluge also update, but it still seems to start OK... Here is SAB log file 2016-02-21 19:54:59,397 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-21 19:54:59,397 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-21 19:54:59,397 INFO exited: sabnzbd (exit status 2; not expected) 2016-02-21 19:54:59,398 DEBG received SIGCLD indicating a child quit 2016-02-21 19:55:02,402 INFO spawned: 'sabnzbd' with pid 27 2016-02-21 19:55:02,594 DEBG 'sabnzbd' stdout output: Error: Can't write to logfile 2016-02-21 19:55:02,609 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-21 19:55:02,610 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-21 19:55:02,610 INFO exited: sabnzbd (exit status 2; not expected) 2016-02-21 19:55:02,610 DEBG received SIGCLD indicating a child quit 2016-02-21 19:55:03,611 INFO gave up: sabnzbd entered FATAL state, too many start retries too quickly

OK, I found a Radeon HD5570 (which is probably a little older than the 560ti still), but re-created the VM with the new GPU, then seeing the video passthrough to the connected monitor. I still had to click next for all of the default settings with the USB Keyboard on the server before the Kore would connect, but once I did, Kore on my Android tablet then saw the server and connected as I expected it too and am now browsing and adding my shares. Sorry for blowing up your Template support thread! Thanks for your help and patience!

Most certainly sure, yes... have no issues connecting to my Plex Docker on my Media server from the same Android device(s) and my unRAID console via the browser, etc, I just removed the entire new VM, re-setup everything and no change, doesn't even appear to be getting an IP Address now from my Router, so I think time to call it a night and look at it again in the morning. -W I bet it's your default network bridge. Goto settings -> network settings and see if the network bridge is enabled. If not, stop the array and enable it. Once enabled, go to Settings -> VM Manager and make sure that the default bridge is set to br0 and not virbr0. Remove the existing OpenELEC from the VMs tab, then add a new OpenELEC VM and it will have this new bridge enabled by default. This will ensure you VM gets an IP on the network and is accessible by the Kore app. I'm been using a "br1" (which is what I changed the bridge name too in my network settings) bridge that I setup previously when playing with Win10 VM, not using virbr0. It's getting a 192.168.1.xx IP address from my router that I can ping and see on my primary network just fine. This might be a dumb question, but If I physically plug a monitor into the GPU should I be seeing "something" on that monitor when the VM is running? I'm getting absolutely nothing... Yes you should. If you have nothing on the display, that means your not successfully assigning the GPU yet. There are steps in the wiki relating to GPU pass through that you can try. I know we have had issues with the GTX 550 in the past, so the 560 may share a similar fate. It is a rather older GPU. Some things you can try are in the wiki though. If you have another GPU laying around, I'd give that a shot. I think this was the least old of the old GPU's that I had in my "surplus" box but I will try one of the others.