Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Is this normal to have?

haravikk said:
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.
Click to expand...

I can't answer you directly as I haven't pored through Apple's documentation for Yosemite. I can, however, offer that my 10.9 partition was left untouched and I could modify and delete my 10.9 partition from Disk Utility. Also, I can also offer that the issue reported by the OP, myself, and others has been reported as a bug since 10.7 Lion - via several OS installs, this is only the third time it's happened to one of my Macs.

There's a couple of links to my OP in the other thread - refer to Foskett's blog post, as it was for Lion at the time. That Apple hasn't incorporated some of those now-documented Terminal commands (in the BSD Manual) into Disk Utility has led me to surmise that what's occurred (in this thread) isn't a desired result.

Having to reboot, fire up Terminal and type in a couple of commands is only a minor PITA to me but there are some alarmed users here, including a few that indicated they had some time wasted by the old erase-and-install. As for me, I'll put my 10.10 partitions on an SSD from here on! :eek:
 
i814u2 said:
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:

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
                                 Unencrypted

Disk Utility shows:
System Drive​
System Drive​
Click to expand...

Interesting... so yours got converted to core storage also. :confused:
 
Tried using the terminal command...

So i have the same problem and tried using the same terminal command that BrettApple used but the process was stuck at 60% for 30 mins...
QemQ4bb.png


