Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

Would someone who has a fusion drive that they bought directly from Apple please provide diskutil output sufficient to describe the choices they made?

I've seen lots of different sets of advice for how to DIY it, and that's fine, but I'd like to know how Apple is doing it on the ones they sell.

In particular, the interesting part is the choice they made on locating the recovery partition. Is it "outside" the fusion drive? If so, is it located on the SSD or the HD? Or is it "inside"?

If it were up to me, I would be inclined to locate the recovery partition "outside" on the spinny disk, but before my SSD and retrofit kit comes in the mail, I'd like to know how Apple did it.

share|improve this question
2  
Ars Technica have a very detailed article on the Fusion Drive. arstechnica.com/apple/2012/11/… –  daviewales Dec 5 '12 at 22:43

2 Answers 2

up vote 4 down vote accepted

Ars Technica did an article on how to roll your own Fusion Drive and one that details the layout of an Apple installed Fusion drive from a Mac Mini.

From that article:

LeeHs-Mac-mini:~ leeh$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *121.3 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_CoreStorage 121.0 GB disk0s2
3: Apple_Boot Boot OS X 134.2 MB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_CoreStorage 999.3 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: Apple_HFS Macintosh HD *1.1 TB disk2

LeeHs-Mac-mini:~ leeh$ diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 31CBA650-4ABC-4DA6-AA73-6D96B36693E2
        =====================================================
        Name:         Macintosh HD
        Size:         1120333979648 B (1.1 TB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume F4A50F9C-841D-4C6D-AFC4-6A10560E0717
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     120988852224 B (121.0 GB)
        |
        +-< Physical Volume C86789FD-1978-453A-BCA7-81DC05AA66C7
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     999345127424 B (999.3 GB)
        |
        +-> Logical Volume Family AA92FDF8-F962-4DE3-AC2F-1B6ABF22AA22
            ------------------------------------------------------
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume B97C9558-14FC-4BFC-B413-AFB292BD29F0
                -----------------------------------------------
                Disk:               disk2
                Status:             Online
                Size (Total):       1115853029376 B (1.1 TB)
                Size (Converted):   -none-
                Revertible:         No
                LV Name:            Macintosh HD
                Volume Name:        Macintosh HD
                Content Hint:       Apple_HFS

As you can see, the recovery partition is "outside" the Core Storage volume which gets mounted by the OS and functions as "the Fusion Drive". The Fusion Drive is comprised of one standard partition from each disk, rather than using the full drive and storing the configuration data out of or in-band by hiding it. Everything we know so far about standard Fusion Drives is pretty straightforward and transparent.

share|improve this answer

For what it's worth, I've gotten this working now. For anyone coming along behind me, I managed to get the volumes backwards - in my 'diskutil cs list' output, the spinny disk is index 0 and the SSD is index 1. Despite this, it appears to be behaving exactly how Fusion Drives are documented to work - all of the writes are hitting the SSD until it is full, and then overflow is going to the spinny disk.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.