Jump to content
InsanelyMac Forum
  • Announcements

    • Allan

      Solution to create a topic or post.   04/24/2018

      Hello guys. The majority of you are having issues to create a topic or post here. This are a problem with our current theme InsanelyMac.  Now the theme will be the Default IPS. Sorry for any inconvenience.
Sign in to follow this  
Derty

Fusion drive on older Macs? YES!

Recommended Posts

Advertisement

Maybe like in RADI boot - Chameleon should pass Fusion volume UUID to kernel instead of physical partition UUID?

 

I googled that and and I think I get how this should work, but I don't know how to exactly do that. I added something like this to my org.chameleon.boot.plist:

- Add "rd=uuid boot-uuid=506D8F03-0596-32D8-BE0B-E3A4E7D5C72A" to your kernel flags

but chameleon still didn't show the fusion partition. Could you maybe help me with that?

Share this post


Link to post
Share on other sites

Well, I did not set up any fusion drive so I can only write in theory. You should specify

boot-uuid=<root voluem uuid>

in Chameleon command line or in boot.plist (in Kernel Flags) as you already did. And in theory that should be enough.

 

But, note: Chameleon does not see fusion drive . It can only see separate physical partitions. If those fusion partitions are visible in Chameleon and if they (or one of them) contains kernelcache and other files needed for initial boot, then your boot should start from there (you should select it).

 

Chameleon should then read kernelcache and other stuff it needs from that physical partition, but will pas given boot-uuid to kernel, and kernel will wait until volume with that boot-uuid becomes available (when needed drivers for fusion drive are loaded and fusion drive inited) and then should use it as root drive.

 

Edit:

"man diskutil" tells that physical partitions that make core storage volume will be "converted" or re-typed from standard Apple HFS to Apple_CoreStorage type (GPT type GUID: 53746F72-6167-11AA-AA11-00306543ECAC ?). If this is correct, then this will make them invisible to Chameleon, right?

 

If that's the case, then this type should be added to Chameleon like there is already GPT_HFS_GUID and GPT_BOOT_GUID in libsaio/disk.c - and then they should be visible in Chameleon's menu.

Share this post


Link to post
Share on other sites

Taruga tested booting from CoreStorage volume here - it works. Booted by Clover, but I would expect that it's possible with Chameleon also.

 

And to correct myself from the above post: Apple_CoreStorage is probably not pure HFS+ volume plus Taruga says that OSX adds boot helper partition with that CS volume (like in RAID config), so adding Apple_CoreStorage type to Chameleon is a bad idea. Booting should start from that boot helper partition.

Share this post


Link to post
Share on other sites

Taruga tested booting from CoreStorage volume here - it works. Booted by Clover, but I would expect that it's possible with Chameleon also.

 

And to correct myself from the above post: Apple_CoreStorage is probably not pure HFS+ volume plus Taruga says that OSX adds boot helper partition with that CS volume (like in RAID config), so adding Apple_CoreStorage type to Chameleon is a bad idea. Booting should start from that boot helper partition.

 

Somehow it works here, too. Chameleon is installed on a thumbdrive, so the computer boots from there. Chameleon doesn't show the fusion drive or one of the partitions included in the fusion drive, but when I select my bootable ML install data partition, it boots from the fusion partition instead since I included the

boot-uuid=<root voluem uuid>

