Fusion Drive als virtuelles Volume ?

Hallo Gemeinschaft
Ich habe dummerweise zuviel rumexperimentiert, als ich meine Recovery-Partition löschen wollte und meine kompletten Laufwerke und Partitionen verwurstet.
Nach einigem hin und her mit 'diskutil' via Terminal habe ich dann alles wieder lauffähig bekommen und konnte/durfte mein OSX neu installieren.
Nun ist aber folgendes passiert:
Wenn ich mein Festplattendienstprogramm öffne, dann wird mir mein Fusion Drive nicht mehr mit der Festplatten-Bezeichnung (wie früher) angezeigt sondern dort steht 'Gesamtes virtuelles Volume'
Das macht mir Angst...
Ebenso bin ich mir nicht sicher, dass meine MacintoshHD als Logische Partition so richtig ist.
Ich hänge hier mal 2 Bilder unten dran.
Hat jemand Ähnliches erlebt? Wenn ja, bekomme ich damit Probleme? Kann ich das vor den Problemen irgendwie retten?
Danke und Gruß - Kai

You can definitely create a Fusion Drive using an external drive to add capacity, and in fact it can be a great thing to do as the SSD will eliminate most of the latency involved.
The SSD will contain whatever the most frequently used blocks are, and these will moved from your HDD(s) onto the SSD to provide the performance improvement. This means you could potentially end up with any number of your working files on the SSD depending upon how often you use them (or have been using them recently). This is important to keep in mind; the SSD in a Fusion Drive is not the cache as a cache-disk, meaning that if the SSD fails you will lose data and have to rebuild your Fusion Drive from backups.
This will essentially eliminate the redundancy advantage of RAID-5, as while you can replace any HDDs that fail as normal, an SSD failure will render the volume unusable.
I'm actually currently interested in whether a RAID-1 of SSDs can be used within a Fusion Drive, as it could allow the SSD part of the Fusion Drive to be given redundancy too, in which case the setup would be safe as it'd be 2x SSDs in RAID-1 + HDDs in RAID-5, giving you one to two disks worth of redundancy. However I suspect it won't work, as I believe Fusion Drive just queries each disk to determine if it is an SSD, and of course an Apple RAID won't identify itself as such.

