I would like to use an intel H10 optane SSD module to create a fusion drive container for an osx install.
I have an MSI b360i pro AC mobo with intel i5-8400 amd rx580 8gb and 2x 8gb ddr4 2666
Its all in a Dan case with the HdPlex 400w Pure DC PSU
Its running windows on a Toshiba KXG5A 512 SSD which is fast but i wanted to install osx and I wanted to use a new drive for that, I chose the H10 intel optane drive because from what I gather if I dont use any optane software or bios settings it will appear as two drives to the UEFI firmware, one 32gb Optane drive and the 512 SSD, I wanted to know if I could use this as a fusion drive container. Has anyone done this? Also I need to figure out the DSDT or clover setup to use to make this mobo boot with the hardware I have. I havent built a osx86 box since ML but I think that i can figure it out with some help. Thanks.
I would like to try to install Catalina on a 64 GB flash drive, in order to bypass the SATA issue. I so thay many managed to do that on external SSDs.
Actualy, already tried it. The first step finished ok, just it took much longer. After first booting from the target flash drive from the installing flash drive, it blocked on something like ”installer will create a non-removeable partition”. Perhaps if I waiting long enough, I would have passed that phase, but there were already some 15 minutes since it blocked.
Here is a new utility to patch the EFI firmware in VMware Workstation and Fusion to allow the non-server versions of Mac OS X 10.5 (Leopard) and 10.6 (Snow Leopard) to run. Yoiu will need macOS unlocker 3 if you are using Workstation on non-Apple hardware. I still have to find a way to do this on ESXi as the UEFIPatch utility will not run in the ESXi console.
This currently supports:
Workstation 11/12/14/15 on Windows and Linux
Workstation Player 7/12/14/15 on Windows and Linux
Fusion 10/11 on macOS
Please read the readme.txt file for details.
Hey guys, I have a ridiculously convoluted issue. Take a seat.
I am trying to use Logic Pro X on a 2012 Mac Mini I have, but I currently have Snow Leopard OS X 10.6.8, and will need to update to Sierra 10.12. However, I realize I need to update to a newer OS such as El Capitan in order to be able to update to Sierra. Except I cannot sign into the App Store. I am greeted with an error message along the lines of "this computer or device cannot be verified." So I did some digging and it seems to be because my Ethernet port and Wifi don't work. I use a USB Wifi adapter to get around this but now it seems like I finally have to fix it for good so I can get into the App Store to get these updates I need.
In System Preferences > Network, I do not see Ethernet or Wifi listed. Only my USB Wifi Adapter and Firewire. In System Profiler > Hardware > Ethernet Cards, it says, "This computer does not appear to have any PCI Ethernet cards installed."
I'm pulling my hair out over here to get Logic Pro X on this computer, that's all that I really want, and that's all I want this computer to do. If you can help, God bless your soul.
I have 5 disks including four SSDS and a 4TB HDD configured in a CoreStorage (Fusion drive) volume.
I have Filevault enabled also.
When I turn on my hackintosh, I am presented with the Filevault screen to select my user, enter my password and continue to decrypt and boot macOS. This works around 80% of the time with no issues at all.
Sometimes with seemingly no identifiable pattern, after I enter my password it just hangs on the Filevault screen with the loading bar and does not progress. There is no disk activity either. After a while of the hanging, it will just display the prohibitory sign against a black background.
I have to force shut the hackintosh off with the power button and try to boot again. Usually after I do this, it will boot the second time.
I'm currently running Sierra 10.12.6 but this has also happened when I tried 10.13 too.
Clover is fully up to date as of today (r4380).
Does anyone know why this might occur?
The only thing I have picked up on is the drives change disk identifiers and move themselves around (eg. /dev/disk1) during different boot ups so maybe it's getting confused when trying to decrypt and boot as a corestorage volume. I have no idea how to prevent this from happening either.
Any help or suggestion would really be appreciated.