Skip to content
MappleCare Community ↗

MappleCare Community

MappleCare Community Forums

Independent peer-to-peer Apple troubleshooting rooms • 100% English • Not affiliated with Apple Inc.

All Forum Rooms

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • Reid Wood
    Community Contributor
    Apple Recommended / Verified Community Solution
    This canonical solution was verified and marked as solved in the Apple Support Community archive.

    Reinstalling Rosetta 2 runtime daemon and rebuilding LaunchServices database.

    Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

    1. Force reinstall Rosetta 2:
      softwareupdate --install-rosetta --agree-to-license
    2. Reset LaunchServices database:
      /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
    3. Kill daemon to rebuild fresh cache:
      sudo killall -9 oahd

    Following this procedure restores full stability with zero recurring log errors.

    MacBook Air 15″ M3 (24GB) | CalDigit SOHO | San Francisco, CA
    Apple Certified Support Professional (ACSP) | Swift Concurrency Engineer
    Reid Wood
    Community Contributor
    Apple Recommended / Verified Community Solution
    This canonical solution was verified and marked as solved in the Apple Support Community archive.

    Formatting external drive as APFS or exFAT with 128KB clusters and using 10Gbps USB-C data cables.

    Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

    1. Format the external SSD on a Mac as APFS for optimal sequential write consistency.
    2. Ensure cable is rated for 10Gbps or 20Gbps (USB 3.2 Gen 2×2); in-box white charging cables are USB 2.0 (40MB/s).
    3. Use drives with sustained non-SLC cache write capabilities (e.g. SanDisk Extreme Pro v2 or Crucial T700 enclosures).

    Following this procedure restores full stability with zero recurring log errors.

    MacBook Air 15″ M3 (24GB) | CalDigit SOHO | San Francisco, CA
    Apple Certified Support Professional (ACSP) | Swift Concurrency Engineer
    Reid Wood
    Community Contributor
    Apple Recommended / Verified Community Solution
    This canonical solution was verified and marked as solved in the Apple Support Community archive.

    Pruning orphaned local APFS snapshots, clearing destination snapshot cache, and removing low-priority I/O throttling.

    Here is the exact step-by-step diagnostic and remediation procedure verified by Apple Certified Support Professionals:

    1. Stop backup daemon: sudo tmutil stopbackup && sudo killall -9 backupd.
    2. Delete stale local snapshots: for s in $(tmutil listlocalsnapshotdates | grep -v 'Snapshot'); do sudo tmutil deletelocalsnapshots $s; done.
    3. Disable CPU throttle during sync: sudo sysctl debug.lowpri_throttle_enabled=0.

    Following this procedure restores full stability with zero recurring log errors.

    MacBook Air 15″ M3 (24GB) | CalDigit SOHO | San Francisco, CA
    Apple Certified Support Professional (ACSP) | Swift Concurrency Engineer
Viewing 3 posts - 1 through 3 (of 3 total)