Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Big Sur downloads Catalina #33

Closed
flexage opened this issue Dec 27, 2020 · 6 comments
Closed

Big Sur downloads Catalina #33

flexage opened this issue Dec 27, 2020 · 6 comments

Comments

@flexage
Copy link

flexage commented Dec 27, 2020

When selecting Big Sur as the Mac OS version to install, and leaving the download method as Method 1, the installer for Catalina is downloaded.

The Macinabox docker image in use is the latest, perhaps the Big Sur product ID has changed or something?

Download Method 2 just failed to do anything for me.

@flexage
Copy link
Author

flexage commented Dec 27, 2020

OK, got method 2 working by deleting the macinabox appdata, vm, and downloaded iso's.

Method 2 downloaded the correct version.

Tried method 1 twice and it downloaded Catalina both times.

@jack60612
Copy link

Happened to me too

@ParadoxEpoch
Copy link

Fixed in PR #37.
fetch.sh wasn't passing arguments onto fetch_macos.py when method 1 and Big Sur were selected.

@gloubix
Copy link

gloubix commented Mar 15, 2021

OK, got method 2 working by deleting the macinabox appdata, vm, and downloaded iso's.

Method 2 downloaded the correct version.

Tried method 1 twice and it downloaded Catalina both times.

How did you delete the VM , i have this message ->

Requested operation is not valid: cannot undefine domain with nvram

@Cilusse
Copy link

Cilusse commented Mar 15, 2021

How did you delete the VM , i have this message ->

Requested operation is not valid: cannot undefine domain with nvram

You need to edit the VM in expert mode, and delete the line that defines the nvram location.
something I think. It should be near the top third of the file.

@bpelech
Copy link

bpelech commented Mar 27, 2021

For everyone who ended up with Catalina instead of Big Sur, here's what I was able to gather and do to fix this issue:

  1. Use method 2 as explained in the video from SpaceInvader (because this method expects downloading "InstallAssistant.pkg" which needs to be extracted).
  2. Start Macinabox
  3. Open console - click on Macinabox docker icon and then Console.
  4. Install nano (or vim) - apk add nano
  5. Edit unraid.sh - nano /Macinabox/unraid.sh. Find and replace 001-86606 to 071-05432 (this is correct big sur ID)
  6. Restart Macinabox
  7. Follow the SpaceInvader video

Additional troubleshooting:

  • If you were too slow and wrong image was already downloaded while you were editing the unraid.sh no worries. Just delete the files ("BigSur-install.img" and "BigSur-opencore.img") from isos folder and restart Macinabox. It will download the correct files again.
  • If you messed up somehow with the VM: delete the VM, restart the Macinabox and run the "1_macinabox_helper" user script again.
  • If you can't delete the VM (I saw this error once "Requested operation is not valid: cannot delete inactive domain with nvram"), run this command from shell virsh undefine --nvram "Macinabox BigSur". You can open the shell with the >_ icon from the right top corner.

Hope SpaceInvader will be able to find the time to fix the Macinabox. Until then - stay with catalina or try this fix.

If SpaceInvader will read this post: HUGE THANK YOU for this tool and all your work. You rock man! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants