Now select Disk Utility -> Quit then Utilities -> TerminalĤ. First, pick Disk Utility, select your main disk and Mount it this is required if your disk is encrypted and requires password to be mountedģ. Boot to Recovery (with CMD + R or CMD + Shift + R if you don't have recovery partition)Ģ. However, one problem with that article is that the kextstat command is not available in Terminal utility running in recovery mode.Īs a work-around, these are the steps i took to solve the problem:ġ. In that article, the section titled “ Un-Assigned Kernel Misfiring” explains how to boot into recovery mode and launch Terminal utility. MacBook Will Not Start Up After macOS Update, How-To Fix Note: When I removed these KEXT Extensions, the “circle slash” problem did not resolve until i finally removed: ParagonSnapshot.kext and VDMounter.kextīelow is a link to a useful article which provides some helpful information regarding: LittleSnitch.kext (Creator: LittleSnitch) (note: this is DIFFERENT directory from /System/Library/Extensions/) UNSIGNED KEXT EXTENSIONS REMOVED FROM Directory: USING TERMINAL COMMANDS IN RECOVERY MODE, YOU SHOULD BE ABLE TO RESOLVE THIS PROBLEM BY REMOVING UNSIGNED KEXT EXTENSIONS FROM LOCATION: /Volumes//Library/Extensions/Īfter I removed the following KEXT files from the /Volumes//Library/Extensions/ directory, my MacBook booted up properly, and finished installing the Mojave update.
Sometimes these un-signed kernel extensions cause this headache after an OS X or macOS update. Starting with Yosemite, kernel extensions must be code signed by the developer with Apple authorization or OS X won’t load them. The kernel typically manages I/O requests, and in OS X, the file ends in “.kext.” Kernel Extension is a piece of code that extends the capability of the base kernel of an operating system. This time i did some more research, and discovered that the issue may be caused by UNSIGNED KERNEL EXTENSION (KEXT) files existing on my HD. My computer automatically installed the update overnight, and in the morning, my screen was showing circle slash. This happened again the other day with the recent Mojave update 10.14.2. In the past, the only way i was able to get around the problem, is by re-formatting my HD, installing latest version of Mojave OS, and then migrating all my data from my TimeMachine backup. I have also tried: (a) specifying the startup disk (problem still persists) (b) attempting to start in safe mode (problem persists) doing the NVRAM reset (problem persists). I’m still able to boot into recovery mode (CTRL-R at Startup), however running disk repair on my MacBook HD does NOT solve the problem. Rebooting still produces a prohibitory symbol. I have a MacBook pro running MacOS Mojave.įor the past year or so, every time a new MacOS update rolls out, and is attempted to be installed on my MacBook, it ends up displaying the circle slash (Prohibitory Symbol). SOLVED: MacBook Will Not Start Up After macOS Update
0 kommentar(er)
