Golden Gate Does Not Actually Support CoreStorage
macOS 15 Sequoia had a hard time with CoreStorage and HFS+ volumes, since it deprecated both technologies and callously crippled some important tools for working with them, but nonetheless it mostly still worked.
[…]
Not only does Golden Gate just not support CoreStorage or HFS+ volumes, out of the box you can’t do anything with them – can’t mount them, can’t convert them to APFS, can’t even erase them. It renders your expensive storage hardware completely useless.
Worse, macOS 27 puts up a misleading dialog, upon boot, saying that macOS 28 (the next version) won’t support these volumes. I have no idea what Apple’s doing or thinking. Maybe it’s all just an embarrassing misunderstanding – the file system team told the notifications team that CoreStorage & HFS support is gone, and typoed the version number as 28 rather than 27?
Apple also wrote an article this summer saying that CoreStorage volumes would be supported in macOS 27 and that unencrypted HFS+ would be supported in macOS 28.
Tregaskis says that macOS 27 does not support “CoreStorage or HFS+,” but in my testing plain HFS+ volumes do work.
Previously:
Update (2026-11-04): See also: Hacker News.
9 Comments RSS · Twitter · Mastodon
Interesting - I had absolutely no luck getting any encrypted HFS+ drive to work… when you say “plain”, do you mean unencrypted (and presumably thus non-CoreStorage)? I didn’t test that case - to be honest it didn’t really cross my mind till just now (I’ve been using encrypted disks exclusively - camera memory cards notwithstanding - ever since FileVault 2 came out).
It could be that the problem is only with CoreStorage, not the HFS layer. I’m not sure how helpful that is in practice, but nonetheless I’d like to correct my post, if so.
>Tregaskis says that macOS 28 does not support “CoreStorage or HFS+,” but in my testing plain HFS+ volumes do work.
macOS 27, no?
Yeah, unencrypted HFS+ works fine on Golden Gate.
I just formatted a USB drive as HFS+ in the Finder (by right-clicking it, choosing "Erase…) … it gave me the choice of APFS, HFS+, ExFAT, or FAT. When choosing HFS+ it has a checkbox to choose whether or not to use the case-sensitive version. (Whereas with APFS it gives me both the case sensitivity checkbox and a checkbox for encryption, the latter of which is now missing for HFS+.)
% diskutil list disk14; mount | grep disk14 /dev/disk14 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *15.5 GB disk14 1: Apple_HFS Untitled 15.5 GB disk14s1 /dev/disk14s1 on /Volumes/Untitled (hfs, local, nodev, nosuid, journaled, noowners)
Thanks for the follow-ups and corrections - I’ve updated my post, to at least be clearer. I still haven’t tried unencrypted HFS+ (I’m not in front of a Golden Gate machine right now) but it seems likely that the problem is with CoreStorage specifically, not HFS+ per se.
I still don't understand what I'm supposed to do with my large storage *hard* drives. You know, the ones that perform just *awful* if you use APFS with them?
My Time Machine drive is a hard drive and formatted APFS, and it is dog slow. Recovering data from it is grueling. Every time I open it in Finder I have to stare at a screen that says "No completed backups" -- a stupid UI design flaw in of itself -- and listen to it furiously click for a minute or so before it realizes that there are indeed over a year's worth of backups on it. I never use the snazzy Time Machine interface any longer because the performance is so bad that it simply doesn't work. But it worked great as an HFS+ drive back in macOS 10.14.
Why does Apple think that an SSD filesystem should be used universally? Do they think hard drives just vanished, especially in this time where storage prices have exploded and large SSDs are obscenely expensive compared to their HDD counterparts? I suppose it's the same boneheaded decision making that led them to mess up their UI.
@Bri: My solution as far as what to do with my spinning rust has been to stick them in a NAS and let Time Machine talk to them using SMB, sadly seems to work better than having directly attached spinning drives.
I'm not sure if encrypted HFS+ always implies CoreStorage, but here's another data point:
- macOS 27.2.1 had no problem reading my 2 external USB hard drives that were formatted with encrypted HFS+. They showed up in Finder and Disk Utility just fine.
- I performed the Convert to APFS step in Disk Utility and it also ran fine on both drives. The conversion only took 1 or 2 minutes and the result was an encrypted APFS volume.