Skip to content

Revert Mac OS X Yosemite Core Storage Back to Mac OS Extended HFS+

My Macbook Pro’s hard drive died recently, again. The Apple Store had to order the replacement Hitachi 750GB hard drive which took several days. I have a suspicion that Apple is using refurbished hard drives because it has just been two months since the last hard drive replacement. Hitachi is a brand I can trust… to fail quickly… because in addition to these two failures, when I first got my brand new Macbook years ago, the Hitachi drive died within three months. This time, I decided to install a Samsung EVO 850 500GB solid state hard drive to avoid having to visit the Apple Store again.

I also decided to do a fresh installation using the latest Mac OS X 10.10 Yosemite version. When I attempted to partition the hard drive into a Mac OS X Yosemite, a Windows 7 Boot Camp, and a shared FAT32 partition, I found that I couldn’t merge or resize the Mac partition to create the shared FAT32 partition using either Disk Utility or the diskutil command line.

The problem is that Yosemite installs the Mac OS X partition using a new Core Storage volume manager, which in turn uses the HFS+ (aka Mac OS Extended) file system. Unfortunately, Apple has not yet updated the Disk Utility or diskutil command line to resize, merge, or delete a Core Storage volume. Boot Camp does know how to resize the Core Storage volume correctly though. (Supposedly, there is an undocumented “diskutil coreStorage resizeVolume” command that supports resizing a Core Storage volume, but I hesitate to use it. And I couldn’t find an undocumented command to merge a Core Storage volume with a blank partition.)

Run the Terminal app and execute the “diskutil list” command to show the Core Storage volume (under “/dev/disk0”), which wraps the old HFS+ partition (under “/dev/disk1”).


The Core Storage volume manager is the basis for Appleโ€™s Fusion Drive technology, which is used to present several partitions on multiple drives as a single logical volume. Because I had only one hard drive on my Macbook, I didn’t need that function. (I can see using the Fusion Drive feature on a server which usually has more than one hard drive.) Thankfully, I found a way to convert the Core Storage volume back to a plain old HFS+ partition. Note that this method only works if the Core Storage volume is not encrypted.

To start, you need to find the Core Storage Logical Volume identifier used by the wrapped HFS+ partition. It is the long alpha-numeric string (“1FC06AF9-EED2-4066-BE3F-FE47166A2190” on my machine) listed under the HFS+ partition (“/dev/disk1/”) in the “diskutil list” command output above.

You can also find the Logical Volume identifier and encryption status by running the “diskutil cs list” command in the Terminal app.


Locate the bottom-most “Logical Volume” entry which has the identifier listed. Underneath that is the “Revertible: Yes (no decryption required)” line which indicates that the volume is not encrypted and can be reverted.

Once you have the Logical Volume identifier, you can revert the Core Storage volume back to a plain HFS+ partition using the “diskutil coreStorage revert” command like so:


You will need to reboot the Macbook. If you don’t reboot and run the “diskutil list” command, it will incorrectly show the logical volume (under “/dev/disk1”) even though the Core Storage has been replaced by HFS+ (under “/dev/disk0”).


Once the old HFS+ partition was back in place, I was able to delete, merge, and resize to my heart’s content. The solid state hard drive makes Mac OS X blazing fast; I regret waiting so long before installing one.


  1. Wayne Chia

    Hi Chanh,

    Like you, I partitioned my 512GB SSD into 3 partitions just so that I can have a shared partition that both Mac and Windows can access. Of course, I had to learn the hard way how easily OS X corrupts ExFAT partitions.

    I finally resorted to formatting my shared partition in NTFS and using Paragon NTFS to access the shared partition. However, I am still not really satisfied with this arrangement because I hibernate my windows partition a lot and there are some issues with files missing if OS X were to write to a partition that is hibernated.

    At this point in time, I am considering switching the shared partition to FAT32. I hope you don’t mind sharing:

    1) If you are still using FAT32 for your shared partition and how has the experience been so far.

    2) Do you have issues with files disappearing when you are writing to the FAT32 partition in OS X while the Bootcamp partition is in hibernation state?

    Your feedback is much appreciated ๐Ÿ™‚


    • Chanh

      Hi Wayne,

      So far, I haven’t had any issues with Mac OS X using FAT32 partition. No missing files or corruption. It is pretty solid. The only annoyance is the proliferation of .DS_Store files that Mac OS X puts everywhere.

      I’ve only used the Windows Hiberation a few times and did not notice any problems.

      Actually, I went further and converted the FAT32 partition to a Truecrypt 7.1a encrypted FAT32 partition. After login on Windows or Mac OS X, I would mount the Truecrypt partition. I don’t think this affects anything because after mounting, it looks like a normal FAT32 partition to both Windows and Mac OS X. I did this so that if the Macbook is stolen, the data on the FAT32 partition will remain secure.

      Regards, Chanh

  2. Wayne Chia

    Hi Chanh,

    Thanks for sharing. Interesting point on the Truecrypt encryption. Just a few questions:

    1) Does the encryption / decryption affect the overall performance of the drive?

    2) What does the encrypted drive look like in Windows / OS X before mounting / decryption? Does it show up as a normal mounted drive (which cannot be accessed) or it doesn’t even show up as a drive at all?

    Cheers, Wayne

    • Chanh

      Hi Wayne,

      Truecrypt encryption/decryption didn’t affect the speed for me at all. I’ve only used it on Core i5 Macbooks so if you have that or better, you should be okay. I’ve used Truecrypt on my Core 2 Duo Windows desktop in the past and don’t remember any slowdown.

      The encrypted partition will show as unrecognized/unformatted under Windows or Mac OS X. Once Truecrypt decrypts the partition, it will show up as a regular FAT32 partition. Under Windows, the drive letter is assigned as part of the Truecrypt decryption process.

      Regards, Chanh

  3. Wayne Chia

    Hi Chanh,

    Thanks for sharing. Sounds like a solid option. Will keep it in mind. You’ve been a great help ๐Ÿ™‚

  4. Glenn Petrie

    What happens if it says “Revertible: No”?

    • Chanh

      Hi Glenn,

      I think “Revertible: No” means that the volume is encrypted and I don’t think you can revert an encrypted volume. Do you have FileVault turned on for that volume? If FileVault is on, try turning it off. Hopefully that line will turn into “Revertible: Yes (no decryption required)”. Once you finish reverting the volume back to Extended HFS+, you can then turn FileVault back on again.

      Let me know how it goes,

  5. Alex Zavatone

    You’re a lifesaver, Chanh.


Leave a Reply

Your email address will not be published.