flag. This works for now, but it would be nice if I could get Chameleon (or Clover if that's better) to show the fusion partition.

 

Thanks for your help!

Share this post


Link to post
Share on other sites

That probably won't happen. How I understood it so far you need some boot helper partition that contains kernel and other basic stuff. You are using your another ML for that now.

Share this post


Link to post
Share on other sites

Hi - I have Fusion working on my 2011 Mac mini Server loaded with osx10.8.2 (non server version). It works fine and i am impressed.

 

However in my Hackintosh I have an M4-CT128M4SSD2 SSD which I have attempted to Fusion pair with a WD WDC WD1502FAEX 1.5Gb disk.

 

I have tried a number of combinations even another WD drive but during the Fusion setup process I get this POSIX error

 

"Error 22: POSIX reports: invalid argument"

 

All searches on the web do not give any reason or info regarding error 22. Any ideas would really be appreciated?

 

It appears to happen after Fusion formats the second drive, unmounts it and on attempting to remount it the error appears, as stated I have tried different drive as the HD (both WD), I wondered whether my system still sees the drives as "external" although I have used the vanilla 10.8.2 IOBlockstorage.kext and an amended one but always the same error... It would appear that POSIX errors refer to external drives.. Any ideas or suggestions would be appreciated as a web search shows nothing- Thanks..

Share this post


Link to post
Share on other sites

I have gotten odd errors similar to that while trying to do disk operations that require rdisk access and you only have disk access, are you only giving the fusion drive access to part of the HDD? or have you cleared formatted and then unmounted the second drive (the WD) before beginning the process?

 

just a thought due to the way I understand what is going on, it is making a modified raid between the mismatched disks, and it is failing while writing that information to the tail of the second disk the buffer space that OSX uses to boot and do other odd things from due to not owning the whole disk.

 

then you may try running the same commands using your mac mini server as a host and the two drives as externals (via usb/firewire)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.



  • Posts

    • Sadly the revealing information is lying between the 2 pictures
      Press spacebar in Clover and enable the option that says Don't reboot on panic (something like that), it might help taking a better picture.

      I don't really have any experience with High Sierra and laptops,@Allan or others are more knowledgeable on this subject than I

      Envoyé de mon PH-1 en utilisant Tapatalk

    • Well this is what I got: Displays: Framebuffer: 0x2BC4E780 Size: 1600x900 Depth bits Per Pixel: 24 Depth bits Per Sample: 8 Depth is Planar: false Frame: (0.0, 0.0, 1600.0, 900.0) Visible Frame: (37.0, 0.0, 1563.0, 877.0) Depth backing Scale Factor: 1.0 Name: Display Vendor Id: 0x6AF (1711) Product Id: 0x139E (5022) Year Of Manufacture: 2013 Week of Manufacture: 17 Blue Point X: 0.150390625 Blue Point Y: 0.0595703125 Green Point Y: 0.3251953125 Green Point Y: 0.5703125 Red Point X: 0.6201171875 Red Point Y: 0.33984375 White Point X: 0.3134765625 White Point Y: 0.3291015625 White Gamma: 2.20000004768372 Brightness Affects Gamma: true Horizontal Image Size: 380 Vertical Image Size: 210 Has Back light: true Is Digital: true Is HDMI Sink: false EDID data: 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x06, 0xAF, 0x9E, 0x13, 0x00, 0x00, 0x00, 0x00, 0x01, 0x13, 0x01, 0x03, 0x80, 0x26, 0x15, 0x78, 0x0A, 0xC4, 0x95, 0x9E, 0x57, 0x53, 0x92, 0x26, 0x0F, 0x50, 0x54, 0x00, 0x00, 0x00, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x01, 0x1C, 0x2A, 0x40, 0x6E, 0x61, 0x84, 0x0C, 0x30, 0x30, 0x20, 0x36, 0x00, 0x7E, 0xD6, 0x10, 0x00, 0x00, 0x18, 0x00, 0x00, 0x00, 0x0F, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x20, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x41, 0x55, 0x4F, 0x0A, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x20, 0x00, 0x00, 0x00, 0xFE, 0x00, 0x42, 0x31, 0x37, 0x33, 0x52, 0x57, 0x30, 0x31, 0x20, 0x56, 0x33, 0x20, 0x0A, 0x00, 0x24 next step is to integrate relative code in the app
    • Anyone with 3d envy can share his dsdt?
    • Thanks for taking a care in this!   I´m using iMac 18,3 right now   Attaching my IOREG in a dropbox link, apparently it's too big to upload here!  https://www.dropbox.com/s/occwob8acrwk3av/Ritchies iMac 18%2C3.ioreg?dl=0
×