zleef

Thanks @ljm42, that fixed it!!! - i restored /boot to its previous state, and restarted to confirm the original issue was present at startup (it was). - i updated /boot/config/domain.cfg per comment from @ljm42 and restarted. I didn't have any isos in /mnt/user/isos, so i left the VIRTIOISO blank.

Quick update - i followed @johnnie.black advice: I backed up the /boot drive, deleted everything from it, downloaded the latest unRAID server: https://lime-technology.com/download/, and then copied over my key and super.dat file from my backup (/boot/config/super.dat and /boot/config/Basic.key). Upon restart, the array started up successfully! However (obviously), now i have none of my dockers or other system configuration. I'll spend a little time seeing if i can add back config slowly enough to find the culprit.

Thanks for taking a look. I re-installed and opened in private browsing as well as in a different browser. Still the same issue.

Sure thing. I downloaded the diagnostics after initially running into issues. I believe this was prior to disabling docker or plugins though (this might have been on the second restart?). I didn't expect such a quick response, so i've already reverted back to 6.3.5. If you want me to try something or get a new log, I'm happy to go back to 6.4.0. tower-diagnostics-20180119-0957.zip

I did try that, nothing different happened. I was able to use the new terminal/console feature to view the syslog, but the "Log" display popup (from the nav bar) never loaded. Although i did find at one point i could view the syslog through the ui from the Tools -> Syslog page.

Same for me. I disabled all plugins and docker. Tried following all relevant steps from the "6.4.0 Stable Release - Update Notes". My server is still stuck in "service starting".