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

Caution - Yosemite may screw up partitions.

I'm quite interested in this as well. Unfortunately I don't have the hardware for more testing. I personally think you can't compare this VM test to a real life test.

I know your time is limited but why you don't install Yosemite on a zeroed disk ? You have the hardware to evaluate and you will spend 2-3 hours for setting up a "dummy" BootCamp and for restoring your current BootCamp into this partition.

Then we would know more ;)

There is some logic behind the BootCamp theory because Core Storage is nothing else than a Logic Volume Manager and Bootcamp = Windows would not be able or willing to support the OS X LVM ( so I guess ), regardless whether the LVM creation is a bug or not.
 
Last edited:
theSeb said:
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.
Click to expand...



there is not 100% chance u get core storage volume
I upgraded my mavericks to yosemite preview 7 then 8 then 9 and 10 as well as GM 1 and GM2 and then I got core storage I dont know why, now I cant upgrade to official yosemite because of core storage and I cant partition or use bootcamp Im looking forward to get a new external hard this week and reformat everything hopefully it will get rid of core storage problem

in conclusion I dont think its all AES or Yosemite there must be something else in common for me and other users that we did and it created this, as well as AES and Yosemite ....
 
Last edited:
TENTACULA said:
there is not 100% chance u get core storage volume
I upgraded my mavericks to yosemite preview 7 then 8 then 9 and 10 as well as GM 1 and GM2 and then I got core storage I dont know why, now I cant upgrade to official yosemite because of core storage and I cant partition or use bootcamp Im looking forward to get a new external hard this week and reformat everything hopefully it will get rid of core storage problem

in conclusion I dont think its all AES or Yosemite there must be something else in common for other users that we did and it created this, as well as AES and Yosemite ....
Click to expand...

You cannot use a tool like parted to zero the disk ?
 
macenied said:
You cannot use a tool like parted to zero the disk ?
Click to expand...

Ultimate Boot CD (UBCD) works with my MacBookPro5,2 and includes PartedMagic – user-friendly.

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

macenied said:
…. I personally think you can't compare this VM test to a real life test.
Click to expand...

Agreed. Long ago I experimented with the GUI to FileVault 2 with VirtualBox. I didn't expect it to work, it didn't.

There is some logic behind the BootCamp theory because Core Storage is nothing else than a Logic Volume Manager and Bootcamp = Windows would not be able or willing to support the OS X LVM ( so I guess ) …
Click to expand...

That's reasonable.
 
I wasn't expecting the vm test to do anything, but it had to be done for scientific reasons.
 
grahamperrin said:
Ultimate Boot CD (UBCD) works with my MacBookPro5,2 and includes PartedMagic – user-friendly
Click to expand...

I did not know about this tools compilation - thank you for the info !

Here is another link for a toolset CD so that you can partition or create & restore disk/partition images while looking YouTube videos or reading macrumors during processing ( Firefox included ) ...

It's from a german Server, however default language is english.

http://www.chip.de/downloads/Parted-Magic_32391033.html
 
Last edited:
My partitions are fine
Fx42sbE.png
 
TENTACULA said:
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 :
/*
In my testing with 10.10 DP 7, it looks like the 10.10 DP 7 installer creates a CoreStorage volume as part of the 10.10 installation process on some Macs but does not create a CoreStorage volume on others. I was tipped off that the determiner for this behavior is whether or not the Mac's Intel processor has AES-NI support. If a Mac's processor has AES-NI support, the CoreStorage volume is created.



To help determine if a particular Mac's processor has AES-NI support, you should be able to use the following command:



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



Running that command should return "AES" (no quotes) on systems with processors that have AES-NI support. On systems with processors that don't have AES-NI support, no output should be returned.


*/




so yea thats the thing that causes it and my terminal answer is AES
Click to expand...

Just typed in that command and my Mac Mini does have AES support... But it was a cool theory! :)
 
I'm gonna file a bug report with Apple and see what happens regarding this issue, whether it's a bug or whether it is intentional for some reason.
 
libfvde

Weaselboy said:
… would be nice if Apple just came out …
Click to expand...

In the absence of information from Apple, you might find something relevant at

libyal/libfvde on GitHub

Library and tools to access FileVault Drive Encryption (FVDE) encrypted volumes​

The project is focused on encryption as an application of Core Storage, but it's possible that something there might hold an clue to the logic of what Apple is doing.
 
grahamperrin said:
... you might find something relevant at

libyal/libfvde on GitHub ...
Click to expand...

phew ... ;)

-----

IMO the whole point in this discussion is why it seems that Yosemite creates randomly ??? CoreStorage on some machines, even when the users never configured FileVault and/or Fusion.

I really hope it's a bug because I want to have knowledge and control about the structure and functionality of my storage.
 
macenied said:
… IMO the whole point in this discussion is why it seems that Yosemite creates randomly ??? CoreStorage on some machines …
Click to expand...

From what's in this topic, certainly there's a sense of randomness but I reckon that it's neither random nor a bug.

Discovering the logic (making things predictable, not random): yeah, that seems to be the key point. For some people, understandably the whole point.

Whilst I don't plan to follow this topic in depth, I suggest paying close attention to relevant lines in

/var/log/install.log

– typically best viewed in Console.app and (from experience, not particularly recent) I guess that lines of interest will be relatively near the beginning of the log.

Analysis may be easiest if there's an initial focus on logs from full installations that used the installer app released by Apple (not an initial focus on updates from any beta).
 
macenied said:
I see some people interested in this topic and trying to understand what's going on here, others are just rolling eyes. Now, what has been your contribution ?
Click to expand...
Read post 36 and a few others going back 2-4 months. Maybe if you took to read the thread, you'd know that.
 
Please find an excerpt of my MBP install.log attached.

It was an install on a zeroed disk and I created a one partition layout for the entire disk in advance of the installation. The disk is a non-Apple SSD ( Corsair ).

The log says it will not create CS because no CPU AES support.
 

Attachments

  • log.png
    log.png
    75.1 KB · Views: 192
macenied said:
Please find an excerpt of my MBP install.log attached.

It was an install on a zeroed disk and I created a one partition layout for the entire disk in advance of the installation. The disk is a non-Apple SSD ( Corsair ).

The log says it will not create CS because no CPU AES support.
Click to expand...

Nice find!
 
Well, well, well. Why did I forget to look in there!

MacPro install.log

Code: 
Won't convert to CS, machine is not a portable

rMBP 2012
Code: 
Won't convert to CS, an internal volume is formatted for windows

So, I think we can now assume that we know most of the puzzle

If there is no AES support, or the mac is not a portable, or bootcamp is present, then do not convert to CS.
 
Last edited:
theSeb said:
Well, well, well. Why did I forget to look in there!

MacPro install.log

Code: 
Won't convert to CS, machine is not a portable

rMBP 2012
Code: 
Won't convert to CS, an internal volume is formatted for windows

So, I think we can now assume that we know most of the puzzle

If there is no AES support, or the mac is not a portable, or bootcamp is present, then do not convert do CS.
Click to expand...

Agreed. Now we just need to know why.
 
theSeb said:
Well, well, well. Why did I forget to look in there!

MacPro install.log

Code: 
Won't convert to CS, machine is not a portable
Click to expand...

Which makes me wonder why it thinks my MP 5,1 qualifies as portable then... :)

And mine says

Code: 
Oct 16 16:35:55 Mac-Pro.local OSInstaller[462]: Won't convert to CS, volume is external

Yet it converted to CS anyway...
 
Last edited:
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