kc9wwh / macOSUpgrade

Workflow for doing in-place upgrades.
Other
420 stars 103 forks source link

Hangs on "Preparing..." screen for ever. Logs show "Preparing: 100+%" #175

Open Rorzzer opened 2 years ago

Rorzzer commented 2 years ago

All intel devices 10.14-11.3 attempting to update to update to Big Sur 11.4 are having issues with hanging on the preparing screen.

The startosinstall.log shows that it is infinitely "Preparing: 108.1%" etc, well beyond 100%

Logs attached. system (1).log startosinstall.log install (1).log

Screen Shot 2021-07-23 at 4 18 48 pm

jamf (1).log

Rorzzer commented 2 years ago

I've just updated my script to include "set -m" as suggested by @fponcelin

"I added it right at the start of the # APPLICATION section, just before ## Launch jamfHelper. I also added set +m at the very end of the script (before exit 0), although that might not be needed (I don't know for sure '^_^)."

I'll report results back soon hopefully!

Rorzzer commented 2 years ago

no change, devices still hang on the preparing screen forever. Tested with 16 MacBook Pro new out of the box macOS 11.3.1, enrolled then kicked off the update to 11.4.

Strangely though, if you press cmd+Q to exit the black screen then leave the device for 10 minutes it eventually restarts and completes the update... it seems to just be the "Preparing screen that causes the issue.

Logs: system 2.log startosinstall 2.log jamf 2.log install 2.log

tsinghzf commented 2 years ago

It goes through but m1, it fails. I haven't been able to get it to work. Any ideas as far scripting goes for the existing script tweaking?

Rorzzer commented 2 years ago

To confirm this issue is still present. Just tried a clean install from 11.6 to 12.0.1 and it hung on the installer screen for an hours, eventually I pressed Command+Q and had a look at startosintall.log.

Same as before, it reports Preparing #% over and over then runs past 100% It then continues to report "Preparing 105.6%" and on an on well past 100%

I've left devices overnight in the past and they will continue like this indefinitely.

Not sure what else to try, this is a pretty constant issue we are observing roughly 1/3 times.