ferrofivestar.blogg.se - Boot mac into safe mode mojave

#BOOT MAC INTO SAFE MODE MOJAVE FULL#
#BOOT MAC INTO SAFE MODE MOJAVE PRO#
#BOOT MAC INTO SAFE MODE MOJAVE SOFTWARE#

The iMac Pro, running Mojave and Time Machine, took half an hour – yes, 30 minutes – to start up in Safe Mode, requiring two separate logins, the first to unlock its T2-encrypted internal SSD at the start, the second half an hour later to log on as the user.

#BOOT MAC INTO SAFE MODE MOJAVE PRO#

The other is my Catalina test system, a MacBook Pro 2017 without Touch Bar (no T1/T2 chip) running Catalina 10.15, with an external 750 GB SSD but no Time Machine or backups, so probably no snapshots either.īoth systems seemed to accomplish objectives 2 and 3 above just fine, but disk checking and repair remain a mystery. One’s an iMac Pro running fully updated Mojave with Time Machine active, and a couple of dozen snapshots accessible as well as the backup drive, and external RAID in HFS+. I’ve now put both my active Macs into Safe Mode. It also doesn’t mention checks on other mounted volumes, or on APFS snapshots.

#BOOT MAC INTO SAFE MODE MOJAVE FULL#

If the directory is repaired, your Mac automatically restarts.” I note the carefully chosen words “similar to”, which isn’t the same as “the same as”, and specific reference to directory checking and repair, which is more limited than a full fsck_apfs. This is similar to what happens when you use Disk Utility to verify or repair your disk. Of course, that should be easy to answer by trying it then browsing the fsck_apfs log in /var/log.Īccording to Apple, “Your Mac automatically checks the directory of your startup disk when you start up in safe mode. If you’re trying to isolate a problem which affects one of those sub-systems, Safe Mode won’t help.īut the question which was raised here was whether Safe Mode performs a full check and repair of your boot disk, in the way that would be performed by starting up in Recovery Mode and running First Aid in Disk Utility. The second of those limits its usefulness, as some of the blocked items prevent some sub-systems from working normally.

it deletes font caches, the kernel cache, and other system caches.

it blocks the loading of many kernel extensions, startup and login items, and user-installed fonts.

it verifies the boot disk and, if there are any directory issues with it, it attempts its repair.

According to Apple’s current support page, Safe Mode does three things: What used to be a quick check of your boot disk file system has, by some accounts, turned into a very long inspection of all the snapshots stored in APFS, something not even attempted by Recovery Mode, unless you make it so. Recently, though, it seems to have changed.

It also conveniently flushed various unmentionable caches, and left your user space clean as a whistle again.

#BOOT MAC INTO SAFE MODE MOJAVE SOFTWARE#

Safe Mode was a useful tool when things started to go awry: there was something not quite right, possibly a software conflict, and starting up with the Shift key held gave you a chance to isolate the problem.