I like Tahoe a lot. But a word of warning about a glitch that I ran into this evening.
I was trying to do some screen resolution adjustments on my Mac Mini, which I use as a ChannelsDVR server. I run it headless and connect to it using Jump Desktop (or, occasionally, the built-in Screen Sharing). I updated it to Tahoe last week.
Wanting to see if my changes would stick, I rebooted the machine — only to discover I could no longer connect to it.
To figure out what was going on, I had to unplug it and take to a different room so I could connect it directly to a monitor. When I booted up again, it demanded my password, which I thought odd. Because I only ever access the machine remotely — from several states away at some times of the year — I’d had auto login enabled.
When I went into settings to re-enable it, I couldn’t, because FileVault was enabled. I had to disable that before re-enabling auto login.
Here’s the thing: I never enabled FileVault on this particular machine, precisely so that I could safely reboot it remotely if needed.
FileVault is turned on by default when you upgrade to Tahoe if you sign in with an Apple account during the process. I discovered that with a quick search that led me to this conversation in the TidBits forum.
And sure enough, that bit of information was included in the Ars Technica review, which I hadn’t seen.
The problem is that at no point that I can recall during the upgrade process was I told that FileVault would be automatically enabled, so this caught me by surprise.
It’s an issue that’s easy enough to fix, once you know what’s going on, but I’d like to spare others the head-scratching and frustration I encountered this evening.