The first thing I did after connecting the MacBook Pro as a disk to the Mac Pro was to run Disk Utility again and confirm that the SSD was, in fact, corrupted, and that the hard disk was not. I shut down my MacBook Pro, and restarted it in FireWire Target Disk Mode, and plugged it into the Mac Pro I have at work.

It found several minor issues, and one that it described as an “invalid sibling link.” At this point, I went into recovery mode. Lest you think I have a truly weird setup, consider the fact that Apple currently sells two Macs - the MacBook Air and the server configuration of the Mac mini - that also lack an optical drive.Ĭoncerned for the health of my disk, I fired up Disk Utility and had it check my startup disk. This hardware configuration would affect my efforts to repair the damage. My MacBook Pro is not quite stock I have replaced its internal SuperDrive with a 120 GB solid-state drive (SSD), leaving the 500 GB internal hard drive in place. In old Mac (Carbon and pre-Carbon) header files, this error was described as “I/O error (bummers)”, and that’s usually what it means - some serious general error has occurred. This disturbed me greatly, since, as an old-time Mac developer, I know that -36 is a serious error. The message said that an error had occurred, and gave me an error code: -36. Last Wednesday afternoon, when I tried to empty my MacBook Pro’s Trash, I got an error message.

#1616: Explaining passkeys, Apple challenges for senior citizens, macOS 11.6.7 Big Sur fixes email attachment bug.

#1617: Pages regains mail merge, HomeKit sensor improvements, keyboard flags in Monterey.

Preview selections, portable power for a MacBook Pro

#1618: M2 MacBook Air available to order, Lockdown Mode, Live Text vs.

#1619: Stage Manager first impressions, Live Text in Preview redux, SMS 2FA failure fix, moving large folders with ChronoSync.#1620: OS updates, AssistiveTouch for iOS shortcut palette, Photos album sharing bug.

Owc mac memory reviews