Caution - Yosemite may screw up partitions.

[theSeb]

Yosemite turns the volume into a core storage volume tat cannot be resized normally, and that nay be what is going on with you.

Enter the line below in Terminal and post up the out put so we can see what is going on.

diskutil cs list

Well, I have an interesting issue after the upgrade

rMBP:~ sebastianp$ diskutil cs list
No CoreStorage logical volume groups found
rMBP:~ sebastianp$

Running diskutil list instead

rMBP:~ sebastianp$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MBP                     349.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                150.2 GB   disk0s4

So , it would appear that the installer has not turned the volume into a core storage one. I tried booting into the recovery partition and it won't work - the status bar gets to half way and then it just sits there.

I am now going to try and delete the recovery partition, merge the partitions and reinstall Yosemite again to see if that helps to resolve this, unless someone has any better ideas on how to get the recovery partition working (2012 rMBP)

 

[jschoorl]

I am not quite sure if this happens during the upgrade to Yosemite (at least didn't noticed it before) and didn't mess with it, but my Fusion drive is broken. I noticed it because the performance was dramatically slower then before.

I have a late 2013 iMac with a 3TB fusion drive. In "about my Mac" the fusion drive shows up as two separate drives:

- Macintosh HD, 3TB Sata-disk, 2,14TB free of 3 TB)
- Untitled, 121 GB flash storage, 120,77 GB free of 120,99 GB

Anyone noticed this or even better has a solution?

 

[grahamperrin]

Respecting authors and giving credit

miserly

It's not miserly, I'm trying to help people. There's no suggestion that you or the original poster were unhelpful. The information is helpful and (hopefully) correct.

what private information ? … developer forums lol

That forum is private.

If the author had wished to publish, he might have published – and then posted privately with a link to draw attention.

You can't be certain that Apple, or the author, intended the information to be public. Generally, what was true in mid-September for a pre-release may be not true for a release in all environments. That said, there are only minor changes between the pre-release and release so I doubt that the limitations associated with Core Storage have changed.

Please understand, it was not a criticism aimed solely at you – I, too, am guilty of stretching the boundaries of what's acceptable within a confidentiality agreement – but generally, it's not good etiquette to publicly quote – verbatim and in whole without crediting the author – a private post, unless you have the express permission of the author.

