Caution - Yosemite may screw up partitions.

[rohithbasu]

bootcamp

don't know if anyone mentioned this, but yosemite also screws up the bootcamp partition and you cannot install windows via bootcamp fresh if you are running yosemite because of the way the partitions are structured in yosemite (core storage stuff ?)

 

[grahamperrin]

… all main HD's PASSED and no errors or bad sectors. …

Thanks.

If bad blocks were dealt with at the Core Storage level, then the logs of such events (written by OS X) are probably no longer available.

In SM.A.R.T., what's the count of reallocated sectors? Zero, or greater?

Does anything in the S.M.A.R.T. logs indicate that, for example, the disk temperature rose unusually high on two or more occasions?

 

[crjackson2134]

So, how does one do an install of Yosemite without the core storage voodoo?

Also, if I do an upgrade instead of a clean install, does that also force core storage?

 

[campyguy]

So, how does one do an install of Yosemite without the core storage voodoo?

Also, if I do an upgrade instead of a clean install, does that also force core storage?

First answer: I have no idea - my recent installs of the DP5 yielded CS volumes on 6 out of 10 drives, where using the DP1 installer yielded CS volumes on 10 out of 10 drives.

Second answer: Since there hasn't been an update to the DP5 installer, I can't give you a straight answer. Installing updates over DP1 did not change the type of drive once I reverted the CS drive.

My recommendation: Wait, if those Terminal commands instill trepidation. Apple's going to issue updates to of GMs of iOS 8 and Yosemite very shortly. I've already restored all of my iOS devices and deleted all, but one, Yosemite DP partition (the one partition I'm typing this on...). I won't spend any more time on iOS 8 or Yosemite until the GMs come out. But, that's just me.

 

[grahamperrin]

… Apple's going to issue updates to of GMs of iOS 8 and Yosemite very shortly. …

For Yosemite: maybe a full installer, but I would not expect the next few days to bring the golden master.

 

[antonis]

Anyone experiencing the below symptom (DP6) ?

Holding option key during boot (that is supposed to bring up the partitions/disks screen) takes about 2-3 minutes (or even more) to show up. That's after upgrading from DP5 to DP6.

Also, in the aforementioned screen, I see 2 "Macintosh HD" volumes now. Should I suppose that the volumes are messed up now ?

 

[tywebb13]

Did you install the yosemite recovery update 1? That renamed the yosemite recovery partition to the same name as the yosemite partition. The workaround is here: https://forums.macrumors.com/threads/1756752/

 

[antonis]

Did you install the yosemite recovery update 1? That renamed the yosemite recovery partition to the same name as the yosemite partition. The workaround is here: https://forums.macrumors.com/threads/1756752/

Indeed, I've installed the recovery update 1. Thank you, I'll use the workaround you linked. However, I'm not sure this issue is also responsible for the huge delays when booting with the "option" key pressed. Or could it be ?

 

[grahamperrin]

… Holding option key during boot (that is supposed to bring up the partitions/disks screen) takes about 2-3 minutes (or even more) to show up. …

That's probably not a Yosemite partitioning issue.

I suggest beginning a separate topic with relevant details (at least, output from diskutil list). I have a hunch that diagnosis will be possible without breaking the confidentiality agreement.

 

[antonis]

That's probably not a Yosemite partitioning issue.

I suggest beginning a separate topic with relevant details (at least, output from diskutil list). I have a hunch that diagnosis will be possible without breaking the confidentiality agreement.

Yes, it seems so. Once I get rid of the partitioning issue that caused by recovery update, and if the problem persists, I will open a new topic for this. It's certainly a weird one.

 

[campyguy]

Also, in the aforementioned screen, I see 2 "Macintosh HD" volumes now. Should I suppose that the volumes are messed up now ?

They're *likely* not messed up, you're seeing a Logical Volume naming scheme - assuming you do not have a Fusion Drive, follow the instructions earlier in this thread, and - if the new structure is revertible - the results of those two commands will restore the drive's naming scheme and properties. My LVs have been named "Yosemite" with partitions of "Yosemite" and "Macintosh HD", after the commands I get my disk name back with the partitions named as I intended. Cheers.

----------

For Yosemite: maybe a full installer, but I would not expect the next few days to bring the golden master.

Agreed. I was actually hoping for the GMs over the weekend. With the iTunes Festival starting today (I'm waiting for deadmau5 on my ATV) Apple's servers are going to get hammered. But with the iTF on, I'm a happy camper...

 

[tywebb13]

There are really 2 problems.

1 is that the yosemite installer may create unwanted logical volumes which is the main subject of this thread and can be fixed by various means discussed here.

But the other one was that there was a yosemite recovery update which prevented the yosemite recovery partition from showing up in the startup manager.

They are 2 separate issues, the latter of which is solved in this thread: https://forums.macrumors.com/threads/1756752/

 

[grahamperrin]

They're *likely* not messed up, you're seeing a Logical Volume naming scheme …

Yeah, I can not think of a Core Storage configuration that could take more than three minutes to appear in Startup Manager.

… if the problem persists, I will open a new topic for this. …

antonis: considering the possibility of a hardware problem – unrelated to Yosemite – you might like to begin that topic sooner rather than later.

 

[campyguy]

Yeah, I can not think of a Core Storage configuration that could take more than three minutes to appear in Startup Manager.

Yeah, I didn't address the slow startup. On purpose. So, yeah.

 

[antonis]

They're *likely* not messed up, you're seeing a Logical Volume naming scheme - assuming you do not have a Fusion Drive, follow the instructions earlier in this thread, and - if the new structure is revertible - the results of those two commands will restore the drive's naming scheme and properties. My LVs have been named "Yosemite" with partitions of "Yosemite" and "Macintosh HD", after the commands I get my disk name back with the partitions named as I intended. Cheers.

I confirm that by following the procedure described for re-creating the restore partition, the volumes appear normal once more (that is, the boot partition is named Macintosh HD and the restore partition as "Restore 10.10").

Yeah, I can not think of a Core Storage configuration that could take more than three minutes to appear in Startup Manager.

antonis: considering the possibility of a hardware problem – unrelated to Yosemite – you might like to begin that topic sooner rather than later.

I have to agree here. The workaround didn't make anything for the delay issue. Therefore, I'm not sure if I should open the topic in the Yosemite thread, but I'll start from there. However, I do have a hope that it might still be a Yosemite issue as the new OS certainly makes changes to the EFI as well (the black boot screen instead of the gray one, the lack of boot sound etc. I assume are changes to the EFI).

 

[grahamperrin]

… I'm not sure if I should open the topic in the Yosemite thread, but I'll start from there. …

Thanks. Got it:

Startup manager (holding "Option" key at boot) takes over 2 minutes to show up

– my reply is there.

 

[antonis]

Thanks. Got it:

Startup manager (holding "Option" key at boot) takes over 2 minutes to show up

– my reply is there.

I am the one that should be saying "Thanks". I'll reply as soon as I get back home where the machine is.

 

[crjackson2134]

Two Terminal commands assessed and fixed the issue for me in about 10 seconds:

1. First, the "diskutil cs list" command yielded two critical pieces of information - that the volume was Revertible and the lvUUID of the volume I wanted to revert. I have always used the last lvUUID for the next step.
2. Second, the "diskutil coreStorage revert lvUUID" (where lvUUID is that reported by the previous Terminal command) restored both partitions to the Mac OS Extended (Journaled) format that I'd set them up with.

No erasing necessary. This works on single and multiple partition volumes. You may need to enter in your password for protected drives - look at the two links for additional information regarding Terminal commands. I can't offer advice on non-revertible volumes.

Thanks for this, I have Yosemite installed on a separate drive, and from a clean install it produced a CoreStorage volume giving me all the same annoyances that everyone has reported.

I used your reposted instructions as listed above and in less than 5 Sec. of issuing the command it was reverted. I rebooted as the Terminal printout suggested and all was/is well. I just don't understand the logic of the LV creation on clean drive. What's it's purpose anyway?

 

[grahamperrin]

… the logic of the LV creation on clean drive. What's it's purpose anyway?

As there's a relatively closed/secretive approach by Apple to Core Storage, so it's impossible to know the logic. I suspect that some of Apple's logic will become clear in 2015.

In the meantime, in Apple Support Communities, for example:

Storage problems, Core Storage, Disk Utility, checksums, fsck_cs and cksum mismatches

– my August 2014 follow-up is not comprehensive; I did not (could not) go into any meaningful level of detail.

With or without that detail: I suspect that the use of Core Storage, at least for Yosemite, will ultimately be of significant value.

That value may not be realised until after Yosemite becomes outdated or legacy. For now, I should say:

• if normal use of Core Storage presents no obstacle to your everyday use of a Mac, then aim to accept what Apple uses as a default.

For pre-release software: try to be not annoyed when for some things, there's an apparent lack of explanation or logic from Apple.

 

[Tony.Skid]

Before reading your suggestion, I did something different: restarted with recovery HD, repaired permissions on Mavericks (lot of corrections on iTunes. Maybe because Yosemite had updated iTunes?), then restarted. TM backup now is ending, with a total of 4.98GB. Still, very odd.... Any idea?

Quote myself, only to tell that.. here we are again. After the update from dp7 to dp8, this is the results from the TM backup in 10.9: more than 15Gb...!
To recap, Yosemite is installed in external usb drive, is not included in TM backup, and now the drive with 10.10 is not connected to my MBP.... while work in Yosemite, I always disable the internal Hard disk (ejecting it from the desktop) right after the icon shows up in desktop.

 

[campyguy]

Thanks for this, I have Yosemite installed on a separate drive, and from a clean install it produced a CoreStorage volume giving me all the same annoyances that everyone has reported.

I used your reposted instructions as listed above and in less than 5 Sec. of issuing the command it was reverted. I rebooted as the Terminal printout suggested and all was/is well. I just don't understand the logic of the LV creation on clean drive. What's it's purpose anyway?

I'm agreed with grahamperrin, there appears to be no obvious reason or purpose, nor a rationale being made public. I downloaded the new installer last night, wiped my DP7 partition, and installed from the new installer - which turned out to be a new installer (with a new redemption code) for DP7, which I then updated to DP8 via the App Store. And, I was left with a Logical Group to revert. Again.

I haven't installed the update on another drive, but might do so later today.

There are advantages to the Logical Volume/Group with Physical Volume structure - but none that I'm aware of on Mac OS X outside of their creation of the Fusion Drive and support for commands in Terminal (of which you now know two). The "advantages" are IMO targeted to small volume management while using Linux - small as in 30-100 MB (not GB) volumes, and IMO the main advantage is in being able to dynamically resize volumes without having to repartition a drive(s)/volume(s) (set) - which we can't do in Disk Utility, and, if you need to dynamically resize drives and/or volumes, you're using Linux or virtualization software anyway.

I wrote earlier that this "thing" we're dealing with is a bug that showed up first in the Lion installer, along with an undocumented fix (those two and other CS commands). So, this is how we're going to have to deal with it until Apple fixes their installer. I think I'm going to submit this to Apple as a bug - given that it was in yesterday's installer, it ain't fixed yet...

BTW, I also noticed that yesterday's latest installer had today's date on it as I was downloading it from the App Store. I took screenshots...

 

[crjackson2134]

I'm not positive it's a bug, but I actually hope that it is, and that it will be rectified before release. It's like, during the install when it asks you if you want to encrypt the drive, it assumes yes will be the default and prepares for it, but when you say no, it's already laid the groundwork.

Now I'm sure that's a far fetched scenario, but it has the right feel. Please do file the bug report and I'll do the same. If it's not a bug they'll just ignore it anyway. Perhaps even an explanation would be forthcoming.

 

[BrooklynAl]

Checksum errors

Has anyone loaded the Yosemite GM on a fusion drive and are there the dreaded checksum errors?

 

[campyguy]

Has anyone loaded the Yosemite GM on a fusion drive and are there the dreaded checksum errors?

I'm going to give it a go in a few hours and will report back - I didn't get the new App Store code until a few minutes ago and it's DLing in the background. I'll also be attempting to install it on partitioned internal and external SSDs... Fingers crossed...

Not a waste of time for me, I'll be watching last night's Sons of Anarchy episode - so I'll be in the mood if my install goes sideways...

 

[campyguy]

I'm going to give it a go in a few hours and will report back - I didn't get the new App Store code until a few minutes ago and it's DLing in the background. I'll also be attempting to install it on partitioned internal and external SSDs... Fingers crossed...

Not a waste of time for me, I'll be watching last night's Sons of Anarchy episode - so I'll be in the mood if my install goes sideways...

A few days ago I took the plunge and installed GMC1/2/3 on my main drive - I erased the second partition, backed everything up, and went ahead with the installation. Everything seemed to go fine, until earlier today when I opened Disk Utility.

I found my single-partition drive set up as a Logical Group, which I found odd in that I've never seen that before in Linux or on a Mac. Unsure of how to proceed on the revertible single volume Logical Group, I used the two commands to restore the drive and was left with something I've never seen before - a group, partition, and "failed" partition named "Macintosh HD", with the "failed" partition showing up in red. Attempts to repair the drive failed, and I couldn't delete the failed partition.

Sorry, I didn't take any screenshots - I was busy trying to rescue my drive.

I restarted and booted into the recovery partition, and launched Disk Utility and was happy to see things right away as I'd expected - before having to use Disk Utility. I can't offer an explanation of what removed the problem partition - maybe the restart? - and I'll be filing a bug report with Apple over the weekend. I'm also considering wiping the drive and starting over, but that's just me thinking...