You will need to boot from either an external drive of some sort or from Internet recovery then erase the entire disk, not just the Yosemite volume.
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.
Caution - Yosemite may screw up partitions.
- Thread starter yjchua95
- Start date
- Sort by reaction score
You will need to boot from either an external drive of some sort or from Internet recovery then erase the entire disk, not just the Yosemite volume.
The released build still converts the drive to CoreStorage.
I have absolutely no idea why they're doing this, maybe it's something to do with Filevault? Yosemite runs fine without it (as shown when you install on a raid array).
http://arstechnica.com/apple/2014/10/os-x-10-10/
The Arstechnica review here speculates a bit about it. Best theory I have seen.
Hopefully Apple will put up a tech support article on this soon.
Weasel,
I want to do a clean install since I have had all the betas on the drive. Currently, file vault is turned on. Do I need to decrypt the drive first, before doing a fresh install? My password won't be changing and I have the vault key printed out if need be.
I want to do a clean install since I have had all the betas on the drive. Currently, file vault is turned on. Do I need to decrypt the drive first, before doing a fresh install? My password won't be changing and I have the vault key printed out if need be.
i updated to yosemite from mavericks i had a windows partition with bootcamp installed. the only thing that isn't working for me is the tap to click and the tab isn't there under the bootcamp portion of my windows for me to change this option however every other option still remains there
so you are saying if I format everything and install yosemite again it will convert my disk to corestorage and so i cant partition my disk and use bootcamp to install windows?
I just upgraded my Mavericks install and it didn't convert to a CoreStorage volume.
When I did a clean install of the PB however, that one was created as a CoreStorage volume. I've had a better experience with the release/upgrade as compared to a clean install of the PB (not surprisingly though).
If the CoreStorage volume were critical, I think it would have been forced during the upgrade too.
When I did a clean install of the PB however, that one was created as a CoreStorage volume. I've had a better experience with the release/upgrade as compared to a clean install of the PB (not surprisingly though).
If the CoreStorage volume were critical, I think it would have been forced during the upgrade too.
Yeah, I'd expect Core Storage to be used for clean installation and in some other environments.
Partial incompatibility with apps such as Disk Utility, lack of documentation and so on … such things can be very inconvenient and/or frustrating, but my best guess is to accept the constraints of Core Storage within the operating system versions as we currently know them.
"… in the absence of any contradictory truths, I choose to believe that this default application of Core Storage is at least partially intended to lay the groundwork for a future in-place conversion of HFS+ volumes …"
For Core Storage: it's reasonable to assume that refusing what's currently offered will make it relatively difficult to accept a future offer.
For what it's worth, I continue to wonder about 'Location independent files'. I gained insider knowledge that threw me off that particular scent, but it doesn't stop me from sniffing around.
I doubt that many people have noticed, but with Yosemite there is explicitly a 'legacy' aspect to (at least) HFS Plus. More on this later.
Ok I'm really lost. I fresh installed Yosemite to my MacBook Air. But now I've got half my hard drive space and can't resize the partition. Anyone know how to fix this? Photos added. First photo is the installed stuff and the second shows a grayed section that I can't seem to mess with at all. I try and format it but it doesn't do anything. I just want my one hard drive of a 128 as one partition again.
Yep. That's definitely a core storage logical volume.
You can revert it to get partitions back to normal by running these 2 commands in terminal.
diskutil cs list
and then
diskutil coreStorage revert lvUUID
where lvUUID is the last lvUUID reported by the previous Terminal command.
Then restart for everything to get back to normal after you have run these commands in Terminal.
You can revert it to get partitions back to normal by running these 2 commands in terminal.
diskutil cs list
and then
diskutil coreStorage revert lvUUID
where lvUUID is the last lvUUID reported by the previous Terminal command.
Then restart for everything to get back to normal after you have run these commands in Terminal.
No guarantees. You're looking at a single-volume Logical Group (LG), similar to what I've encountered on my rMBP but with one difference. I deleted the second (lower) partition before installing Yosemite, but was left with an LG nonetheless after the install.
Read the post #36 in this thread (https://forums.macrumors.com/posts/19207476/) and #31 above it. I ran the first command, and then the second - I was left with an LG with one partition, similar to what you're seeing but mine was using up the entire drive, AND, mine was "revertible". Restarting my Mac left me with a typical drive configuration in which I can add/delete partitions again. As I wrote in #36, if your drive is not revertible, wiping and starting over is likely your best and only option (besides dealing with it as it is, which I don't recommend).
I'm not happy with being left with an LG, and I saw it after installing the GM and again with the final installer - I'll likely end up wiping the drive and installing Yosemite again over the weekend. FWIW, I installed 10.10 on a 2012 rMBP and it went as expected. I believe that there's a bug in the installer(s) - seeing an LG on a single-partition, non-Fusion drive isn't what I expect. You might consider doing the same. It was a beta-related issue, and I rolled craps on this one...
Ok guys I was able to install the os on 60 gb partition but still can't get to the other 60... Which isn't listed at all. And I can't resize the one I'm currently on. What should I do next? Thx
I don't have anything on this machine so if I need to dump it all I will do that and start fresh again. I'm just very lost on how to get the rest of the drive back. Thx
I don't have anything on this machine so if I need to dump it all I will do that and start fresh again. I'm just very lost on how to get the rest of the drive back. Thx
Last edited:
As long as you erase the entire disk and not just the os partition, the FileVault volume will be erased and you will be starting new. So no need to turn off encryption.
----------
Just run the command below to turn off core storage then you will be able to resize the volume.
diskutil cs revert /
Disconnect any other drives before you do this.
Thanks for the info, Weasel. I will keep that in mind for next time. To be safe, I turned off file vault last night before installing, just in case...
Just wanted to say thanks for this.
I just did a clean install of Yosemite to my 2014 MacBook Air (upgraded from Mavericks using a USB installer) and had the same issue as tkukoc (both the SSD and the partition were named Macintosh HD).
This terminal command + reboot appears to have solved the problem.
Is this the best way to solve this or would I be better off doing something else? I only ask because my recovery partition isn't showing either. Did I do something wrong during the installation? Is this a bug or did apple intend for Yosemite to install this way?
Thanks again
You did not do anything wrong and this is by design. There has not been anything official from Apple that I have seen, but the best theory I have seen was in the John Siracusa review on Arstechnica here. Excerpt below.
Unless you have some need to resize the install partition, there is no need to turn off core storage.
Enter the command below in Terminal and it will show if you have a recovery partition.
Code:
diskutil list
But I wonder why it seems to happen randomly though. For example, I upgraded both my Mac Mini 2011 and Macbook Air 2013. The Mini was not converted to Core Storage but the Air has.
Neither have File Vault enabled.
Neither have File Vault enabled.
That is curious. How were they both configured? Single drives and single partitions with everything just a standard setup?
I wasn't very clear before but I was referring to actually being able to boot from the recovery partition (I knew the recovery partition existed but it wouldn't show up in the boot manager).
When I tried to enter the recovery partition, it was actually before I reverted from CoreStorage (used "diskutil coreStorage revert lvUUID" terminal command as described in previous post by tywebb13).
This command actually solved the recovery partition problem as well (recovery partition now appears / works exactly as it should in the boot manager).
Just figured I'd mention that as I'm sure somebody else will stumble across this thread with the same problem.
Anyway, thanks for the additional info and clearing that up.
Under Yosemite with core storage on, an option key boot will not show the recovery partition as a boot option, but it four do a command-r boot it will boot from the recovery partition. I believe what you experienced is normal.
Cross reference
As promised:
Storage and file systems, HFS and legacy, kSKDiskRoleLegacyMacData and kSKDiskTypeHFS
As promised:
Storage and file systems, HFS and legacy, kSKDiskRoleLegacyMacData and kSKDiskTypeHFS
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
+1
for finding the information – I bookmarked it privately a couple of weeks ago, couldn't relocate it yesterday (seeking 'Core Storage' but not 'CoreStorage') – but sorry,
-1
for publicly quoting from a discussion that is not public.
Here's the item that was linked from that private post:
Intel® Advanced Encryption Standard Instructions (AES-NI) | Intel® Developer Zone (2012-02-02)
what private information ? its a thread for everyone in developer forums lol and the guy who said it was trying to help so dont be jelous or miserly
and you are not in charge for anything so its not your information
and Im trying to help people with their problems