Back in September, I wrote about how to get ready for this upgrade. “Preparation Guide For macOS High Sierra Installation.” However, despite my eagerness, I was waiting for one mission critical app to get updated. More on that below. Finally, I decided to forge ahead when both a quiet Saturday and macOS version 10.13.1 arrived at the same time.
I followed my guidelines. I checked off my app compatibility list first. It was a good time to upgrade to some mission critical apps: Audio Hijack (3.3.5), BBEdit (12.0.1), Carbon Copy Cloner (5.0.3), Loopback (1.1.5). Along the way, I cleaned out some crufty 32-bit apps tha aren’t going to work in macOS 10.14 next year.
Left behind, however, was Data Backup 4. It’s not yet ready for High Sierra. I have been in contact with Prosoft Engineering, and they’re going to notify me when it’s ready. I decided to live on the edge and use only Time Machine and Carbon Copy Cloner for a short time.
Speaking of backups, I did some research on CCC. I had suspected that I needed CCC 5 to continue making backups of my newly formatted APFS internal drive. That’s not the case. Mike Bombich has provided a very helpful FAQ. “Everything you need to know about Carbon Copy Cloner and APFS.” Notable was this section.
Can CCC make a bootable backup of an APFS volume?
Yes. Both CCC 4 and CCC 5 can make bootable backups of APFS-formatted startup disks, however there is a limited amount of support for APFS in CCC 4. CCC 4 can make a bootable backup from an APFS-formatted volume to an HFS+ formatted volume, and can even create a recovery volume on that HFS+ backup disk. CCC 5 can make a bootable backup from an APFS-formatted volume to an HFS+ formatted volume or to an APFS-formatted volume. CCC 5 also supports APFS encryption (e.g. CCC 5 can unlock and mount APFS-encrypted volumes during a backup task). Naturally any additional support that we can provide for APFS will be made within CCC 5; new features and functionality will not be added to CCC 4.
Finally, I did my system integrity checks, and double checked to make sure I was fully backed up using Time Machine, CCC, and Data Backup. I started the upgrade.
The install took about an hour. The first thing I checked when the Mac Pro came back up was a Get Info on the boot volume to make sure it was upgraded to APFS. It was. Cool.
Then I started launching some of my mission critical Apps. I noticed that High Sierra seemed snappier, as is usually the case with a new macOS. One of the first apps I tested was email.
That’s when I had serious cause for alarm.
All the email text was scrambled. And I mean all. Both the message list and the message body looked as if it had become encrypted. But it was really just an undefined font, a sea of random unicode graphics characters. OMG.
My first reaction was alarm. (In my agitation, I failed to get a screen shot of this mess.) Was the H.S. upgrade corrupted? Would I have to do a restore to Sierra?
I did a Google search to see if anyone else had this problem. Apparently not. So I tried a simple restart. No joy. Then I tried a safe boot, and while that didn’t improve the mail fonts, during the boot, it occurred to me to try something simple.
Think about straightforward fixes.
macOS is so complex and opaque in many ways, it’s tempting to conclude that something very bad and unrecoverable has happened behind the scenes. Instead, it’s often helpful to sit and think for a bit. Maybe there’s a user-level fix. No other app experienced this problem, and that was a major clue.
In this case, it occurred to me that perhaps only the Mail app had simply lost track of the assigned fonts. So I went into the Mail App preferences and reassigned new fonts like this:
As I did that, the message list and message bodies snapped into proper legibility. To say that I was relieved that my entire email database was not completely scrambled is putting it mildly.
The lesson, as always, is to 1) Don’t overreact. 2) Do a Google search for that problem (and a solution). It may have happened to someone else. 3) Investigate and experiment. Remain calm. 4) Look for clues. 5) Think about user-level fixes. The core of macOS is unlikely to be the culprit these days.
Next page: Unexpected GUI lockups.