(If you had said "quoted with permission" that should have been fine

 

[Weaselboy]

its not random accourding to what I found in the developer forums of apple...

Good info and thanks for posting this. It would seem to explain why core storage gets turned on for only some systems.

----------

Well, I have an interesting issue after the upgrade

rMBP:~ sebastianp$ diskutil cs list
No CoreStorage logical volume groups found
rMBP:~ sebastianp$

Running diskutil list instead

rMBP:~ sebastianp$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS MBP                     349.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data BOOTCAMP                150.2 GB   disk0s4

So , it would appear that the installer has not turned the volume into a core storage one. I tried booting into the recovery partition and it won't work - the status bar gets to half way and then it just sits there.

I am now going to try and delete the recovery partition, merge the partitions and reinstall Yosemite again to see if that helps to resolve this, unless someone has any better ideas on how to get the recovery partition working (2012 rMBP)

Yeah... no core storage for you.

I wonder if your CPU does not support AES-NI like TENTACULA discovered? If you run the command TENTACULA found in Terminal does it show AES support. Just curious.

It sure seems like Bootcamp causes issues with the Yosemite installs.

sysctl -a machdep.cpu | grep -E -o AES

 

[NateEssex]

Do you know if I would lose my partition?

Good info and thanks for posting this. It would seem to explain why core storage gets turned on for only some systems.

----------



Yeah... no core storage for you.

I wonder if your CPU does not support AES-NI like TENTACULA discovered? If you run the command TENTACULA found in Terminal does it show AES support. Just curious.

It sure seems like Bootcamp causes issues with the Yosemite installs.

sysctl -a machdep.cpu | grep -E -o AES

So, if I have a MacBook Pro (15-inch, Mid 2012), would I lose my partition also? I have Windows 7 installed on the partition with work stuff. I really don't understand any of the technical stuff above.

Thanks!

 

[Weaselboy]

So, if I have a MacBook Pro (15-inch, Mid 2012), would I lose my partition also? I have Windows 7 installed on the partition with work stuff. I really don't understand any of the technical stuff above.

Thanks!

I don't know that theSeb's Windows install is messed up, I was just commented that based on some earlier posts it seems like this whole core storage conversion business was doing odd things to Bootcamp.

If you have work on there you don't want to lose, it might be worth you getting something like WinClone to copy that Windows install. Or at least get your data onto a USB key or something.

 

[theSeb]

Yeah... no core storage for you.

I wonder if your CPU does not support AES-NI like TENTACULA discovered? If you run the command TENTACULA found in Terminal does it show AES support. Just curious.

It sure seems like Bootcamp causes issues with the Yosemite installs.

sysctl -a machdep.cpu | grep -E -o AES

So I did exactly as I said I would. For those interested:

rMBP:~ sebastianp$ diskutil eraseVolume HFS+ ErasedDisk /dev/disk0s3
(output removed)

rMBP:~ sebastianp$ diskutil mergePartitions HFS+ MBP disk0s2 disk0s3
(output removed)

Edit: please note that MBP above should be replaced with YOUR volume name. disk0s3 should correspond to the recovery partition and disk0s2 should correspond to your main volume (MBP in my case) . You will get all of this info from "diskutil list" . Do not do any of the above if you don't have backups are not comfortable about messing around with your Mac.

Then I reinstalled Yosemite on top of the current installation. I noticed that there was an extra restart this time.

Previously when holding ⌥ during startup I had MBP MBP Bootcamp

Now I have MBP BOOTCAMP Recovery-10.10

I am able to use recovery now and it is the Yosemite version.

Finally, CoreStorage still has not created a volume (2012 rMBP)

Running to check if AES is present (which I expected to have)

rMBP:~ sebastianp$ sysctl -a machdep.cpu | grep -E -o AES
AES

So I am quite confused.

----------

I don't know that theSeb's Windows install is messed up, I was just commented that based on some earlier posts it seems like this whole core storage conversion business was doing odd things to Bootcamp.

If you have work on there you don't want to lose, it might be worth you getting something like WinClone to copy that Windows install. Or at least get your data onto a USB key or something.

Bootcamp works... although let me double check right now, because I haven't tried since my last experiments above.

Edit: Yes, Bootcamp still works. I must say I have never had this much trouble upgrading OS X and I've written a bloody e-book with video tutorials on upgrading from Lion to Mountain Lion, so it's not exactly my first time.

 

[Weaselboy]

So I am quite confused.

Thanks for the follow up. Yes, this is odd. You think having Bootcamp there stopped it from converting to core storage?

I saw posts during the betas that Bootcamp was causing issues, so I'm wondering if in the final version Apple stopped converting to core storage if Bootcamp is present.

 

[Kimble Cheat]

Partitions

Quote: I discovered that Yosemite had somehow messed up the partitions, to the point that:....

Hi, I bought my mac air last yr, the 8g one...I may even be asking a dumb question here because it's my first mac and I'd never had a single problem with it until now with Yosemite(my battery life has disappeared by a third) I haven't massively explored the machine yet either-I write, so I just write stuff on it all over the place.
Not liking the battery thing I finally decided to explore and begin to understand things a little better.I came across the partition thing today...one is the flash memory..but the other one is almost totally full? And I dont understand whether this is right? or a problem? Or something to do with Yosemite..
Yours, the mac philistine


It's like buying an expensive car and never looking under the hood, so I'm changing.

 

[canuckle]

Weaselboy, I'm certainly not nearly as adept as most here, but I was able to reclaim my 'free space' partition that the Yosemite beta was installed on. Here are the details:

First, I erased the beta partition.
This created a partition of 'free space'.
Tried to delete the partition, would not commit.
Rebooted, tried again, no dice.
Tried to format empty partition to Mac Journaled, no dice.
Activated Internet Recovery, Disk Utility, formatted to Mac Journaled.
Rebooted, delete partition, no dice.
Turned off File Vault before bed, let it work.
This morning, I rebooted to LOCAL recovery (command +r). entered Disk Utility. Here I was able to pull down the main partition to recover the 'free space'. Now have my full drive back.

Like I said, not a particularly technical explanation, but HTH someone.

Thanks,

Mike

 

[theSeb]

Thanks for the follow up. Yes, this is odd. You think having Bootcamp there stopped it from converting to core storage?

I saw posts during the betas that Bootcamp was causing issues, so I'm wondering if in the final version Apple stopped converting to core storage if Bootcamp is present.

This is my suspicion right now. I am going to try update the nMP tonight, which also has bootcamp.

 

[theSeb]

Weaselboy, I'm certainly not nearly as adept as most here, but I was able to reclaim my 'free space' partition that the Yosemite beta was installed on. Here are the details:

First, I erased the beta partition.
This created a partition of 'free space'.
Tried to delete the partition, would not commit.
Rebooted, tried again, no dice.
Tried to format empty partition to Mac Journaled, no dice.
Activated Internet Recovery, Disk Utility, formatted to Mac Journaled.
Rebooted, delete partition, no dice.
Turned off File Vault before bed, let it work.
This morning, I rebooted to LOCAL recovery (command +r). entered Disk Utility. Here I was able to pull down the main partition to recover the 'free space'. Now have my full drive back.

Like I said, not a particularly technical explanation, but HTH someone.

Thanks,

Mike

This sounds familiar, since I have been having similar issues. I had Yosemite beta on a separate partition, but I deleted the partition a couple of weeks ago and went for the VM machine route instead, due to various issues that I had running two versions of OS X on the same volume, even though they were in separate partitions.

Long story short, after I got rid of the beta's partition I had a 250 GB Mavericks partition, 100 GB of free space and then 150 GB for Bootcamp, according to disk utility.

I kept trying to get the 250 GB partition to merge with the 100 GB of free space via disk utility with no result. It would start doing stuff, like it was actually going to do it and then when it was complete I would still have the 100 GB of free space.

In a moment of anger and frustration, I completely forgot about the terminal and trying to do it via there. Instead, I used my carbon copy cloner volume and booted into its recovery partition. I then delete the Mavericks partition and was able to create a new 350 GB partition. After that I booted into the CCC clone and cloned it back to the 350 GB partition on the rMBP.

Bootcamp was untouched, but it would not boot. So I used winclone to restore an image that I made just before I started all of this. Finally I had Mavericks (350 GB) and Bootcamp (150 GB) running.

The lesson here is to keep backups of everything before messing around

 

[canuckle]

The lesson here is to keep backups of everything before messing around

Yes indeed

 

[theSeb]

So, I have just done the update on a nMP with Windows 8 in Bootcamp.

No CoreStorage logical volumes and the best part is that the recovery partition has not been updated and is still the 10.9 version.

 

[Weaselboy]

So, I have just done the update on a nMP with Windows 8 in Bootcamp.

No CoreStorage logical volumes and the best part is that the recovery partition has not been updated and is still the 10.9 version.

Hmmm... so looks like Bootcamp does stop the core storage conversion.

 

[theSeb]

Hmmm... so looks like Bootcamp does stop the core storage conversion.

In the interest of science I am tempted to remove the bootcamp partition and try, but I just cannot justify the time and the hassle to get everything back right now. I do wish I hadn't given my Mini to my dad now.

I reckon that the speculation in the Ars Technica article about the link between this conversion to a CoreStorage volume and a replacement for HFS+ could be right on the money, so I am interested to know what does this mean for those of us with Bootcamp in the future.

 

[grahamperrin]

… the update …

From which build of the OS?

What approach did you take to the installation?

 

[campyguy]

A few posts in here and Siracusa's missive (I read the WHOLE article) still leave me feeling this whole Core Storage thing is a bug to be dealt with. My personal opinion, not speculation.

As for the "some guy" post cited/alluded to by TENTACULA - I disagree. Any time I see or hear "some guy" it means BS crap to me - cite it, show it to me, or go away and stop wasting my time. I had two rMBP test machines, one mid-2012 and one late 2013, both have AES-NI support. Testing of DP1-7 and Candidate builds 1-3 yielded non-CS results on my mid-2012 rMBP and CS results on my late-2013 rMBP. Installing the release build over the Candidate 3 build yielded CS results on both machines. I've seen it for myself, and I'll leave it to the rest of you to discover it for yourselves.

Siracusa wrote in the Installation section:
"[Update: Here’s one contradictory truth. Core Storage is not applied to all installation targets. For example, installing onto an external hard drive will not convert the volume to Core Storage.]"
I installed Yosemite in DP, GM, and final (whatever it's called) build, and I was able to yield a CS volume on a LaCie Rugged TB SSD drive whether it was partitioned or not. I also installed it on a Buffalo MiniStation Thunderbolt 1TB drive - the DPs did not create a CS drive; I didn't install the final build on this drive. So, I disagree with Siracusa's position here - and I put that out there in MR weeks ago.

I'd like to daydream as Siracusa did that Apple has something greater in mind. That these single-volume non-Fusion drives of mine were converted - to a revertible state, no less - without explanation by Apple leaves me a bit wanting for an explanation. That its as easy as executing two CoreStorage commands in Terminal and rebooting to revert to a non-CS state - on "some random" drives, but not all drives, I'm not convinced it's a "feature".

There's enough conflict and speculation here and the interwebs to keep me from allowing my non-Fusion drive Macs from remaining with converted Core Storage drives.

Taken out of context from Siracusa's article "Here we are in 2014, and HFS+ is still going strong. Yet here’s Core Storage once again, this time without any obvious purpose" - I do agree with this 100%.

I'd hazard a wager that there's going to be a change (read: bugfix) and Genius Bars will be a bit busy "fixing" this "feature". Just in time for the holiday shopping season...

 

[grahamperrin]

its not random accourding to what I found in the developer forums of apple
there was a guy who said this on one of the threads I found …

… That forum is private.

… can't be certain …

… As for the "some guy" post cited/alluded to by TENTACULA - I disagree. Any time I see or hear "some guy" it means BS crap to me - cite it …

https://devforums.apple.com/thread/245853 is as much as I can/should give in this instance.

Thanks for the additional information.

 

[theSeb]

From which build of the OS?

What approach did you take to the installation?

From the last released version of mavericks to the release version of Yosemite. No DP or beta versions have ever been installed on this machine.

It was a pure upgrade - i.e. Ran the Yosemite installer from mavericks.

 

[macenied]

I want to confirm that

- on a computer without CPU AES-NI Support &
- zeroed ( completely erased ) HDU / SSD

Yosemite does not create a core storage volume.

I installed Yosemite first ( 1 Partition, entire disk ) and after that BootCamp using the Yosemite BootCamp assistant. Recovery partition is created as well and accessible via Boot Manager ( <Option> key on Startup ).

 

[KoolAid-Drink]

Installed Yosemite on a 2011 MBP with three partitions set up (all three of them empty - completely fresh install): OS, Data, and Time Machine. 10.10.0 I can confirm, converted to CS. It took about five seconds to revert.

I'm convinced this is a bug. If it wasn't a bug, it would be applied to EACH installation configuration. As of now, it seems to be random, and does not seem to jive with any specific configuration. There would also be documentation of some kind regarding the change in installation operations.

So, this may be a harbinger of a new file system, or may be a bug. As it's existed (to lesser extent) since 10.7, my gut tells me it's a bug that Apple forgot/neglected to fix.

 

[salkin]

Hey guys,

I desperately need help. Since Yosemite was released I wanted to start using Fusion Drive instead of separated SSD & HDD. I found instructions online but they didn't work for me.

I'm not sure if this is right thread but could anyone help me with this?

Edit I found fix

 

[theSeb]

https://devforums.apple.com/thread/245853 is as much as I can/should give in this instance.

Thanks for the link, but it does not provide any new information, or explanations.

Both of the Macs I have used have AES support, yet no CoreStorage volume has been created. Any ideas on why this is? Is it because of the Bootcamp partition?

 

[theSeb]

Just a little update, because I am quite interested in this.

Perhaps it is not a reliable test, but I just upgraded a Mavericks virtual machine to Yosemite. Terminal tells me that the virtual machine supports AES and the partition layout is simple without any complications, yet no CoreStorage logical volumes have been created.