Jump to content

Fusion Drive or not?


HBP
 Share

14 posts in this topic

Recommended Posts

ok, after many many months of using this drive on 10.9x, and many updates up to 10.9.4 I have a question.  is this really a Fusion drive or not?  we have been touting that all you have to do is put the SSD first and the CS will sort everything else out, but in my case it hasn't.  I used this guide #1 to setup my drives, and as far as I can tell have never gotten any speed increase at all.  Using black magic disk benchmark allowed me to BM it when it was freshly made, 130MB per sec while the SSD is humming along @ 500MB per sec. is there a flag we are missing that flips on the Fusion Drive functionality?

 

HBP

Johns-iMac:Library test$ diskutil corestorage list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group FFC095BF-FB5E-4324-B598-DA80CA7AB4B0
=========================================================
Name: fusion
Status: Online
Size: 1238926282752 B (1.2 TB)
Free Space: 0 B (0 
|
+-< Physical Volume 2FD21EC8-17BE-409C-9680-D85CC3449AA7
| ----------------------------------------------------
| Index: 0
| Disk: disk0s3
| Status: Online
| Size: 239581159424 B (239.6 GB)
|
+-< Physical Volume CAA0A89E-DA4D-4CC0-B747-B4C70C4FF133
| ----------------------------------------------------
| Index: 1
| Disk: disk1s2
| Status: Online
| Size: 999345123328 B (999.3 GB)
|
+-> Logical Volume Family A43414E3-0BF3-4DF0-949E-041FDB653AB0
----------------------------------------------------------
Encryption Status: Unlocked
Encryption Type: None
Conversion Status: NoConversion
Conversion Direction: -none-
Has Encrypted Extents: No
Fully Secure: No
Passphrase Required: No
|
+-> Logical Volume 9BE06E14-45B0-42D2-8DC3-6FFA4D512706
---------------------------------------------------
Disk: disk2
Status: Online
Size (Total): 1234623901696 B (1.2 TB)
Conversion Progress: -none-
Revertible: No
LV Name: Fusion HD
Volume Name: Fusion HD
Content Hint: Apple_HFS
Johns-iMac:Library test$ diskutil corestorage info FFC095BF-FB5E-4324-B598-DA80CA7AB4B0
Core Storage Properties:
Role: Logical Volume Group (LVG)
UUID: FFC095BF-FB5E-4324-B598-DA80CA7AB4B0
LVG Name: fusion
LVG Version: 1
LVG Size: 1238926282752 B
LVG Free Space: 0 B
LVG Status: Online
LVG Sparse: No
Fusion Drive: No
Link to comment
Share on other sites


Johns-iMac:Library test$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS Fusion_Host 10.0 GB disk0s2
3: Apple_CoreStorage 239.6 GB disk0s3
4: Apple_Boot Boot OS X 134.2 MB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI 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 Fusion HD *1.2 TB disk2
Logical Volume on disk0s3, disk1s2
9BE06E14-45B0-42D2-8DC3-6FFA4D512706
Unencrypted

Link to comment
Share on other sites

Offhand it looks fine to me.

This is the guide I used way back when... but if you use clover that last part is different of course.

http://www.macbreaker.com/2012/12/how-to-set-up-fusion-drive-on-hackintosh.html

 

But then again, your core storage output looks off because nothing is indented. Is it possible you just made a logical group and not a fusion drive?

Link to comment
Share on other sites

the issue come about that I am not receiving any benefit from the SSD, speeds are consistent with what my Platter drive was before doing this. I do not use clover, I use ozmosis, which will boot off any efi visible boot volume, so when OS X blesses the fusion drive as bootable it is.

 

right now backing it up to break the drive down again...

 

HBP

Link to comment
Share on other sites

If you created it on a clean install of 10.9.x it should be correct. It looks like it is. When people first started making fusion drives in ML, a lot of them weren't actual fusion drives because the "correct" (in other words, clean install from 10.8.4 or later) version of disk utility wasn't used. So after I upgraded to mavericks I did the process over again.

 

I don't think there's any sure way to check if it's working properly as a fusion drive other than measuring the reads and writes of each drive.

 

I would just re-do the fusion drive setup from scratch.

Link to comment
Share on other sites

thank you for the input, but I believe almost everyone who is out there playing with this has not been actually using a Fusion drive...

after refollowing the steps from the before mentioned guide, I got to the part of making a LVG, but I named it 'FUSION' without the ' marks, then I went into disk utility (the Graphical interface) and did a repair disk on it, it asked it I wanted to restore a working Fusion Drive. I clicked yes.  and now I have a Fully working Fusion Drive.

 

BEFORE:

Johns-iMac:Library test$ diskutil corestorage info FFC095BF-FB5E-4324-B598-DA80CA7AB4B0
Core Storage Properties:
Role: Logical Volume Group (LVG)
UUID: FFC095BF-FB5E-4324-B598-DA80CA7AB4B0
LVG Name: fusion
LVG Version: 1
LVG Size: 1238926282752 B
LVG Free Space: 0 B
LVG Status: Online
LVG Sparse: No
Fusion Drive: No

AFTER:

Johns-iMac:~ test$ diskutil cs info 6F050F63-F87A-4690-AED4-7274C27DAC09
Core Storage Properties:
   Role:                       Logical Volume Group (LVG)
   UUID:                       6F050F63-F87A-4690-AED4-7274C27DAC09
   LVG Name:                   FUSION
   LVG Version:                1
   LVG Size:                   1249576288256 B
   LVG Free Space:             57344 B
   LVG Status:                 Online
   LVG Sparse:                 Yes
   Fusion Drive:               Yes

time to restore and enjoy life.

 

the code I used to create this Drive is bellow where disk0 is SSD and disk1 is platter drive. 

diskutil cs create FUSION disk0 disk1

HBP

Link to comment
Share on other sites

Interesting. Mine doesn't even say Yes or No for Fusion Drive, it just looks like this:

diskutil cs info 25BBC571-DF53-485D-B7AE-F4A553926A69
Core Storage Properties:
   Role:                       Logical Volume Group (LVG)
   UUID:                       25BBC571-DF53-485D-B7AE-F4A553926A69
   LVG Name:                   Fusion Drive
   LVG Version:                1
   LVG Size:                   868986765312 B
   LVG Free Space:             106496 B
   LVG Status:                 Online

I also noticed that diskutil cs list tells me I have 106.5 kb free on my LVG, which is clearly not the case, I actually have 399GB free.

 

 

I'm assuming that means that my LVG is NOT a true Fusion Drive. So is the trick for it being a Fusion drive to name it 'FUSION' or is it the disk repair part (or both)? Also where did you figure out this was the correct way to do it, or was it just trial and error?

Link to comment
Share on other sites

checked it against another Hack I setup for a friend who I named the LVG 'fusion' and it showed the same, that it was Sparse and a Fusion Drive, so I believe that CS treats the LVG 'FUSION' and 'fusion' differently then other names/tags and sets up the binding accordingly.

 

that readout is from diskutil in 10.10 which is one of the ways I knew that I didn't have a real fusion drive. after setting it up right I have speeds of my SSD for 90% of the stuff I do, even though I just CCC'd my old drive (the one that was from the Failed attempt at a fusion drive) back over onto it.

 

it is still learning, but I would say that it excels at what it does, and 250GB was plenty of SSD for the 1.2 TB fusion drive.

 

HBP

Link to comment
Share on other sites

  • 2 months later...

This is very interesting. But, I wonder if it just expects a capital "F" in "Fusion", because this is my output, drive created in Mavericks, but Terminal output from Yosemite:

diskutil cs info D2C8C77B-CDDF-46F5-98E1-629405D40026
Core Storage Properties:
   Role:                       Logical Volume Group (LVG)
   UUID:                       D2C8C77B-CDDF-46F5-98E1-629405D40026
   LVG Name:                   Fusion Drive
   LVG Version:                1
   LVG Size:                   1249576288256 B
   LVG Free Space:             0 B
   LVG Status:                 Online
   LVG Sparse:                 Yes
   Fusion Drive:               Yes

Interesting. Mine doesn't even say Yes or No for Fusion Drive, it just looks like this:

diskutil cs info 25BBC571-DF53-485D-B7AE-F4A553926A69
Core Storage Properties:
   Role:                       Logical Volume Group (LVG)
   UUID:                       25BBC571-DF53-485D-B7AE-F4A553926A69
   LVG Name:                   Fusion Drive
   LVG Version:                1
   LVG Size:                   868986765312 B
   LVG Free Space:             106496 B
   LVG Status:                 Online

I also noticed that diskutil cs list tells me I have 106.5 kb free on my LVG, which is clearly not the case, I actually have 399GB free.

 

 

I'm assuming that means that my LVG is NOT a true Fusion Drive. So is the trick for it being a Fusion drive to name it 'FUSION' or is it the disk repair part (or both)? Also where did you figure out this was the correct way to do it, or was it just trial and error?

 

 

Is this output from Yosemite or Mavericks?

I'm inclined to think "diskutil cs" has been updated in Yosemite, as the man page shows June 2014.

 

'diskutil info diskX' should reveal Fusion drive status, as well:

(Last few lines):

   This disk is a Core Storage Logical Volume (LV).  Core Storage Information:
   LV UUID:                  FC33E586-03D7-480A-B471-0E9B761B342C
   LVF UUID:                 50389DB3-53A2-4C16-AF3A-38983B199A6C
   LVG UUID:                 D2C8C77B-CDDF-46F5-98E1-629405D40026
   Fusion Drive:             Yes
   Encrypted:                No

MAJ

Link to comment
Share on other sites

  • 10 months later...

I recently had to recreate my Fusion Drive, which I was using since 10.8.3 or .4 and which ran perfectly fine (used iostat to verify). Since the HDD recently died, I had to recreate the drive. However, diskutil info and diskutil cs info always claim that what I created was not a Fusion Drive. I tried El Capitan and Yosemite to create the Fusion Drive to no avail. I'm downloading Mavericks right now.

I tried names like "Fusion Drive" (which worked before), "Fusion", "FUSION" and "FUSE", but that did not change anything. 

 

Funny thing is: A few weeks ago, I upgraded a friend's iMac and replaced the Superdrive with an SSD. I then used a thumb drive with the Yosemite installer to create the Fusion Drive (naming it "Fusion Drive" as I always do) and it worked absolutely fine! The iMac is on a model that never sold with a Fusion Drive (Late 2011 AFAIK).

 

Does anyone know what exactly causes Disk Utility (the GUI version) to claim that the Fusion Drive needs repair? From what I've heard, on iMacs sold with a Fusion Drive, there must be some magic string in the NVRAM that causes Disk Utility to always recreate the Fusion Drive if it ever gets broken. Is there any more info on that?

Link to comment
Share on other sites

 Share

×
×
  • Create New...