drumking53

This totally worked for me!!! by changing the XML, it booted right away to the install screen. Thank you so much!

So I was able to: 1. change the "disk.cfg" file from the usb boot drive and changed the "startArray="no"" to "startArray="yes"" 2. then I was able to ssh and remotely start my docker containers. Everything seems to be running as it use to. However, I still cannot access the GUI.

Thank you @trurl Here are two files. one before shutting down (I believe - 0347.zip) that I found and the other after the shutdown (2017.zip). yianni-diagnostics-20220121-0347.zip yianni-diagnostics-20220121-2017.zip

I am currently having the same issue. I see a bunch of files listed but still am unable to get into the GUI. Any thoughts?

Hello all, I understand that there are many posts about not accessing GUI, but none of the fixes have helped me. Background Info: - I had noticed a few days ago that I could not log into the GUI, it seemed that everything else, dockers and vms and smb were working. - I chose to reboot because I needed to access GUI for Sonar/radar downloads. - When I rebooted I used the powerdown -r command. It restarted no problem but then the array was not started. - I still couldn't access GUI... - I rebooted manually at this point....still no GUI, but can still access via ssh. Currently: - I have reformatted the flash drive a few months ago and do not want to do it again if it is even the issue. (don't know if it is or not) - I know logs will be asked for, I do not know which exactly nor the proper command. - I have attached a syslog to begin with. - I am able to run the diagnostics command and it created a file. How do I access this via command line and download via terminal? (although this was run after the reboot) I would greatly appreciate any help to avoid loosing any configuration or information. Thank you syslog.docx

Hey all! I also have encountered this email. I do not know why and what this could mean. Any help would be greatly appreciated. yianni-diagnostics-20211021-1926.zip

Hello All, Ive also received this error: Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the unRaid forums. The output of mcelog (if installed) has been logged. Ive uploaded both methods of obtaining logs below. I don't know what I would be looking for. Any help would be appreciated syslog yianni-diagnostics-20211010-0708.zip

Yes as you can see here: # vm name (put the name of the vm as defined in your template) NAME="Macinabox BigSur" Ive also attached the helper script for your input and review. Much appreciated. I don't believe anything else needs to be edited. I also added the Macinabox_Big Sur.log macinabox_helper_userscript.sh macinabox_Big Sur.log

@ghost82. I attempted to start from scratch yet still receive the same error..... I am currently at a loss. Script location: /tmp/user.scripts/tmpScripts/1_macinabox_helper/script Note that closing this window will abort the execution of this script Starting to Fix XML error: failed to get domain 'put the name of the vm here' No network adapters in xml to change. Network adapter is already vmxnet3 Added custom qemu:args for macOS topolgy line left as is custom ovmf added error: Failed to define domain from /tmp/put the name of the vm herefixed.xml error: (domain_definition):3: Extra content at the end of the document ^ This is what has been done to the xml Your network type was already correct. Network has not been changed. The custom qemu:args have been added to you xml. VM is set to use custom ovmf files. xml is now fixed. Now goto your vm tab and run the VM Rerun this script if you make any other changes to the macOS VM using the Unraid VM manger macinabox_helper_userscript.sh

@ghost82 you mean like this? I apologize for the n00b questions, but this forum has been very helpful with the new guys. macinabox_helper_userscript.sh

So I ran it again and it ran very quickly. Here is the download log: log-2.txt also here is the log from Macinabox docker macinabox.rtf

I did run each script and have been following the tutorial. Should I run each script again? Ive also tried each download method and the same issue occurs. Ill try again....

Thank you Spaceinvader for providing this content and all the content you create. I am stuck when running the "1_macinabox_helper" script. I continuously receive the same error: "failed to get domain 'put the name of the vm here'" and when I go to VMs tab, there is no VM. Below is the script from the helper: Script location: /tmp/user.scripts/tmpScripts/1_macinabox_helper/script Note that closing this window will abort the execution of this script Starting to Fix XML error: failed to get domain 'put the name of the vm here' No network adapters in xml to change. Network adapter is already vmxnet3 Added custom qemu:args for macOS topolgy line left as is custom ovmf added error: Failed to define domain from /tmp/put the name of the vm herefixed.xml error: (domain_definition):3: Extra content at the end of the document ^ This is what has been done to the xml Your network type was already correct. Network has not been changed. The custom qemu:args have been added to you xml. VM is set to use custom ovmf files. xml is now fixed. Now goto your vm tab and run the VM Rerun this script if you make any other changes to the macOS VM using the Unraid VM manger Attached is my Macinabox BigSur_original.xml file. I would greatly appreciate any and all help here to get this up and running. Macinabox BigSur_original.xml