![]() ![]() Thank you again for all you do for our community. Went over to user scripts and ran the notify and it was ready almost instantaneously. This time I edited the appdata path to read /mnt/user/appdata/macinabox instead of the /mnt/user/system/macinabox that my server defaulted to. I deleted the docker, system/macinabox, appdata/macinabox, docker template, and re-did the whole process. Not sure which is easier but I think either way I will delete all and totally redo to ensure a clean install. OR should I switch the first directory to: Macinabox only data: /mnt/user/system/macinabox/macinaboxīasesystem: /mnt/user/system/macinabox/basesystem I believe the three directories outlined in my red annotation should read as follows:Īppdata (leave as is) /mnt/user/system/macinabox It looks like at some point I changed my Docker default appdata location to /mnt/system ? Not sure why I would have done this - but when I started learning Unraid a few years ago I definitely had some beginner mistakes and maybe this is a leftover error that I've just noticed now. Here is a screenshot of /mnt/user/system/macinabox : I checked the appdata folder and this is what I've found: (the parent folder of this screenshot is /mnt/user/appdata) ![]() But you would also need to change the location in the helper script aswell in the installvm function part of that script as it also references the appdata there too when the vm is first installed So you could change the script with the location of your appdata. ![]() ie ( /mnt/user/appdata/ ) the script then will not see the folder as it uses the direct path. Your appdata is not in the default unraid location. With manaul install this folder and xml is not created.Ģ. Manual install was selected and not auto install. There may be 2 cases which happen why the notification script would not show this to be done.ġ. This is created after the install media has been converted from dmg to img and moved into the iso share. usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Macinabox" -d "macOS now ready to install (now run helper script)" -i "normal" Sleep 5 #wait 5 seconds before rechecking # script to notify on Unraid server when Macinabox has finished downloading install media This folder is made and contains the xml to define the vm. What the script does is check if a folder called autoinstall had been made in the macinabox appdata. Not sure if anyone has any input but I will let this run for a few more hours just in case. I checked the isos folder and there are two files: (Note GiB, not GB as reported by Krusader) I'm not sure how big the file(s) are or where they are downloading on my server. I've had the script running in the background for about 45 minutes without any notice that macOS is now ready to install. I'm on a 1Gbps WAN connection so its theoretically possible that it completed the download before I began the script. The reason I ask is because it took me several minutes to get the user script running after I started the docker. OR will no notification appear since the downloading was not in progress when I began the userscript? IF the BigSur download is completed before I run this script:ĭoes the script show a notification that "macOS is now ready to install" ? Question regarding the macinabox_vmready_notify script: ![]()
0 Comments
Leave a Reply. |