I tried to replace my M3 Macbook Professional from Sonoma (14.7.1) to Sequoia (15.3.1) however the installer obtained caught someplace within the center—even after letting it run for greater than 24 hours. (As proven, only a black display with the Apple emblem plus progress bar roughly on the half-way mark.)
I pressured a power-off, then tried booting to see what state I used to be in. I obtained a login immediate however was not in a position to full the login course of. So I attempted to reboot into protected mode, which was profitable, and it reported I used to be working the up to date Sequoia (15.3.1). However since I couldn’t login with out protected mode, although, I had no alternative however to strive once more. I went to the App Retailer, downloaded the installer once more, and ran it once more.
Basically the identical factor occurred however was a lot additional alongside the progress bar, maybe 90% of the best way (however I positively take that with a grain of salt—progress bars are notoriously inaccurate).
I used to be on the lookout for different concepts to strive once more with out having to wipe the disk and begin contemporary; disabling FileVault, reset PRAM, and many others… however lo and behold I used to be in a position to login, and the machine claimed it was efficiently working Sequoia (15.3.1).
However what’s the true state of my machine? On the one hand, the installer didn’t end, so there was no cause I ought to anticipate I’ve a legitimate set up of Sequoia. However however, there are soooo many issues that must be right to have the ability to (a) login efficiently and (b) run all my common apps with none anomalies or obvious points (Slack, VSCode, Chrome, Vim, Joplin, Terminal, git, and many others…) And I’ve been utilizing the machine with out incident for a number of hours.
Checks I made:
- I rebooted into restoration mode and ran Disk Utility and checked the containers and volumes, which reported no points.
System Data >> Software program >> Installationsreviews the 2 set up makes an attempt on the backside (effectively, type of three objects reported ?!):
- Wanting on the set up log (/var/log/set up.log) not fairly positive what to search for, however I do see loads of occurrences of this:
Bundle Authoring: error working installation-check script: TypeError: null just isn't an object
(evaluating 'cpuFeatures.break up') at x-distribution:///installer-gui-scriptpercent5B1percent5D/installation-checkpercent5B1percent5D/@script
Are there another exams or checks I may/ought to run to validate the OS set up?