I upgraded to OS X Yosemite yesterday and I noticed this under disk utilities... I noticed that I had two "Macintosh HD" drives. I didn't notice this in OS X Mavericks. I hope this isn't a stupid question, but I hope I can get some answers. Thanks!
![kYaGmfZ.png]()
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Is this normal to have?
- Thread starter GoldenChild
- Start date
- Sort by reaction score
Thank you man, so don't even bother to do anything right? Haha. I was freaked out for a bit.
You have Filevault encryption turned on and with FV on, that is how the disk looks in Disk Util. This is not new to Yosemite. You just did not notice it before.
Here is mine with FV on in Mavs.
----------
Only if you have Filevault encryption turned on.
Do you have Filevault encryption turned on like the OP? If you do, that is normal and existed before Yosemite.
Nope - as I said it sonly changed since update, doesn't bother me though.
However I thin it may be a bug I have like 150GB of 'free space' that I can't format or do anything with lol - will have to try sort out after full release.
I have an entirely different issue, but didn't feel like making a new thread. I'll post a photo in a while.
I created a new partition on my SSD with Disk Utility like usual for the previews, installed 10.10 to the new partition, and after playing with it, rebooted back to mavericks. Now here's where the issue starts. My drive shows up as a logical volume with my two partitions, one Mavericks, one Yosemite. But, I cannot edit, resize, or delete either of them. Normally after playing around with it for a while, I delete the partition I installed the preview on. But the option is grayed out. This happens from the recovery partition as well as booting from a Mavericks USB drive. Not sure what's up?
Anyway, on to this topic, here's how it looks in Snow Leopard, since I'm using my BlackBook for the time being...
![kkN1aJu.png]()
Screen Shots:
Partitions
![GOzaGE3.png]()
SSD:
![dG9mcny.png]()
Yosemite:
![b3fm6mR.png]()
I can see that Yosemite is a volume by it's mount point, but I just want to get rid of it...
I created a new partition on my SSD with Disk Utility like usual for the previews, installed 10.10 to the new partition, and after playing with it, rebooted back to mavericks. Now here's where the issue starts. My drive shows up as a logical volume with my two partitions, one Mavericks, one Yosemite. But, I cannot edit, resize, or delete either of them. Normally after playing around with it for a while, I delete the partition I installed the preview on. But the option is grayed out. This happens from the recovery partition as well as booting from a Mavericks USB drive. Not sure what's up?
Anyway, on to this topic, here's how it looks in Snow Leopard, since I'm using my BlackBook for the time being...
Screen Shots:
Partitions
SSD:
Yosemite:
I can see that Yosemite is a volume by it's mount point, but I just want to get rid of it...
Last edited:
It says logical volume group when you have that top Yosemite selected, and that leads me to believe you turned on Filevault in Yosemite. If you select the lower Yosemite does it say Encrypted Logical Partition for Format: in DU.
Enter the command below in Terminal and post up the output.
Code:
diskutil listIt all seems to stem from core storage and Yosemite seems to be using it differently than past releases. I don't use fire vault, and It's not a fusion drive. Just an SSD in the optical bay, and my HDD. I'll have to read up on it as I haven't really looked into it all that much.
Here's what diskutil put out.
![]()
It's not a huge deal, because I'll probably do a full reinstall when the public beta comes out anyway, and again when the final release is out. Since my data is on my HDD it's unaffected. But it's still interesting.
Here's what diskutil put out.
It's not a huge deal, because I'll probably do a full reinstall when the public beta comes out anyway, and again when the final release is out. Since my data is on my HDD it's unaffected. But it's still interesting.
This is odd. That is making the new Yosemite partition look just like a Fusion logical volume. Look at this post of a DU with Fusion. Although your diskutil list output is different than a true Fusion drive.
So in Mavs you just shrunk the main volume then added the new one at the bottom, then installed Yosemite to the new volume?
You should be able to kill that Yosemite volume with the "diskutil cs delete" command. Run "diskutil cs list" to ID the UUID of the volume. Give this a read. It describes how to kill a Fusion volume, but the same steps will apply to killing that core storage volume.
Make sure you have a good backup first in case this goes sideways.
Edit: Forum member BrettApple was kind enough to capture the Terminal commands he used in his post here showing the steps I described above.
From Brett's screenshot below you can see how he used "diskutil cs list" to find the correct volume UUID to kill then ran "diskutil cs delete" with the UUID to remove the Yosemite core storage volume. Afterwards Disk Utility can be used to expand your main partition into this now empty space.
EDIT2: Much simpler method... if you installed Yosemite on the first drive in your Mac, running the command below will turn off the core storage.
Code:
diskutil cs revert disk1
Last edited:
For what it's worth, this happened to mine also. I shrunk my main Mavericks volume and created one just for Yosemite. After the install it's showing just as the OP (like a FileVault or Fusion drive logical volume) except with two partitions.
It's worth noting that this happened on my machine with an SSD and a HDD in the optibay.
I've also installed the beta on another machine with only a single SSD and it did NOT do this odd volume management.
It's worth noting that this happened on my machine with an SSD and a HDD in the optibay.
I've also installed the beta on another machine with only a single SSD and it did NOT do this odd volume management.
For what it's worth, I have a 2012 MBA with just one SSD installed, nothing else, and I got the same problem.
I shrunk my Mavericks partition and created a new clean partition on which to test Yosemite. The result is this:
I shrunk my Mavericks partition and created a new clean partition on which to test Yosemite. The result is this:
Attachments
I had my SSD turned into a logical volume by the install of Yosemite on a new partition too. See my post in that thread. I hope it helps: https://forums.macrumors.com/posts/19207476/
Perhaps this means that Yosemite now partitions all HFS volumes (or at least system volumes) with Core Storage by default? I wonder if there are new Core Storage features we haven't heard of yet that might suggest why they're doing this? I have my fingers crossed for data integrity features, but I would have thought they'd have mentioned that somewhere.
It could be a change to get rid of the need to restart to enable FileVault encryption actually, as having the volume as Core Storage already should mean it can just store the key(s) and start encrypting right away.
It could be a change to get rid of the need to restart to enable FileVault encryption actually, as having the volume as Core Storage already should mean it can just store the key(s) and start encrypting right away.
What is odd though is it only seems to do this for people that install on a second partition. I have not seen any reports of this happening when Yosemite is installed on the only partition on a drive like would be the more common setup for a user.
I have a similar setup now and I did not change my partition scheme.
I did, however, upgrade over my Mavericks install.
This is my 'diskutil list' output:
Disk Utility shows:
I did, however, upgrade over my Mavericks install.
This is my 'diskutil list' output:
Code:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_CoreStorage 255.2 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS System Drive *253.4 GB disk1
Logical Volume on disk0s2
A4128CCA-0DC8-4EC3-93F3-A1DEF0FFE1E8
UnencryptedDisk Utility shows:
System Drive
System Drive