-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
Error Update 10.14 or 11.x from 10.13.6 #169
Comments
@bertocea85
You can't have spaces in However, the output says that you ran (I don't think this is causing the error, but please try anyway). To test this I would need to get a hold of a 10.13.6 client that can be upgraded. That might take a while. |
sorry!! |
Again, please choose either os or version, not both. --os=10.14 or --version=10.14.6 should actually do the same thing, since 10.14.6 is the latest available version of macOS 10.14. |
Hello! I have tried both with only the OS and with the version and the same error |
Hey Graham, I just stumbled across this as well. Attempting to go from 10.13.6 to 10.15.7 using the following with v25: Logs indicate the built-in installinstallmacos.py is only returning the following available options: However, if I run installinstallmacos.py manually (pulled from v25 pkg) I see all available macOS versions up to and including Monterey. Also tried this which resulted in the same issue: Here's the full tail end of the log: [run_installinstallmacos] Checking that selected OS 10.15 is available This Mac: Board ID : Mac-B4831CEBD52A0C4C ProductID Version Build Post Date Title [erase-install] 'caffeinate' ended |
Graham, I think I found the bug. I believe installinstallmacos.py is stumbling over Apple's default sucatalog for Darwin 17 (High Sierra)... Take a look at the manual run below. The version number for the 2019-10-22 macOS High Sierra is missing, and according to the erase-install log, basically where it gives up looking for a valid installer (if sorting by Post Date). Board ID : Mac-B4831CEBD52A0C4C
If I force the latest catalog like so, I have no trouble. Thanks so much for your amazing work by the way!!!!! -JonW /Library/Management/erase-install/erase-install.sh --reinstall --check-power --update --current-user --depnotify --os=10.15 --catalogurl=https://swscan.apple.com/content/catalogs/others/index-12-10.16-10.15-10.14-10.13-10.12-10.11-10.10-10.9-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog |
Nice, I was wondering if that might be the case, but still don't have access to a 10.13.6 Mac that I could upgrade. I'm on vacation this week but starting to think about testing the latest catalog regardless of which OS is running. That breaks the convention in installinstallmacos.py, but might solve a few problems (or cause some - hence the need to test!). |
hi @grahampugh. |
@bertocea85 yes, I created a pre-release version that uses the latest catalog for every OS. But, it is also causing problems for people running Big Sur, because Apple are not consistent about which catalog contains which versions. Under that regime, it's impossible to guarantee that either method is correct. I'm considering just making it easier to select which catalog you want to override to. So, instead of having to add |
I've fixed this bug in v26.0. It was occurring because there is missing information in the 10.13 catalog (an empty version string in one of the listings - see #5 below)
|
Describe the bug
hello!
When we try to upgrade from 10.13.6 with the following command, erase-install.sh --os = 11 --force-curl --update --reinstall --confirm --depnotify, BigSur does not appear in the list of available versions. on the other hand, if I try to update from 10.13.3 to 10.14.6, which if it appears in the list, several errors appear and no image is downloaded.
Attached log
To Reproduce
erase-install.sh --os = 11 --force-curl --update --reinstall --confirm --depnotify
ships with a JAMF policy, posted on SelfService
Expected behavior
A clear and concise description of what you expected to happen.
Code/log output
Log to update 11
The text was updated successfully, but these errors were encountered: