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

Mac2013orlater

macrumors member
Original poster
Feb 2, 2014
98
2
All that below is about os x 10.9.5 on iMac 2013 Late with SSD as the only internal drive and the mentioned os x installed on it and working without big problems.
At partition/disk level the ssd is as delivered by Apple, no adaptations were made by user at partition/logical disk level.
Merely the File Vault 2 was applied to this SSD.
That means amongst others no BootCamp.
Disk Utility presents for this SSD 4 items: Macintosh HD, EFI (grey color font), Macintosh HD (grey color font), Recovery HD (grey color font).

The Recovery Mode (by starting the mac while cmd+R is depressed) starts and seems to work pretty well.
However the Startup Manager (by starting the mac while the alt/option key depressed) does not offer the Recovery HD for booting.
It does offer merely the Macintosh HD for booting.
According to some article in web to which in this forum it is widely and frequently referring to,
the Startup Manager should also offer the Recovery HD on the system disk for booting.

I wonder why in case of this mac this does not happen?
Is this the valid and known design of 10.9.5 or the root cause to be searched where else?

I have a clone of that Recovery HD on some external USB storage.
The Startup Manager does offer this Recovery HD for booting very well.
Where the difference in handling these two Recovery HD's come from?
 
Last edited:

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,162
15,654
California
Totally normal. When you turn on FileVault the recovery HD boot option goes away from the startup manager, and is only available via command-r.
 

Mac2013orlater

macrumors member
Original poster
Feb 2, 2014
98
2
Thanks to Weaselboy for helpful information!

The conclusion for me is, all is fine with that Mac.
No more troubleshooting is needed. Valuable time can be
invested in tasks which really need it.

This is highly interesting.
I was namely - regarding this issue - a long time in contact with Apple.
A support ticket/case was open to clarify this issue.
Many weeks in discussion with senior level Apple support.
In the beginning the Apple support was informed the system disk is
protected by File Vault 2.
Lot of weeks of trials, tests and try-maybe-this checks.
No single word on side of Apple expert about the issue connections to FV2.
Finally the contact broke without single word of announcement.
 

Mac2013orlater

macrumors member
Original poster
Feb 2, 2014
98
2
Actually, I wonder why is this that way.
If a lack of ability to see partitions within big encrypted container is the reason
the system startup partition should not be visible for SM as well. FV2 makes whole disk encryption.
Is the property as you point out described in any Apple public document?
 

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,162
15,654
California
Actually, I wonder why is this that way.
If a lack of ability to see partitions within big encrypted container is the reason
the system startup partition should not be visible for SM as well. FV2 makes whole disk encryption.
Is the property as you point out described in any Apple public document?

http://support.apple.com/kb/ht4811

It mentions it in this doc, but no real explanation.

The recovery partition is actually not inside the encrypted space, so I really don't know the exact reason Apple sets it up like this.

If you run the command "diskutil list" (without the quotes) in Terminal you can see the partition layout.
 

Mac2013orlater

macrumors member
Original poster
Feb 2, 2014
98
2
Hmm, I am not sure the article you are referring to is describes the behavior as
you described it here previously.
What is the source of your statement? Some Apple source of knowledge? Which one? Or rather all your experiences with Mac ?
 

Weaselboy

Moderator
Staff member
Jan 23, 2005
34,162
15,654
California
Hmm, I am not sure the article you are referring to is describes the behavior as
you described it here previously.
What is the source of your statement? Some Apple source of knowledge? Which one? Or rather all your experiences with Mac ?

I'm not really clear what you are after.

If you run the command below in Terminal to will see the layout of the hidden EFI and recovery partitions and you will see they are not inside the encrypted core storage space.

Code:
diskutil cs list

You can test the different scenarios I described with option vs. command-r boot on your system and you can verify what I have said.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.