{"article":{"slug":"macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes","title":"macOS 27 Golden Gate does not actually support CoreStorage (or HFS+) volumes","subtitle":null,"summary":"Wade Tregaskis reports that macOS 27 Golden Gate no longer properly supports CoreStorage, and therefore encrypted HFS+ volumes, describes what breaks, shares the workaround he found, and asks for better ones.","content_type":"blog_post","language":"en","canonical_url":"https://wadetregaskis.com/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes/","author":{"name":"Wade Tregaskis","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"Wade Tregaskis","url":null,"listing_slug":null,"listing":null},"topics":[{"name":"macos","slug":"macos","url":"https://listedarticles.com/topics/macos"},{"name":"apple","slug":"apple","url":"https://listedarticles.com/topics/apple"},{"name":"storage","slug":"storage","url":"https://listedarticles.com/topics/storage"},{"name":"filesystems","slug":"filesystems","url":"https://listedarticles.com/topics/filesystems"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":1106,"reading_minutes":5,"published_at":"2026-11-03T07:49:06.000Z","added_at":"2026-11-03T23:08:49.600Z","updated_at":"2026-11-03T23:08:49.600Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":true},"profile_url":"https://listedarticles.com/articles/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes","markdown_url":"https://listedarticles.com/articles/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes.md","example":false,"citation":"Wade Tregaskis, Wade Tregaskis. \"macOS 27 Golden Gate does not actually support CoreStorage (or HFS+) volumes.\" 3 Nov 2026. https://wadetregaskis.com/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes/ (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://wadetregaskis.com/macos-27-golden-gate-does-not-actually-support-corestorage-or-hfs-volumes/"},"body_markdown":"# macOS 27 Golden Gate does not actually support CoreStorage (or HFS+) volumes\n\nContents\n\n- [Details](#Details)\n- [Workaround](#Workaround)\n- [Call for better workarounds](#Call_for_better_workarounds)\n\nmacOS 15 Sequoia had a hard time with CoreStorage – and thus encrypted HFS+ volumes – since it deprecated both technologies and callously crippled some important tools for working with them, but nonetheless it *mostly* still worked. While I’d often – but not always – have to manually unlock one of my HFS+ volumes – but not the others – at boot, and it also refused to convert some – but not all – volumes from HFS+ to APFS[1](#c63a9f61-72c1-4689-a06c-d132ac976f25), keeping me trapped in the situation – it ultimately still *worked*. I could get at my data and use the volumes more or less normally.\n\nUnfortunately, in macOS 27 that’s no longer the case. Not only does Golden Gate just not support CoreStorage / encrypted 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.\n\nWorse, 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 & encrypted HFS+ support is going away, and typoed the version number as 28 rather than 27?\n\n## Details\n\nmacOS 27 cannot mount CoreStorage volumes automatically or through any normal means. Worse, Disk Utility can’t mount them even when manually told to – it just fails with the cryptic error:\n\n> com.apple.DiskManagement.disenter error 49,153\n\n`diskutil mount` *also* fails, this time with an error message that is a blatant lie:\n\n> `disk27 is a CoreStorage Logical Volume which is locked; use \"diskutil coreStorage unlockVolume\"`\n\n```\n$ diskutil cs unlockVolume BC304645-7D99-481E-931F-855B3011D89D  \nBC304645-7D99-481E-931F-855B3011D89D is already unlocked and is attached as disk27  \n$ diskutil cs list                                               \nCoreStorage logical volume groups (1 found)  \n|  \n+-- Logical Volume Group 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \n    =========================================================  \n    Name:         Smash  \n    Status:       Online  \n    Size:         2000054960128 B (2.0 TB)  \n    Free Space:   0 B (0 B)  \n    |  \n    +-< Physical Volume 1B5A1754-184B-4F17-A797-BF69B4BB627F  \n    |   ----------------------------------------------------  \n    |   Index:    0  \n    |   Disk:     disk10s2  \n    |   Status:   Online  \n    |   Size:     2000054960128 B (2.0 TB)  \n    |  \n    +-> Logical Volume Family 376204CD-8048-4962-B05C-72F4FC16B77B  \n        ----------------------------------------------------------  \n        Encryption Type:         AES-XTS  \n        Encryption Status:       Unlocked  \n        Conversion Status:       Complete  \n        High Level Queries:      Fully Secure  \n        |                        Passphrase Required  \n        |                        Accepts New Users  \n        |                        Has Visible Users  \n        |                        Has Volume Key  \n        |  \n        +-> Logical Volume BC304645-7D99-481E-931F-855B3011D89D  \n            ---------------------------------------------------  \n            Disk:                  disk27  \n            Status:                Online  \n            Size (Total):          1999702634496 B (2.0 TB)  \n            Revertible:            No  \n            LV Name:               Smash  \n            Volume Name:           Smash  \n            Content Hint:          Apple_HFS\n```\n\nTangentially: surprisingly, [hfsutils](https://www.mars.org/home/rob/proj/hfs/) (installed via [brew](https://brew.sh)) don’t work at all:\n\n```\n$ sudo hmount /dev/disk27  \nhmount: /dev/disk27: not a Macintosh HFS volume (Invalid argument)  \n$ sudo hmount /dev/disk10s2  \nhmount: /dev/disk10s2: not a Macintosh HFS volume (Invalid argument)\n```\n\nBut what’s even worse about this dumpster fire is that macOS 27 *can* mount these volumes just fine – it’s just that all the *normal* ways to do it are completely broken. If you go down to a lower level and run `mount_hfs` directly, it *does* work:\n\n```\n$ sudo mkdir -p /Volumes/Smash  \n$ sudo mount_hfs -o rdonly /dev/disk27 /Volumes/Smash  \n$ ls /Volumes/Smash  \nDocuments           Pictures           Scratch space\n```\n\nThat said… that `-o rdonly` parameter… in principle it shouldn’t be required, but I could *not* get macOS 27 to let me mount any HFS-on-CoreStorage volume as read-write – no matter what I did, it always fails with error “Resource busy” (EBUSY). I spent a lot of time trying to debug this, and could find *no* evidence of anything having the volume in question open (nothing in `lsof` etc).\n\nBut wait, it gets worse.\n\nmacOS 27 can’t even erase the volume. All the normal tools – `diskutil`, Disk Utility, etc – fail with that same “Resource busy” error.\n\n## Workaround\n\nThankfully, with the help of Gemini 4 Argon, I did find a workaround. It’s convoluted, but takes only a few steps, thankfully.\n\nFirst, while if you try to delete the logical volume group it ostensibly fails, it doesn’t *completely* fail – it does actually delete the logical volume(s) within:\n\n```\n$ diskutil cs delete 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \nStarted CoreStorage operation  \nUnmounting Logical Volumes  \nDestroying Logical Volume Group  \nErasing disk10s2  \nnewfs_hfs: cannot create filesystem on /dev/rdisk10s2: Resource busy  \nMounting disk  \nCould not mount disk10s2 after erase  \nError: -69832: File system formatter failed  \n1 💣 $ diskutil cs list                                         \nCoreStorage logical volume groups (1 found)  \n|  \n+-- Logical Volume Group 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \n    =========================================================  \n    Name:         Smash  \n    Status:       Offline  \n    Size:         2000054960128 B (2.0 TB)  \n    Free Space:   -none-  \n    |  \n    +-< Physical Volume 1B5A1754-184B-4F17-A797-BF69B4BB627F  \n        ----------------------------------------------------  \n        (No properties)  \n$ diskutil cs delete 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \nStarted CoreStorage operation  \nDestroying Logical Volume Group  \nError: -69783: Unable to delete the CoreStorage Logical Volume Group\n```\n\nYou still can’t destroy it completely, nor can you erase the physical volume yet – the “Resource busy” errors persist. But, the trick is to *restart* – after that, you *can* then erase the volume.\n\nSo it seems that whatever broken thing is holding the physical volume (or logical volume group) in a ‘busy’ state is tied to the existence of the logical volume(s) therein, and once they’re deleted (and the machine rebooted) the bug stops being triggered.\n\n## Call for better workarounds\n\nI’ve glossed over a *lot* of debugging and attempts I made to save the volume in-place, by either making it work as-is (even if only with e.g. hfsutils) or by converting it to APFS, but neither I nor Gemini 4 Argon could find anything that worked. It’s too late for me – I was forced to just delete all my HFS+ & CoreStorage volumes and rebuild them painstakingly from backups – but if anyone finds a way, I’d love to amend this post, for the benefit of future readers.\n\n1. The problem remains the same in macOS 27 – so *three* major macOS versions, at a minimum, where essential system update functionality has not worked. Sigh.  \n     \n   `$ diskutil apfs convert disk27  \n   Converting the volume on disk27 to an APFS Volume on an APFS Container  \n   Started APFS operation on disk27 (Smash)  \n   Converting HFS Volume to an APFS Container which will export one APFS Volume  \n   The target is the Journaled HFS+ volume \"Smash\" on disk27 backed via CoreStorage on disk10s2  \n   Checking booter partition disk10s3  \n   The target is a data disk; it is not a macOS system disk  \n   No APFS EFI driver found to install  \n   Saving encryption context  \n   The target is encrypted  \n   Unmounting disk27  \n   Starting conversion from HFS to APFS  \n   Performing apfs_hfs_convert -x --verbose=0x400 /dev/disk10s2  \n   Reporting post-conversion statistics  \n   A problem occurred during conversion from HFS to APFS  \n   APFS Converter exit code is 1  \n   Aborted conversion in commit mode so will restore type  \n   Setting type of disk10s2 to CS  \n   Changing the physical disk partition type in shared mode  \n   Partition modification attempt count was 1  \n   Not mounting APFS Volume  \n   Exiting conversion operations with error code -69860  \n   Error: -69860: The underlying task reported failure on exit  \n   Underlying error: 1`  \n    [↩︎](#c63a9f61-72c1-4689-a06c-d132ac976f25-link)\n","body_html":"<h1 id=\"macos-27-golden-gate-does-not-actually-support-corestorage-or-hf\">macOS 27 Golden Gate does not actually support CoreStorage (or HFS+) volumes</h1>\n<p>Contents</p>\n<ul><li><a href=\"#Details\">Details</a></li><li><a href=\"#Workaround\">Workaround</a></li><li><a href=\"#Call_for_better_workarounds\">Call for better workarounds</a></li></ul>\n<p>macOS 15 Sequoia had a hard time with CoreStorage – and thus encrypted HFS+ volumes – since it deprecated both technologies and callously crippled some important tools for working with them, but nonetheless it <em>mostly</em> still worked. While I’d often – but not always – have to manually unlock one of my HFS+ volumes – but not the others – at boot, and it also refused to convert some – but not all – volumes from HFS+ to APFS<a href=\"#c63a9f61-72c1-4689-a06c-d132ac976f25\">1</a>, keeping me trapped in the situation – it ultimately still <em>worked</em>. I could get at my data and use the volumes more or less normally.</p>\n<p>Unfortunately, in macOS 27 that’s no longer the case. Not only does Golden Gate just not support CoreStorage / encrypted HFS+ volumes, out of the box you can’t do <em>anything</em> 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.</p>\n<p>Worse, macOS 27 puts up a misleading dialog, upon boot, saying that macOS <em>28</em> (the <em>next</em> 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 &amp; encrypted HFS+ support is going away, and typoed the version number as 28 rather than 27?</p>\n<h2 id=\"details\">Details</h2>\n<p>macOS 27 cannot mount CoreStorage volumes automatically or through any normal means. Worse, Disk Utility can’t mount them even when manually told to – it just fails with the cryptic error:</p>\n<blockquote><p>com.apple.DiskManagement.disenter error 49,153</p></blockquote>\n<p><code>diskutil mount</code> <em>also</em> fails, this time with an error message that is a blatant lie:</p>\n<blockquote><p><code>disk27 is a CoreStorage Logical Volume which is locked; use &quot;diskutil coreStorage unlockVolume&quot;</code></p></blockquote>\n<pre><code>$ diskutil cs unlockVolume BC304645-7D99-481E-931F-855B3011D89D  \nBC304645-7D99-481E-931F-855B3011D89D is already unlocked and is attached as disk27  \n$ diskutil cs list                                               \nCoreStorage logical volume groups (1 found)  \n|  \n+-- Logical Volume Group 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \n    =========================================================  \n    Name:         Smash  \n    Status:       Online  \n    Size:         2000054960128 B (2.0 TB)  \n    Free Space:   0 B (0 B)  \n    |  \n    +-&lt; Physical Volume 1B5A1754-184B-4F17-A797-BF69B4BB627F  \n    |   ----------------------------------------------------  \n    |   Index:    0  \n    |   Disk:     disk10s2  \n    |   Status:   Online  \n    |   Size:     2000054960128 B (2.0 TB)  \n    |  \n    +-&gt; Logical Volume Family 376204CD-8048-4962-B05C-72F4FC16B77B  \n        ----------------------------------------------------------  \n        Encryption Type:         AES-XTS  \n        Encryption Status:       Unlocked  \n        Conversion Status:       Complete  \n        High Level Queries:      Fully Secure  \n        |                        Passphrase Required  \n        |                        Accepts New Users  \n        |                        Has Visible Users  \n        |                        Has Volume Key  \n        |  \n        +-&gt; Logical Volume BC304645-7D99-481E-931F-855B3011D89D  \n            ---------------------------------------------------  \n            Disk:                  disk27  \n            Status:                Online  \n            Size (Total):          1999702634496 B (2.0 TB)  \n            Revertible:            No  \n            LV Name:               Smash  \n            Volume Name:           Smash  \n            Content Hint:          Apple_HFS</code></pre>\n<p>Tangentially: surprisingly, <a href=\"https://www.mars.org/home/rob/proj/hfs/\" rel=\"nofollow ugc noopener\">hfsutils</a> (installed via <a href=\"https://brew.sh\" rel=\"nofollow ugc noopener\">brew</a>) don’t work at all:</p>\n<pre><code>$ sudo hmount /dev/disk27  \nhmount: /dev/disk27: not a Macintosh HFS volume (Invalid argument)  \n$ sudo hmount /dev/disk10s2  \nhmount: /dev/disk10s2: not a Macintosh HFS volume (Invalid argument)</code></pre>\n<p>But what’s even worse about this dumpster fire is that macOS 27 <em>can</em> mount these volumes just fine – it’s just that all the <em>normal</em> ways to do it are completely broken. If you go down to a lower level and run <code>mount_hfs</code> directly, it <em>does</em> work:</p>\n<pre><code>$ sudo mkdir -p /Volumes/Smash  \n$ sudo mount_hfs -o rdonly /dev/disk27 /Volumes/Smash  \n$ ls /Volumes/Smash  \nDocuments           Pictures           Scratch space</code></pre>\n<p>That said… that <code>-o rdonly</code> parameter… in principle it shouldn’t be required, but I could <em>not</em> get macOS 27 to let me mount any HFS-on-CoreStorage volume as read-write – no matter what I did, it always fails with error “Resource busy” (EBUSY). I spent a lot of time trying to debug this, and could find <em>no</em> evidence of anything having the volume in question open (nothing in <code>lsof</code> etc).</p>\n<p>But wait, it gets worse.</p>\n<p>macOS 27 can’t even erase the volume. All the normal tools – <code>diskutil</code>, Disk Utility, etc – fail with that same “Resource busy” error.</p>\n<h2 id=\"workaround\">Workaround</h2>\n<p>Thankfully, with the help of Gemini 4 Argon, I did find a workaround. It’s convoluted, but takes only a few steps, thankfully.</p>\n<p>First, while if you try to delete the logical volume group it ostensibly fails, it doesn’t <em>completely</em> fail – it does actually delete the logical volume(s) within:</p>\n<pre><code>$ diskutil cs delete 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \nStarted CoreStorage operation  \nUnmounting Logical Volumes  \nDestroying Logical Volume Group  \nErasing disk10s2  \nnewfs_hfs: cannot create filesystem on /dev/rdisk10s2: Resource busy  \nMounting disk  \nCould not mount disk10s2 after erase  \nError: -69832: File system formatter failed  \n1 💣 $ diskutil cs list                                         \nCoreStorage logical volume groups (1 found)  \n|  \n+-- Logical Volume Group 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \n    =========================================================  \n    Name:         Smash  \n    Status:       Offline  \n    Size:         2000054960128 B (2.0 TB)  \n    Free Space:   -none-  \n    |  \n    +-&lt; Physical Volume 1B5A1754-184B-4F17-A797-BF69B4BB627F  \n        ----------------------------------------------------  \n        (No properties)  \n$ diskutil cs delete 0DC0EFB1-23CC-45BC-B37D-C1BBEBDAFCEB  \nStarted CoreStorage operation  \nDestroying Logical Volume Group  \nError: -69783: Unable to delete the CoreStorage Logical Volume Group</code></pre>\n<p>You still can’t destroy it completely, nor can you erase the physical volume yet – the “Resource busy” errors persist. But, the trick is to <em>restart</em> – after that, you <em>can</em> then erase the volume.</p>\n<p>So it seems that whatever broken thing is holding the physical volume (or logical volume group) in a ‘busy’ state is tied to the existence of the logical volume(s) therein, and once they’re deleted (and the machine rebooted) the bug stops being triggered.</p>\n<h2 id=\"call-for-better-workarounds\">Call for better workarounds</h2>\n<p>I’ve glossed over a <em>lot</em> of debugging and attempts I made to save the volume in-place, by either making it work as-is (even if only with e.g. hfsutils) or by converting it to APFS, but neither I nor Gemini 4 Argon could find anything that worked. It’s too late for me – I was forced to just delete all my HFS+ &amp; CoreStorage volumes and rebuild them painstakingly from backups – but if anyone finds a way, I’d love to amend this post, for the benefit of future readers.</p>\n<ol><li><p>The problem remains the same in macOS 27 – so <em>three</em> major macOS versions, at a minimum, where essential system update functionality has not worked. Sigh.  </p><p> <code>$ diskutil apfs convert disk27  \n Converting the volume on disk27 to an APFS Volume on an APFS Container  \n Started APFS operation on disk27 (Smash)  \n Converting HFS Volume to an APFS Container which will export one APFS Volume  \n The target is the Journaled HFS+ volume &quot;Smash&quot; on disk27 backed via CoreStorage on disk10s2  \n Checking booter partition disk10s3  \n The target is a data disk; it is not a macOS system disk  \n No APFS EFI driver found to install  \n Saving encryption context  \n The target is encrypted  \n Unmounting disk27  \n Starting conversion from HFS to APFS  \n Performing apfs_hfs_convert -x --verbose=0x400 /dev/disk10s2  \n Reporting post-conversion statistics  \n A problem occurred during conversion from HFS to APFS  \n APFS Converter exit code is 1  \n Aborted conversion in commit mode so will restore type  \n Setting type of disk10s2 to CS  \n Changing the physical disk partition type in shared mode  \n Partition modification attempt count was 1  \n Not mounting APFS Volume  \n Exiting conversion operations with error code -69860  \n Error: -69860: The underlying task reported failure on exit  \n Underlying error: 1</code><br />\n  <a href=\"#c63a9f61-72c1-4689-a06c-d132ac976f25-link\">↩︎</a></p></li></ol>","headings":[{"level":1,"text":"macOS 27 Golden Gate does not actually support CoreStorage (or HFS+) volumes","id":"macos-27-golden-gate-does-not-actually-support-corestorage-or-hf"},{"level":2,"text":"Details","id":"details"},{"level":2,"text":"Workaround","id":"workaround"},{"level":2,"text":"Call for better workarounds","id":"call-for-better-workarounds"}]}}