Feb 27 12:02:08 MN-C02M508UF5YV osinstallersetupd: MiniSoftwareUpdate: Asset Caching Error when searching for URL : AssetCacheLocatorService: cancelled A solution, which I found, inspired by this discussion, was to add this line before adding jamfHelper and startosinstall: set -m This made jamfHelper and startosinstall totally independent of macOSUpgrade PID, and solved my problem! I`m really new to Mac OS Admin, and I had high hopes that startosinstall would make it easier for me to update my Mac remotely from 10.14.3 Mojave to 10.15.2 Catalina. But I apparently have the same problem as @krispayne and @beneb12: [STEP 1 of 4] Executing Policies Installation 10.13.3 High Sierra [STEP 2 of 4] Running the SS script: Install 10.13.3 – New… Script Release Code: 0 Script Result: Power Check: OK – AC Power DetectedDisk Check: OK – 85557624832 Bytes Free Space Detectedmkdir: /usr/local/jamfps: File existsLaunching jamfHelper as FullScreen… Startosinstall is launched… [STEP 3 out of 4] [STEP 4 out of 4] Who else has the same problem as @krispayne and has a solution? I see the same type of problem and messages in install.log for installer 10.14.1, but not the 10.14. Problem is independent of this script, because I get the same thing when I run the startosinstall command –erasedisk in the terminal. Then post a message to the user to get help repairing the disk before continuing. The troubleshooting process: could not get a licensing agreement is a simple process and I will explain it in a much simpler language than what other blogs and sites have explained. In addition, I will soon download a video tutorial that shows how the APFS conversion can be effectively avoided when installing macOS High Sierra or Mojave. p.s. found how to get, but I get „error: could not get the license agreement“ However, since we know startosinstall will stop if the disk can not be verified, could not run the diskutil command (or even fsck) that I mention in particular? However, many people who try to use this command ended in an error: no licensing agreement could be obtained (see screenshot above). That`s why we mentioned today in this manual a simpler way to prevent APFS conversion and avoid errors: no licensing agreement could occur when you run the command to avoid aPFS conversion.
@Hacksore – See how the startosinstall binary starts the process in /var/log/install.log? /Applications/Install-macOS-High-Sierra.app/Contents/Resources/startosinstall –converttoapfs NO @sdpalmer we can`t monitor. The script ends before the upgrade is actually completed, otherwise the startosinstall binary will try to restart while the script is still running, creating additional problems. We rely on the binary file to close the jamfHelper window as soon as it`s finished, so I think at this point it would be more of an Apple function that, if the binary fails, always indicates the killPID setting. Once the installation and configuration are complete, go to the system, system report and click Memory. It displays the HFS-Journaled score. This means that your attempt to avoid the aPFS conversion was successful and was dealt with without error: no licensing agreement could be obtained. I also see this problem with a copy of your script. I`m trying to go from 10.12.6 to 10.13.6.
Nothing appears in the installation.log that would be relevant. Once the process begins, it doesn`t seem like installation.log is even affected. The startosinstall process is in a „dormant“ state. If I manually execute the command as root from the terminal (local or via ssh), the executable start-osinstall file is simply hooked after I`ve given myself notification with the –agreetolicense and the option to end now if I don`t agree.