idk what to do.. :(

*EDIT: ok so i cancelled the command by pressing ctrl+c, rebooted to find out when i hold option, yosemite was still there, however i proceeded to boot to mountain lion, and voila, through disk utility, yosemite was gone and it was back to my Samsung SSD name, i was able to resize the partition so now my mountain lion occupies 100% of my ssd! cheers Weaselboy!

6RXJmEp.png


*EDIT 2: Welp, I now no longer have a recovery, when I boot and hold Cmd+R it directed me to Internet Recovery. since Im running ML atm BUT i do have the Mavericks upgrade downloaded (thru app store), will upgrading to Mavericks install a Mavericks recovery alongside upgrading my system to Mavericks?
 
Last edited:
Destructor1337 said:
Welp, I now no longer have a recovery, when I boot and hold Cmd+R it directed me to Internet Recovery. since Im running ML atm BUT i do have the Mavericks upgrade downloaded (thru app store), will upgrading to Mavericks install a Mavericks recovery alongside upgrading my system to Mavericks?
Click to expand...

Yes, just run the installer over top of your existing install and it will create a recovery partition. It will not erase your data, but backup first just to be safe.

I don't see how anything you did there would have erased your Mavs recovery partition though.
 
When installing Yosemite, FileVault is ticked by default, and unless you manually untick it during set up, it'll automatically encrypt your drive, thus the 2 macintosh HD's.

Easy to overlook if you're just flying through clicking next.
 
Weaselboy said:
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. :eek:

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.

Image
Click to expand...

This worked for me to erase the Yosemite partition, although I can't extend my main partition down, it looks like this:-

2cqd4wi.png


Any idea how to fix it?

Thanks.
 
steve23094 said:
This worked for me to erase the Yosemite partition, although I can't extend my main partition down, it looks like this:-

Any idea how to fix it?

Thanks.
Click to expand...

It looks like you should be able to there. If you select Macintosh HD in the left column there will it let you grab the /// at the bottom and pull it down?
 
Weaselboy said:
It looks like you should be able to there. If you select Macintosh HD in the left column there will it let you grab the /// at the bottom and pull it down?
Click to expand...

Yep, just realised that. Me being stupid, I was trying to pull down from the centre.

Thanks.
 
steve23094 said:
Yep, just realised that. Me being stupid, I was trying to pull down from the centre.

Thanks.
Click to expand...

Mine is doing this, I can delete the partition but when I resize and click apply it just reverts back to the size and there is blank space on the drive.
 
Weaselboy said:
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.
Click to expand...

I have the the Logical Volume Group despite only having one partition (and never having had 2 in the past).

daijholt said:
When installing Yosemite, FileVault is ticked by default, and unless you manually untick it during set up, it'll automatically encrypt your drive, thus the 2 macintosh HD's.

Easy to overlook if you're just flying through clicking next.
Click to expand...

I made sure to untick the box and have never had FileVault, but I still have the 2 Macintosh HDs (Logical Volume Group).
 
tl;dr most of it sorry. but i've got the OPs post, and NO I don't have FV on.
It's showing as Macintosh HD for both (one partition - the main), originally it was something like "250.14GB TOSHIBA or whatever they use" on Mavericks.

Is there someway to fix it easily (bet there was something originally and I didn't notice it, I don't want to kill my mac.)
 
mjm91 said:
Mine is doing this, I can delete the partition but when I resize and click apply it just reverts back to the size and there is blank space on the drive.
Click to expand...
Try adding a partition, I think it will just use that free space in the first partition, then click the minus symbol to delete it immediately. That should make that empty space useable in the first partition.
 
smartalic34 said:
I have the the Logical Volume Group despite only having one partition (and never having had 2 in the past).

I made sure to untick the box and have never had FileVault, but I still have the 2 Macintosh HDs (Logical Volume Group).
Click to expand...

Mine is the same way from a clean install on a blank drive. 1 partition and no FileVault, yet I Get Yosemite for drive name, and Yosemite for partition name.

It doesn't seem to cause a problem, but it kind of bugs me.
 
smartalic34 said:
I have the the Logical Volume Group despite only having one partition (and never having had 2 in the past).



I made sure to untick the box and have never had FileVault, but I still have the 2 Macintosh HDs (Logical Volume Group).
Click to expand...

mitchsaunders said:
tl;dr most of it sorry. but i've got the OPs post, and NO I don't have FV on.
It's showing as Macintosh HD for both (one partition - the main), originally it was something like "250.14GB TOSHIBA or whatever they use" on Mavericks.

Is there someway to fix it easily (bet there was something originally and I didn't notice it, I don't want to kill my mac.)
Click to expand...

crjackson2134 said:
Mine is the same way from a clean install on a blank drive. 1 partition and no FileVault, yet I Get Yosemite for drive name, and Yosemite for partition name.

It doesn't seem to cause a problem, but it kind of bugs me.
Click to expand...

Interesting... thanks for the info. With the previous DP versions it seemed like this was only happening if installed on a second partition, so now it looks like the beta 1 converts even a single partition into a core storage volume.

It does not really hurt anything, but if you want to convert it back you can run "diskutil cs list" (without the quotes) in Terminal to find the UUID of the last logical volume. Then run the command below substituting your real UUID to convert the volume back to a normal partition.

Code: 
diskutil corestorage revert FBDC2EE2-E850-4DD8-B271-51E1F5131E6B

That said, it may be that Apple did this for a reason, so it may be better to leave it alone. Other than not being able to resize the core storage volume, I don't see how it breaks anything.
 
Weaselboy said:
Interesting... thanks for the info. With the previous DP versions it seemed like this was only happening if installed on a second partition, so now it looks like the beta 1 converts even a single partition into a core storage volume.

It does not really hurt anything, but if you want to convert it back you can run "diskutil cs list" (without the quotes) in Terminal to find the UUID of the last logical volume. Then run the command below substituting your real UUID to convert the volume back to a normal partition.

Code: 
diskutil corestorage revert FBDC2EE2-E850-4DD8-B271-51E1F5131E6B

That said, it may be that Apple did this for a reason, so it may be better to leave it alone. Other than not being able to resize the core storage volume, I don't see how it breaks anything.
Click to expand...

Agreed - going to leave for now.
 
Looks normal to me. Here's mine. Getting rid of the partition when the public version of 10.10 is gonna be fun...
 

Attachments

  • Screen Shot 2014-07-27 at 1.30.47 PM.png
    Screen Shot 2014-07-27 at 1.30.47 PM.png
    176 KB · Views: 266
Miku:~ miku$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: Apple_HFS 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 214.1 GB disk0s2
3: Apple_HFS 35.4 GB disk0s3
4: Apple_HFS Recovery HD 650.1 MB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD 2 *35.4 GB disk1
Logical Volume on disk0s3
26C54EEC-FA8C-48CF-A085-B77E620FCF4B
Unencrypted
Miku:~ miku$


Any suggestions would be really welcomed. I have erased Mavericks and am stuck with Yosemite.
 
miku2016 said:
Miku:~ miku$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *251.0 GB disk0
1: Apple_HFS 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 214.1 GB disk0s2
3: Apple_HFS 35.4 GB disk0s3
4: Apple_HFS Recovery HD 650.1 MB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD 2 *35.4 GB disk1
Logical Volume on disk0s3
26C54EEC-FA8C-48CF-A085-B77E620FCF4B
Unencrypted
Miku:~ miku$


Any suggestions would be really welcomed. I have erased Mavericks and am stuck with Yosemite.
Click to expand...

Looks like Yosemite created a 35.4GB core storage logical volume at disk1. If you run the command below in Terminal it will convert that volume back to a regular volume that can be manipulated normally in Disk Utility.

Code: 
diskutil cs revert disk1
 
Duplicate partitions with Mac OS 10.8

When I installed 10.8 over 10.6 I had a similar problem. I got two main partitions and no Recovery partition. And as I recall, I couldn't do a clean install and repopulate the HD using my TM backup without the same result. Not knowing what else to do I reformatted the HD and drug over my data files.

I didn't have any further problems going from 10.8 to 10.9.
 
Weaselboy said:
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. :eek:

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.

Image

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
Click to expand...


Maybe I have a similar issue... I was wondering if anyone could help me with this... my thread is here:

https://forums.macrumors.com/showthread.php?p=20475141#post20475141
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back