Similar Messages

  • DIY MAC Fusion Drive

    I'd like to create my own MAC Fusion Drive, but I'm not a dev so I need a little bit of guidance, which would also help a lot of people I'm guessing.
    I am trying to follow jollyjinx's instructions, which are not that detailed.  Specifically, I am trying to find the names of my two drives and I can only find one.  Maybe the drives are not connected in a way to do this I'm not sure.  I have a 750GB HDD and an 80GB SSD installed internally in my 2011 Mac Mini.  I have been using both drives, SSD for the OS and a handful of common files and the HDD for iPhoto and iTunes libraries.  A Fusion drive would be perfect!
    When I run dmesg in Terminal, here is what I get:
    -bash-3.2# dmesg
    PMAP: PCID enabled
    Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64
    vm_page_bootstrap: 2003271 free pages and 77497 wired pages
    kext submap [0xffffff7f8073e000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff800073e000]
    zone leak detection enabled
    standard timeslicing quantum is 10000 us
    standard background quantum is 2500 us
    mig_table_max_displ = 74
    TSC Deadline Timer supported and enabled
    corecrypto kext started!
    Running kernel space in FIPS MODE
    Plist hmac value is    735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
    Computed hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
    corecrypto.kext FIPS integrity POST test passed!
    corecrypto.kext FIPS AES CBC POST test passed!
    corecrypto.kext FIPS TDES CBC POST test passed!
    corecrypto.kext FIPS AES ECB AESNI POST test passed!
    corecrypto.kext FIPS AES XTS AESNI POST test passed!
    corecrypto.kext FIPS SHA POST test passed!
    corecrypto.kext FIPS HMAC POST test passed!
    corecrypto.kext FIPS ECDSA POST test passed!
    corecrypto.kext FIPS DRBG POST test passed!
    corecrypto.kext FIPS POST passed!
    AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
    AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
    AppleACPICPU: ProcessorId=3 LocalApicId=1 Enabled
    AppleACPICPU: ProcessorId=4 LocalApicId=3 Enabled
    AppleACPICPU: ProcessorId=5 LocalApicId=255 Disabled
    AppleACPICPU: ProcessorId=6 LocalApicId=255 Disabled
    AppleACPICPU: ProcessorId=7 LocalApicId=255 Disabled
    AppleACPICPU: ProcessorId=8 LocalApicId=255 Disabled
    calling mpo_policy_init for TMSafetyNet
    Security policy loaded: Safety net for Time Machine (TMSafetyNet)
    calling mpo_policy_init for Sandbox
    Security policy loaded: Seatbelt sandbox policy (Sandbox)
    calling mpo_policy_init for Quarantine
    Security policy loaded: Quarantine policy (Quarantine)
    Copyright (c) 1982, 1986, 1989, 1991, 1993
              The Regents of the University of California. All rights reserved.
    MAC Framework successfully initialized
    using 16384 buffer headers and 10240 cluster IO buffer headers
    IOAPIC: Version 0x20 Vectors 64:87
    ACPI: System State [S0 S3 S4 S5] (S3)
    PFM64 (36 cpu) 0xf10000000, 0xf0000000
    [ PCI configuration begin ]
    AppleIntelCPUPowerManagement: Turbo Ratios 0057
    AppleIntelCPUPowerManagement: (built 13:47:00 Aug 14 2012) initialization complete
    console relocated to 0xf60010000
    PCI configuration changed (bridge=16 device=5 cardbus=0)
    [ PCI configuration end, bridges 13 devices 18 ]
    mbinit: done [96 MB total pool size, (64/32) split]
    Pthread support ABORTS when sync kernel primitives misused
    rooting via boot-uuid from /chosen: 7B269773-B97B-335A-A4EF-A3D6956395BA
    Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
    com.apple.AppleFSCompressionTypeZlib kmod start
    com.apple.AppleFSCompressionTypeDataless kmod start
    com.apple.AppleFSCompressionTypeZlib load succeeded
    com.apple.AppleFSCompressionTypeDataless load succeeded
    AppleIntelCPUPowerManagementClient: ready
    BTCOEXIST off
    BRCM tunables:
      pullmode[1] txringsize[  256] reapmin[   32] reapcount[  128]
      highWaterMark: VO[  192]  VI[  192]  BE[  192]  BK[  192]
    FireWire (OHCI) TI ID 823f built-in now active, GUID c82a14fffeeaff8c; max speed s800.
    USBMSC Identifier (non-unique): 1690A44191FF 0x59b 0x370 0x0
    USBMSC Identifier (non-unique): AA19164300000896 0x3f0 0xb107 0x8192
    Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/EHC1@1D,7/AppleUSBEHCI/U SB FLASH DRIVE@fd133000/IOUSBInterface@0/IOUSBMassStorageClass/IOSCSIPeripheralDeviceNub /IOSCSIPeripheralDeviceType00/IOBlockStorageServices/IOBlockStorageDriver/hp USB Flash Drive Media/IOGUIDPartitionScheme/OS X MOUTNAIN LION INSTALL@2
    BSD root: disk4s2, major 1, minor 15
    imageboot_setup_new: root image url is file:///BaseSystem.dmg
    IOHDIXController: NOTE: administrator is creating non-ejectable disk image
    KDIFileBackingStore::_handleStart: initial R/W vn_open returned 30
    imageboot_mount_image: root device 0x1000011
    HFS: Low Disk: Vol: Mac OS X Base System freeblks: 30158, warninglimit: 30790
    Kernel is LP64
    ioqueue_depth = 64,   ioscale = 2
    Previous Shutdown Cause: 0
    [BroadcomBluetoothHCIControllerUSBTransport][start] -- completed
    DSMOS has arrived
    [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification
    [IOBluetoothHCIController][start] -- completed
    BCM5701Enet: Ethernet address c8:2a:14:59:28:c5
    AirPort_Brcm4331: Ethernet address 28:cf:da:01:31:fd
    IO80211Controller::dataLinkLayerAttachComplete():  adding AppleEFINVRAM notification
    IO80211Interface::efiNVRAMPublished(): 
    [IOBluetoothHCIController::setConfigState] calling registerService
    AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
    en1::IO80211Interface::postMessage bssid changed
    en1: 802.11d country code set to 'US'.
    en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
    MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20  MAC AUTH succeeded
    wlEvent: en1 en1 Link UP virtIf = 0
    AirPort: Link Up on en1
    en1: BSSID changed to 00:23:6c:bf:ae:20
    en1::IO80211Interface::postMessage bssid changed
    AirPort: RSN handshake complete on en1
    [ffffff8018e64c00][BNBTrackpadDevice::init][75.15] init is complete
    [ffffff8018e64c00][BNBTrackpadDevice::handleStart][75.15] returning 1
    [ffffff8019e85800][AppleMultitouchHIDEventDriver::start] entered
    [ffffff8018da6c00][AppleMultitouchDevice::start] entered
    MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20  MAC AUTH succeeded
    MacAuthEvent en1   Auth result for: 00:23:6c:bf:ae:20 Unsolicited  Auth
    wlEvent: en1 en1 Link UP virtIf = 0
    AirPort: RSN handshake complete on en1
    wl0: Roamed or switched channel, reason #4, bssid 00:23:6c:bf:ae:20
    en1: BSSID changed to 00:23:6c:bf:ae:20
    en1::IO80211Interface::postMessage bssid changed
    -bash-3.2#
    I can only find one reference to a drive in the data, but maybe I'm missing something.  Any help would be greatly appreciated!

    So far, so good!  The article steps worked perfectly.  I setup the Fusion Drive and then restored from my Time Machine Backup (from the SSD).  I then moved the files over that were on the HDD (which I also backed up on my external drive.  Everything seems to be working great! The volume was previously named 80 SSD OS X (to differentiate from the HDD) and it is still named that, although, as you can see from the screenshot, it now has a 576GB capacity (not 750GB, which is what I thought I put in there--my memory is horrendous! lol) ....not a big deal.  I consider this a huge success at this point.  Thanks again for the article!

  • I deleted my bootcamp via DU and then deleted the hard drive by using the terminal. My BOOTCAMP is still there and now my fusion drive is separated from the SSD portion and I have no idea how to fix it.

    First off I have a 3tb fusion drive.
    I created a 200gb bootcamp, I tried deleting the bootcamp because I thought I messed it up and googled how to delete a mac partition which told me to use Disk Utility, did that and then erased it and somehow it got locked and wouldn't let me do anything to any partition on my hard drive (everything was greyed out)
    After looking up and googling for hours I found a post saying the only way to fix it would be to go into CMD+R and go into the terminal window and type out disklist and then find the first UUID number and do something along the lines of disklist delete (UUID) i forget the exact formula. I did this, and then I had 3 separate untitled hard drives.
    One in the size of 1.9gb on in 800gb and one in 121.3gb (which is the SSD), I put my time machine backup onto the 1.9gb untitled and now my computer is booting slowly (because it's no longer running off of the SSD and the original bootcamp is still there.
    To be honest I am absolutely confused on what else to do!
    Is there anyway I can fix this?

    How do I go about deleting and then re-adding the hard drives? Completely lost on how to make it back to being a 3gb fusion drive.
    Thank you for all your help, I honestly really appreciate it.
    I followed your instructions and got the following
    diskutil list:
    -bash-3.2# diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            120.5 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *3.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:          Apple_CoreStorage                         1.9 TB     disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
       4:          Apple_CoreStorage                         251.9 GB   disk1s4
       5:                 Apple_Boot Boot OS X               134.2 MB   disk1s5
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *1.3 GB     disk2
       1:        Apple_partition_map                         30.7 KB    disk2s1
       2:                  Apple_HFS OS X Base System        1.3 GB     disk2s2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Untitled               *1.9 TB     disk3
                                     Logical Volume on disk1s2
                                     FD9357F1-1A71-44A0-A01E-41C84F1C8047
                                     Unencrypted
    /dev/disk4
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Untitled               *251.5 GB   disk4
                                     Logical Volume on disk1s4
                                     31B60F49-6981-47A3-9815-6396AD3A9BD6
                                     Unencrypted
    /dev/disk5
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *5.2 MB     disk5
    /dev/disk6
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk6
    /dev/disk7
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk7
    /dev/disk8
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk8
    /dev/disk9
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk9
    /dev/disk10
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk10
    /dev/disk11
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *6.3 MB     disk11
    /dev/disk12
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *2.1 MB     disk12
    /dev/disk13
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk13
    /dev/disk14
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk14
    /dev/disk15
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *524.3 KB   disk15
    /dev/disk16
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *1.0 MB     disk16
    /dev/disk17
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *319.4 GB   disk17
       1:                        EFI EFI                     209.7 MB   disk17s1
       2:                  Apple_HFS IMAC TMB                319.0 GB   disk17s2
    /dev/disk18
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            untitled               *6.3 MB     disk18
    /dev/disk19
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:        CD_partition_scheme                        *804.4 MB   disk19
       1:     Apple_partition_scheme                         700.4 MB   disk19s0
       2:        Apple_partition_map                         32.3 KB    disk19s0s1
       3:                  Apple_HFS WD SmartWare            237.5 MB   disk19s0s2
    -bash-3.2#
    diskutil cs list
    -bash-3.2# diskutil cs list
    CoreStorage logical volume groups (2 found)
    |
    +-- Logical Volume Group 687E889E-B4A1-4F20-8B36-43D7A3701076
    |   =========================================================
    |   Name:         Untitled
    |   Status:       Online
    |   Size:         1946162462720 B (1.9 TB)
    |   Free Space:   5402624 B (5.4 MB)
    |   |
    |   +-< Physical Volume 7BCD8D9C-AEB2-4D48-B248-257EFC7EA922
    |   |   ----------------------------------------------------
    |   |   Index:    0
    |   |   Disk:     disk1s2
    |   |   Status:   Online
    |   |   Size:     1946162462720 B (1.9 TB)
    |   |
    |   +-> Logical Volume Family 3A8A9627-5963-49BA-8E2F-96DC7A1B033D
    |       ----------------------------------------------------------
    |       Encryption Status:       Unlocked
    |       Encryption Type:         None
    |       Conversion Status:       NoConversion
    |       Conversion Direction:    -none-
    |       Has Encrypted Extents:   No
    |       Fully Secure:            No
    |       Passphrase Required:     No
    |       |
    |       +-> Logical Volume FD9357F1-1A71-44A0-A01E-41C84F1C8047
    |           ---------------------------------------------------
    |           Disk:                  disk3
    |           Status:                Online
    |           Size (Total):          1945804734464 B (1.9 TB)
    |           Conversion Progress:   -none-
    |           Revertible:            No
    |           LV Name:               Untitled
    |           Volume Name:           Untitled
    |           Content Hint:          Apple_HFS
    |
    +-- Logical Volume Group 98213AE6-9EA8-4FB7-8B72-8E08BFBFD82C
        =========================================================
        Name:         Untitled
        Status:       Online
        Size:         251864797184 B (251.9 GB)
        Free Space:   5226496 B (5.2 MB)
        |
        +-< Physical Volume 20CEF763-635D-4A0D-A107-40E8FB161D06
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s4
        |   Status:   Online
        |   Size:     251864797184 B (251.9 GB)
        |
        +-> Logical Volume Family 2D3173B3-5B04-47E6-B331-49D1BA58E9F2
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume 31B60F49-6981-47A3-9815-6396AD3A9BD6
                Disk:                  disk4
                Status:                Online
                Size (Total):          251507245056 B (251.5 GB)
                Conversion Progress:   -none-
                Revertible:            No
                LV Name:               Untitled
                Volume Name:           Untitled
                Content Hint:          Apple_HFS
    -bash-3.2#
    Disk0
    -bash-3.2# gpt -vv -r show /dev/disk0
    gpt show: /dev/disk0: mediasize=121332826112; sectorsize=512; blocks=236978176
    gpt show: /dev/disk0: PMBR at sector 0
    gpt show: /dev/disk0: Pri GPT at sector 1
    gpt show: /dev/disk0: Sec GPT at sector 236978175
          start       size  index  contents
              0          1         PMBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6        
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  235298960      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      235708600    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      236978136          7        
      236978143         32         Sec GPT table
      236978175          1         Sec GPT header
    -bash-3.2#
    Disk1
    -bash-3.2# gpt -vv -r show /dev/disk1
    gpt show: /dev/disk1: mediasize=3000592982016; sectorsize=512; blocks=5860533168
    gpt show: /dev/disk1: PMBR at sector 0
    gpt show: /dev/disk1: Pri GPT at sector 1
    gpt show: /dev/disk1: Sec GPT at sector 5860533167
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  3801098560      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
      3801508200     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      3802777736        1912        
      3802779648   491923432      4  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
      4294703080      262144      5  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      4294965224  1565567911        
      5860533135          32         Sec GPT table
      5860533167           1         Sec GPT header
    -bash-3.2#

  • Is there a way to run a external ssd with my mid 2011 iMac hdd in a raid configuration and basically have a fusion drive

    is there a way to run a external ssd with my mid 2011 iMac hdd in a raid configuration and basically have a fusion drive

    A Fusion Drive is not a RAID; it's a CoreStorage logical volume group. While it's technically possible to do as you suggest, there would be little or no benefit from it.

  • DIY Fusion Drive on MacBookPro8,2

    Yes, I know it's not supported out ot the box.
    I've been trying to set up a DIY Fusion Drive on my Early 2011 MBP 15" with no luck.
    I've been googling a bit and found several others reporting the same problems on the MBP8,2. Seems this setup works on most Mac's, just not this model. Has anyone gotten this to work with any sort of hack? Please share your experience.

    In case you are not already aware of these resources here are some links
    http://blog.macsales.com/15617-creating-your-own-fusion-drive
    http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html
    There are others, but the most salient point from the first link is that it alleges the 2012 Mini is the only Mac that uses a version of Disk Utility capable of creating a Fusion volume. This sounds dubious to me though since I find it hard to believe CoreStorage is dependent upon a version of Disk Utility that exists only for the Mini. The only reason I mention this is that I consider OWC knowledgeable about the subject.
    Without further details of how you intend to accomplish this I am curious how you justify the following comment:
    The OS handles where the files go so I can use the time to work instead of managing where the files go for best performance.
    We know Apple's Fusion Drive accomplishes these actions in firmware or software that exists in their new iMacs, but what resource led you to conclude this ability exists in your MacBook Pro, or anything other than the current production 2012 iMacs for that matter?
    If you are certain it does, I may do it also. I like challenges too.

  • Fusion drive DIY not using SSD

    Hello community,
    Recently I have bought a SSD drive for my Mac Mini 2012, in order to make a dual hard drive installation ready to build a DIY Fusion Drive with Disk Utility. Apparently it works well, I have installed Yosemite without any problems and been using the Mac Mini normally. The problem is that it's very slow performance when it needs to read/write from disk, I've got around 40mb/s read and 35mb/s write speeds on BlackMagic disk speed tests.
    In addition, checking the installation of the drives running "diskutil list" from command line (which tells me that disk0 is the SSD and disk1 is the HDD), and the disk usage with "iostat disk0 disk1 1" I can see that the OS is not really using disk0 but disk1 for all disk operations.
    I noticed that eventually disk0 has movement but 99% activity is in disk1 (HDD). I believe that the normal behavior of a Fusion Drive is using SSD mainly and HDD in second instance for "not-cached" or less used files, but I am experiencing the opposite behavior.
    The model of the SSD is Kingston HyperX 3K 240GB.
    Please give me any advice about this issue.
    Thanks for your help.
    Best regards.

    Thanks for your replies.
    Actually the SSD it's installed in the upper bay, because I've tried to install it at the bottom but Fusion Drive seems not to work, failing disk verification and prompting me to repair disk. In the upper bay seems to work fine, but I've this this issue.
    This is my "diskutil cs list" output:
    Mac-mini-de-Arturo:~ Bayo$ diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group FB3EEBCC-EBDA-4F7A-9256-0AE4A854C512
        =========================================================
        Name:         Internal Drive
        Status:       Online
        Size:         1239058448384 B (1.2 TB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 3D0A6EE0-51FE-425C-B716-89215472D2D9
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     239713435648 B (239.7 GB)
        |
        +-< Physical Volume 397E16F1-877B-412B-8D7D-59A5BD47661A
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     999345012736 B (999.3 GB)
        |
        +-> Logical Volume Family 8FEAC5E2-11F2-4FE7-B980-945A0B81463C
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume 1621B9C3-17F9-4ABC-B8FF-767FEF074A94
                Disk:                  disk2
                Status:                Online
                Size (Total):          1230265384960 B (1.2 TB)
                Conversion Progress:   -none-
                Revertible:            No
                LV Name:               Macintosh HD
                Volume Name:           Macintosh HD
                Content Hint:          Apple_HFS
    and, for more info, a screenshot of my current speed test with BlackMagic:
    Many thanks!

  • Mac Fusion drive: The disk "Macintosh HD" could not be unmounted

    Hi
    I recently purchased a Mac Mini with the fusion drive.  When I perform a verify and repair of the disk, I get the error "The disk Macintosh HD could not be unmounted".  This does not occur with any of my other computers, imac or powermac (also running mountain lion).  So I am wondering if I have a defective Fusion/HD or if this is simply a peculiarity of the fusion drive itself.  Please comment.

    If your Fusion drive can be repaired with Disk Utility, it will be shown with red lettering. If you are not seeing red lettering, then you need to boot into Recovery mode to use that Disk Utility. When you order a Fusion drive equipped Mac, there is a special version of Disk Utility included in OS X specifically for operation with Fusion Drives.
    If you have any open files on the volume you wish to verify/repair, then Disk Utility will throw its hands up and give you that cannot unmount drive message. Make sure you have quit all applications you were using that may be accessing files on the disk in question.
    Apple article.

  • Fusion drive & dual boot

    Is it possible on a fusion drive to have Maverick and Windows at the same time? Is it going to work the same way on windows ( I mean as fast as in osx)

    Michael Conelly wrote:
    After much gnashing of teeth, and a half dozen support calls, I'd all but given up.  I finally seem to have solved this though - sort of - by installing windows 8.1 on boot camp on an older iMac, then cloning the bootcamp disk to an external thunderbolt drive via Winclone.  That worked seamlessly, sticking to winclone's instructions, and I can boot via EFI to Windows 8.1 on the new iMac.  So far so good.
    I usually install W8.1 via EFI by using DU and a Free Space partition. The 3TB Fusion is first split into the underlying SSD/HDD physicals. OSX and Windows OSes are installed on SSD via EFI (no BCA). The OSX part and half the HDD are then used to create a new CS volume. The other HDD half becomes NTFS for non-Windows OS files. The Hybrid MBR method is completely unsatisfactory with the 3TB Fusion drive.
    How is the TB/Winclone image for performance of the OS (since pagefile.sys is also on the TB)?

  • Fusion drive and external data drives

    How does Fusion drive behave if you have data on an external device?  I just odered a new Mini and I'm a Logic user with hundreds of GB worth of data on an external RAID 5 exclosure.  Will files stored on the RAID be copied to the Fusion Drive when accessed frequently, or will that functionality be strictly for the boot volume?
    Thanks!

    You can definitely create a Fusion Drive using an external drive to add capacity, and in fact it can be a great thing to do as the SSD will eliminate most of the latency involved.
    The SSD will contain whatever the most frequently used blocks are, and these will moved from your HDD(s) onto the SSD to provide the performance improvement. This means you could potentially end up with any number of your working files on the SSD depending upon how often you use them (or have been using them recently). This is important to keep in mind; the SSD in a Fusion Drive is not the cache as a cache-disk, meaning that if the SSD fails you will lose data and have to rebuild your Fusion Drive from backups.
    This will essentially eliminate the redundancy advantage of RAID-5, as while you can replace any HDDs that fail as normal, an SSD failure will render the volume unusable.
    I'm actually currently interested in whether a RAID-1 of SSDs can be used within a Fusion Drive, as it could allow the SSD part of the Fusion Drive to be given redundancy too, in which case the setup would be safe as it'd be 2x SSDs in RAID-1 + HDDs in RAID-5, giving you one to two disks worth of redundancy. However I suspect it won't work, as I believe Fusion Drive just queries each disk to determine if it is an SSD, and of course an Apple RAID won't identify itself as such.

  • Fusion Drive  4TB + SSD m4 512 Go DEAD can't reformat

    Hello,
    I have an iMac 27 late 2010 i5 3.6 with 16 Go of RAM running 10.8.3
    For Christmas, I received a M4 SSD 512 Go and decided to replace the 2TB in my iMac with a 4TB and create a Fusion Drive.
    The operation worked beautifully and my iMac became incredibly fast, which was the goal.
    Yesterday, the iMac did not start and I got the white screen with the spinning wheel. After reading about zapping the pram and Vram, nothing worked.
    I booted from an external hard drive with Mac os X 10.8.2 and ran Disk Util to check the drive. I got a lot of red lines in the report and got the error Disk Utility can't repair this disk. back , reformat and restore.
    I was able to copy some of the files on the drive and decided to reformat the drive.
    Everytime I try to reformat the drive (4.4tB Fusion Drive) the mac shuts down and restarts.
    I tried to un fuse the fusion drive and I get the same result.  the screen goes black, the computer restarts and displays that the mac encountered a problem and had to restart.
    when I type the commande in terminal diskutil cs file, I see the logical volume group.
    When I do a diskutil cs Delete Volume xxxxxx xxxx xxx x x x x x x x
    started CoreStorage operation on disk 2 iMac
    Unmounting disk2
    Removing Logical Volume from Logical Volume Group
    then the mac shuts down and restarts.
    it took me 2 hours to crack the beast open to perform the disk implant last  christmas and it was scary. I thought I would never manage to close it properly.
    I understand that this operation voided the warranty (i have the Apple Care for 3 years).
    Any help greatly appreciated.
    Thanks
    Phil

    Thanks for your answers.
    I still don't know if it was the SSD or the HD that was faulty but I found a solution via this post
    https://discussions.apple.com/message/21492423#21492423
    Jerome Tremblay
    This solved my questionRe: Unable to reformat/repartition Fusion Drive 
    Mar 12, 2013 11:05 AM (in response to Topher Kessler)
    @Topher : It did not work, and it failed with POSIX errors similar to the zeroDisk message I posted above.
    However, While I was unable to "cleanly" solve my problem, I managed to reset everything by booting in single-user mode from an external hard drive (with cmd-S) and overwriting the disk directly with
    cat /dev/random > /dev/disk0 cat /dev/random > /dev/disk1
    Then I rebooted and I could reformat the drives (actually, I created another fusion drive using these directives).
    I was able to reformat the drives as a Fusion Drive. My time Machine backup was only a week old but it worked perfectly. I was able to add the rest via my Backblaze subscription.
    Don't know how long the Fusion drive will last but I am prepared with my backups in case it happens.
    Phil

  • Fusion Drive on a 2010 iMac with 2tb HDD & 256gb SSD

    Hi,
    well basicailly the title says it all!
    I have a 2010 iMac with the 256gb SSD and 2TB HDD which to me seems like it would be great option for the Fusion Drive...
    Does anyone have any ideas on how I could make the drives work like the new Fusion Drive?
    I've seen the Macworld Tutorial on a DIY Fusion Drive but i'm still not sure if doing that will work in the same way as the preinstalled 2012 iMac Fusion Drive... I know that Mac OSX will treat the combined drives as one, but in terms of moving files depending upon their usage is another matter.
    If the Macworld step by step is followed will Mountain Lion handle frequently used files / apps like the apple presentation states or will it just use the drives as one and not increase the performance of my machine?
    Any help on this would be much appreciated, especially if anyone has followed the Macworld steps etc!
    Thanks
    Darren

    Thanks fir the reply, I thought with the fusion drive the SSD and HDD were two seperate storage devices seen by OSX as one volume, and the software determins where the files most used will be placed and accessed from.
    I've read a bit about this here;
    http://macs.about.com/od/diyguidesprojects/ss/Setting-Up-A-Fusion-Drive-On-Your- Current-Mac.htm
    but would be great to hear first hand experience!!
    With this DIY approach it appears that the same functionality of the 2012 iMacs is achieved but simply not using the older Disk Utility, but a newer version only included on the newer models...

  • Fusion drive on 2011 mid Mac mini...

    Hi everyone,
    I understand how the new Fusion drive works. But only available on new macs.
    I've been watching videos on YouTube that show how to make an ssd and hdd into one volume. And they show after the upgrade that these upgrades work. Now, I've also been hearing from other sources that it is impossible to make your own Fusion drive. That all you are doing is adding the two different drives. That the two drives don't actually don't work like I've been seeing on you tube.
    I really do want to make my Mac mini into Fusion drive Mac. I don't have the funds for a new computer. I've also seen the new hybrid drives. 8gb ssd with 750 gb hhd to kind of a poor man's version of the Fusion drive.
    So, I really need the advice of the experts here.
    Thanks everyone,
    mhh

    1. Fusion Drive works on OS level, or more precisely, it lays between the physical storage and the file system, therefore there are few requirements for hardware, only you need an SSD + an HDD to make it work.
    2. With the two drives properly installed, boot your mac with a recovery disk (10.8.3 and later) or with the Internet recovery (which makes sure that you have the latest recovery image), the disk utility will prompt that your drives are not working correctly and needs to be fixed. Fix it as prompted (note that your data on BOTH drives will be erased, so make a backup before doing this), and you will get a fusion drive, automatically, without any further configuration.
    3. Reboot and restore from your backup, you are ready to go!
    Addtionally:
    1. You will need to enable the TRIM support for your SSD (it's pretty important) manually (try TRIM Enabler: http://www.groths.org/trim-enabler/ ), because OS X only provide native TRIM support for Apple stock SSDs, but not for any 3rd party ones.
    2. As someone said above, the RAM capacity has little relevency with the performance of Fusion Drive.
    3. Hybrid only achieves a small part (read and write caching) of what Fusion Drive provides, as the SSD part is too small. Fusion Drive stores the whole OS and other frequently accessed data almost permanently on the SSD part, which means you will have most of your job done much faster.

  • DIY Fusion Drive...

    So i've just installed a Crucial M4 128GB SSD and when i get home from work i'm putting the original HDD back in my MacBook Pro in the optical drive bay with a 'caddy' kit.
    I'm considering creating a Fusion drive out of the 2 internal HDD's but before I go through with are there any risks with doing it myself? And, is it worth it?

    In case you are not already aware of these resources here are some links
    http://blog.macsales.com/15617-creating-your-own-fusion-drive
    http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html
    There are others, but the most salient point from the first link is that it alleges the 2012 Mini is the only Mac that uses a version of Disk Utility capable of creating a Fusion volume. This sounds dubious to me though since I find it hard to believe CoreStorage is dependent upon a version of Disk Utility that exists only for the Mini. The only reason I mention this is that I consider OWC knowledgeable about the subject.
    Without further details of how you intend to accomplish this I am curious how you justify the following comment:
    The OS handles where the files go so I can use the time to work instead of managing where the files go for best performance.
    We know Apple's Fusion Drive accomplishes these actions in firmware or software that exists in their new iMacs, but what resource led you to conclude this ability exists in your MacBook Pro, or anything other than the current production 2012 iMacs for that matter?
    If you are certain it does, I may do it also. I like challenges too.

  • Windows will not boot to my boot camp partition on a DIY fusion drive - gives "No bootable device found" error

    I have a MacBookPro 9,1 (mid-2012, non-retina) running OS X 10.8.2.  Here is what I have done to my system:
    Installed Windows 7 x64 Pro to a boot camp partition; installed all windows updates.
    Using WinClone, save an image of this boot camp partition.
    Removed optical drive and HDD.
    Installed HDD in place of optical drive.
    Installed SSD in place of HDD.
    Booted to recovery partition, installed OS X on a flash drive.
    Booted to flash drive, created fusion drive using [MacWorld's instructions](http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html)
    Booted to recovery partition on flash drive.
    Restored system to fusion drive from a Time Machine backup. Unfortunately, it seems that because I never installed OS X on my fusion drive, I do not have a recovery partition. But that's an issue for another day.
    Using Boot Camp assistant, created a boot camp partition on my HDD.
    Using WinClone, restore my Windows installation from the previously created image.
    Now, Windows boots to a black screen telling me that it can't find a bootable device. I have tried a few things to resolve this, all without effect:
    I know that VMware Fusion has to prepare a boot camp partition in order to virtualize it, so I figured it might inadvertently fix things. Alas, while it *did* successfully boot my boot camp partition into a virtual machine, I still can't boot into Windows.
    I figured I'd just try to reinstall Windows. Surprisingly, my system booted to my Windows install disc, which was in my original optical drive (which I had put in a USB case). But, Windows refused to install, giving me a an error 0x8030024. It seems the solution to this issue is to disconnect all drives but the one on which you want to install Windows, which is something I would dearly like to avoid. It would be a pain, but more than that, I'm afraid it would bork my fusion drive, even if I'm careful to never boot to OS X with the SSD disconnected.
    A lot of places said that this error results from a borked MBR, and suggest using a tool like gptfdisk to rewrite it. I followed the instructions [here](https://discussions.apple.com/thread/4144252?start=0&tstart=0), but *that* didn't work either.
    I am now completely at a loss as to how to proceed, and Google isn't much help either.
    In conclusion, here is some information that you may find helpful:
        $ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *240.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:          Apple_CoreStorage                         239.7 GB   disk0s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk1
       1:                        EFI                         209.7 MB   disk1s1
       2:          Apple_CoreStorage                         648.4 GB   disk1s2
       3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
       4:       Microsoft Basic Data BOOTCAMP                100.9 GB   disk1s4
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Mayfly                 *884.0 GB   disk2
    $ diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 63DC419F-1A09-4C5B-977A-F59F79502CA1
       =========================================================
       Name:         FusionDrive
       Size:         888087773184 B (888.1 GB)
       Free Space:   0 B (0 B)
       |
       +-< Physical Volume B1B14251-2DB3-491C-9E7A-5C2FD11881BA
       |   ----------------------------------------------------
       |   Index:    0
       |   Disk:     disk0s2
       |   Status:   Online
       |   Size:     239713435648 B (239.7 GB)
       |
       +-< Physical Volume D0BA2837-514D-4620-8E1D-26D18137CA94
       |   ----------------------------------------------------
       |   Index:    1
       |   Disk:     disk1s2
       |   Status:   Online
       |   Size:     648374337536 B (648.4 GB)
       |
       +-> Logical Volume Family 736A8900-FE9C-4342-A932-EDC35444774C
           Encryption Status:       Unlocked
           Encryption Type:         None
           Conversion Status:       NoConversion
           Conversion Direction:    -none-
           Has Encrypted Extents:   No
           Fully Secure:            No
           Passphrase Required:     No
           |
           +-> Logical Volume B4997853-59F8-4480-BB48-3481B2F2A123
               Disk:               disk2
               Status:             Online
               Size (Total):       884000030720 B (884.0 GB)
               Size (Converted):   -none-
               Revertible:         No
               LV Name:            Mayfly
               Volume Name:        Mayfly
               Content Hint:       Apple_HFS
    $  sudo gpt -r -vv show disk1
    Password:
    gpt show: disk1: mediasize=750156374016; sectorsize=512; blocks=1465149168
    gpt show: disk1: Suspicious MBR at sector 0
    gpt show: disk1: Pri GPT at sector 1
    gpt show: disk1: Sec GPT at sector 1465149167
          start        size  index  contents
              0           1         MBR
              1           1         Pri GPT header
              2          32         Pri GPT table
             34           6        
             40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  1266356128      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
    1266765768     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
    1268035304         280        
    1268035584   197111808      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
    1465147392        1743        
    1465149135          32         Sec GPT table
    1465149167           1         Sec GPT header
    $ sudo fdisk /dev/disk1
    Disk: /dev/disk1     geometry: 91201/255/63 [1465149168 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   2 - 1023 254  63 [         1 - 1268035583]     *2: 07 1023 254  63 - 1023 254  63 [1268035584 -  197111808] HPFS/QNX/AUX
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused

    My setup is very similar to your's, Ryan, on a Mac Mini5,2 and the ordering is different and Winclone was not used.
    1. New Mini with internal 500GB with Mountain Lion(ML), put into an external FW enclosure, so the Mini can/could be booted using an external drive for contigency.
    2. Replaced internal stock HDD (500Gb/5400rpm) with SSD/HDD (256Gb SSD/1TB 5400rpm).
    3. Installed W7 x64 on 64GB partition on HDD, which was a single-partition drive to begin with.
    4. The remaining HDD partition and the entire SSD was put into a Fusion drive.
    5. Using Command-R, new ML installed on Fusion HD.
    Here is what I currently have...(Disk0 - SSD, Disk1- 1TB HDD, Disk2 - Fusion, Disk3 - External FW).
    diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *256.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:          Apple_CoreStorage                         255.7 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                         934.5 GB   disk1s2
       3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
       4:       Microsoft Basic Data BOOTCAMP                64.9 GB    disk1s4
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Fusion HD              *1.2 TB     disk2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk3
       1:                        EFI                         209.7 MB   disk3s1
       2:                  Apple_HFS Rescue HD               371.8 GB   disk3s2
       3:                  Apple_HFS Leopard HD              31.9 GB    disk3s3
       4:                  Apple_HFS Snow Leopard HD         31.9 GB    disk3s4
       5:                  Apple_HFS Lion HD                 31.3 GB    disk3s5
       6:                 Apple_Boot Lion Recovery HD        650.0 MB   disk3s6
       7:                  Apple_HFS Mountain Lion HD        31.3 GB    disk3s7
       8:                 Apple_Boot Mountain Lion Recove... 650.0 MB   disk3s8
    diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group A8C00490-0E14-401F-AB69-59F37724E8C4
        =========================================================
        Name:         Fusion
        Size:         1190201270272 B (1.2 TB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 4772013B-5520-4801-9BE5-BCAEF4AEDAB3
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     255716540416 B (255.7 GB)
        |
        +-< Physical Volume A679A101-3C78-4A59-B5EE-A4339210CFAD
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     934484729856 B (934.5 GB)
        |
        +-> Logical Volume Family 5EF5C7CA-0B9C-4169-82A1-41C84F206672
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume 1512657C-ED13-4B31-82C6-7AECBBCA7F98
                Disk:               disk2
                Status:             Online
                Size (Total):       1185508581376 B (1.2 TB)
                Size (Converted):   -none-
                Revertible:         No
                LV Name:            Fusion HD
                Volume Name:        Fusion HD
                Content Hint:       Apple_HFS
    sudo gpt -r -vv show disk1
    gpt show: disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168
    gpt show: disk1: Suspicious MBR at sector 0
    gpt show: disk1: Pri GPT at sector 1
    gpt show: disk1: Sec GPT at sector 1953525167
           start        size  index  contents
               0           1         MBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  1825165488      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC
      1825575128     1269544      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      1826844672   126679040      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      1953523712        1423        
      1953525135          32         Sec GPT table
      1953525167           1         Sec GPT header

  • Can I bootcamp Windows on SSD instead of Fusion Drive?

    Hi guys,
    I have a base retina iMac which I have boot camp Windows 8.1 on it. However, I would like to know if I can improve the performance of Windows 8.1, like installing Windows 8.1 on SSD part instead of HDD?
    If not, how can I improve the performance of windows 8 on fusion drive?
    thanks

    Hi, Sorry for the late reply...
    Here's what I got...
    diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *121.3 GB   disk0
       1:                        EFI 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 EFI                     209.7 MB   disk1s1
       2:          Apple_CoreStorage                         441.5 GB   disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
       4:       Microsoft Basic Data BOOTCAMP                557.8 GB   disk1s4
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                  Apple_HFS Macintosh HD           *557.0 GB   disk2
                                     Logical Volume on disk0s2, disk1s2
                                     4AF164C1-45E3-48A3-93CA-51CE5DF7011A
                                     Unencrypted Fusion Drive
    diskutil cs list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group E97FFD32-8648-4CA3-B8E8-44589594E6F8
        =========================================================
        Name:         Macintosh HD
        Status:       Online
        Size:         562498494464 B (562.5 GB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 474F7386-3E05-4500-ADAB-5F91269183B6
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk0s2
        |   Status:   Online
        |   Size:     120988852224 B (121.0 GB)
        |
        +-< Physical Volume 7ACB35A3-83FA-4572-99C2-16F1FA925A48
        |   ----------------------------------------------------
        |   Index:    1
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     441509642240 B (441.5 GB)
        |
        +-> Logical Volume Family BA6AFD64-62E4-4230-ACD5-D3256A3D0347
            Encryption Status:       Unlocked
            Encryption Type:         None
            Conversion Status:       NoConversion
            Conversion Direction:    -none-
            Has Encrypted Extents:   No
            Fully Secure:            No
            Passphrase Required:     No
            |
            +-> Logical Volume 4AF164C1-45E3-48A3-93CA-51CE5DF7011A
                Disk:                  disk2
                Status:                Online
                Size (Total):          557000032256 B (557.0 GB)
                Conversion Progress:   -none-
                Revertible:            No
                LV Name:               Macintosh HD
                Volume Name:           Macintosh HD
                Content Hint:          Apple_HFS

Maybe you are looking for