macOS 27 Drops CoreStorage: The End of an Old Disk Format

Apple has quietly removed a compatibility feature that was crucial for long-time users in the latest macOS 27: CoreStorage volumes. This change sparked discussion on the tech community Hacker News, and although the discussion wasn't very heated, it reflects yet another thorough clean break by Apple from an old technology stack.

What Is CoreStorage, and Why Does It Still Affect You

CoreStorage is a logical volume management architecture that Apple introduced during the Mac OS X Lion era. It was once the underlying support for Fusion Drive and FileVault full-disk encryption. Simply put, it sits between the physical disk and the file system, responsible for combining multiple physical volumes into one logical volume, or for encrypting and converting volumes.

Before APFS became the default file system, a large number of Mac devices—especially iMacs and Mac minis equipped with Fusion Drive—ran on top of CoreStorage. Even after APFS gradually took over, some users still retained CoreStorage volumes due to upgrade paths, external drives, or compatibility with older devices.

According to discussions on Hacker News, macOS 27 no longer recognizes such volumes, meaning these users may be unable to mount or access their original data after upgrading the system.

To understand CoreStorage's position, one must first clarify its hierarchical relationship with the file system. Traditionally, above the disk is the partition table (GPT), and directly above the partition is the file system (such as HFS+). CoreStorage inserts a layer of logical volume management between the two: physical partitions are first wrapped as "physical volumes," which are then combined, encrypted, or snapshotted into "logical volumes," and the file system is built on top of this logical volume. This design is similar to Linux's LVM or Windows Storage Spaces. The benefit is that volumes can be merged, expanded, and encrypted without changing the file system. Fusion Drive relies on this layer to transparently merge an SSD and a mechanical hard drive into a single volume, with the system automatically migrating data between them based on access frequency. This also explains why removing CoreStorage affects older Fusion Drive devices—if the underlying logical volume cannot be recognized, the upper-layer merging and cache scheduling naturally all fail.

Apple's Compatibility Strategy: Gradual Phase-Out

Apple has never taken a one-size-fits-all approach to phasing out old technology. In the migration from HFS+ to APFS, Apple gave users years of transition time and built conversion tools into the system installer. But CoreStorage's situation is more special: it was never officially and explicitly labeled "deprecated," yet it never received new feature support in the APFS era.

This "silent phase-out" has precedent in Apple's product history. The multiple delays of Rosetta 2 and the eventual retirement of 32-bit apps all followed a similar rhythm—first stop promoting it, then stop supporting new features, and finally remove it entirely in some system version. macOS 27's handling of CoreStorage is exactly the endpoint of this path.

For users still using CoreStorage volumes, there are few realistic choices left: either manually migrate data to an APFS volume before upgrading, or stay on an older version of macOS. Apple did not prominently explain this change in the release notes, which also means the company may not provide an automatic conversion tool.

It should be added that APFS and HFS+/CoreStorage differ fundamentally in design goals. APFS is a new-generation file system Apple introduced in 2017 with macOS High Sierra. From the start, it treated snapshots, copy-on-write, native encryption, space sharing, and SSD optimization as core design goals, rather than patching an old architecture. This means that the logical volume merging and encryption functions provided by CoreStorage are natively handled in APFS by the container and volume mechanisms. The two do not correspond one-to-one conceptually, so there is no simple in-place upgrade path. Apple built a conversion process for Fusion Drive into the High Sierra installer, but that process required specific firmware and volume state checks first, and some external or non-standard configurations were excluded. This is precisely the technical reason why some users remain on CoreStorage today.

Practical Impact on Ordinary Users and IT Administrators

The scenarios affecting ordinary users are mainly concentrated in two categories: first, older Macs using Fusion Drive; second, external storage that once had FileVault encryption enabled but never completed APFS conversion. After these devices upgrade to macOS 27, CoreStorage volumes will no longer be recognized by the system, and data access will be interrupted.

For IT administrators, the impact is more specific. A large number of old devices in enterprise environments may still be running CoreStorage volumes, and a volume format audit is needed before batch upgrades. Apple's silent approach means administrators cannot rely on system update prompts to discover risks and must actively check.

From the perspective of technical evolution, this removal itself is not surprising. APFS has clear advantages in snapshots, encryption, space sharing, and other areas, and CoreStorage's historical mission was long ago completed. What is truly worth discussing is whether Apple should give users clearer warnings and a smoother migration path when phasing out old technology.

For IT administrators, to determine whether a Mac uses CoreStorage, they can run diskutil cs list in Terminal. If it returns logical volume group information, the machine is still on CoreStorage. Once macOS 27 removes support, this command and any scripts that depend on it will stop working, so audit work must be completed before upgrading. The usual migration approach is to back up data and then erase and rebuild the disk as APFS, or use diskutil apfs convert to attempt an in-place conversion, but the latter has additional restrictions for Fusion Drive and already-encrypted volumes. During enterprise batch deployment, volume format checks should also be included in the standardized pre-upgrade checklist to avoid discovering only after the system update that devices cannot boot or data is unreadable.

Lessons From the Retirement of Old Technology

macOS 27's removal of CoreStorage support is another step in Apple's technology stack modernization. For ordinary users, this is an upgrade risk that requires proactive handling; for the industry as a whole, it once again reminds us that in a closed ecosystem, backward compatibility is always a limited resource, and users cannot assume that old formats will be supported forever.

If you still have devices with CoreStorage volumes, be sure to back up and convert the format before upgrading. Apple did not make a fanfare about this change, but the risk of data loss will not be reduced because of that.

One-line Summary

macOS 27 quietly removes CoreStorage volume support, putting older Mac users at risk of interrupted data access when upgrading.

Paragraph Summary

The article discusses the change in macOS 27 that removes CoreStorage volume support. CoreStorage is a logical volume management architecture introduced in the Lion era and was once the underlying support for Fusion Drive and FileVault full-disk encryption. Even after APFS became widespread, some older devices and external storage still used it. macOS 27 no longer recognizes such volumes, and users may be unable to mount their original data after upgrading. The article points out that Apple has consistently adopted a gradual, low-publicity phase-out strategy; this time there was no high-profile explanation, and an automatic conversion tool may not be provided. Those affected are mainly older Macs using Fusion Drive and encrypted external drives that have not completed APFS conversion. Ordinary users need to back up and migrate before upgrading, while IT administrators must proactively audit volume formats in enterprise environments.