Me and SDDs don't get along too well. I have a 120GB mSATA drive in a SATA3 enclosure and when I used OS X to format it OS X bricked it. I had to use both Linux and Windows 8.1 to bring it back from the dead. It now stays formatted in NTFS because HFS+ nearly killed it (it wiped out the serial number, too) and since Linux can write to an NTFS partition that seems the best way to go.
Tony has a section devoted to SDDs and multi booting. Me, I probably would have gone with a Samsung Pro (MLC) SDD, but I don't like the idea of installing a M.2 SATA type drive on my mobo, unless it was an ITX mobo, of course.
Since it is an SSD you will probably need to use UEFI boot records, and you should select an SSD that Tony has found to work well with OS X.
http://www.tonymacx86.com/buyersguide/may/2016#Solid_State_Drives
Cutting edge:
http://www.tonymacx86.com/threads/os-x-driver-for-nvme-m-2-solid-state-drives-released.181387/
As far as bricking a system goes, you'll just have to take the chance, like the rest of us who love to learn from our mistakes.
(I had a hard time getting my HD to boot from the HD instead of USB and I was finally able to get it all sorted out; I used the latest MultiBeast and the latest Clover and a whole lot of help from the good folks here on Tony's website.
Booting type problems first start with the Mac ID selection, so see if the default 3,1 profile works. Once you get that going don't jump into making it a 14,2 or 15,1, for example. No, what you want to do is to make the HD bootable. There are threads elsewhere that should help. Once you get the HD to boot then you can use Clover to make the changes on the HD. Once it boots from HD and you've changed the ID profile you will probably get devices not working that worked with the Mac Pro 3,1 profile. That's when you need to get into the "nuts and bolts" (like clearing nvram and kernel caches and adding kext files manually).
My first suggestion for anyone who wants to use SSDs is to make sure that the motherboard has the maximum amount of memory the motherboard can take. In the case of my Z97 it is 32GB. Had I bought a Skylake board it would have forced me to install 64GB of memory, and because DDR4 2133 men is slower than DDR3 1600 or 2400 memory I would have had to get a Z170 board so that I could install 64GB of DDR 3200 memory, which cost $300 - $600 back in January, depending on the motherboard. Why max men? So that I could turn off Swap Space. Both Linux and Windows allows tweaking the SSD to allow the most performance and reliability from an SSD; I don't know what they are in OS X, yet. (And to tell you the truth I'm not in any hurray to find out.)
If you have a really powerful mobo, CPU, with MAX men you could run OS X under VMWare under Windows or Linux. That presents it's own set of problems, though. There's a section for running OS X under VMWare elsewhere on Tony's site.
I just looked at your ASUS Asus H61m. Hmmm, 16GB men sticks could be pricey... That's why I won't buy a mobo unless it has 4 men slots... 32GB would cost about $250. That's just a little bit more than what I paid for my 32GB. Unfortunately your H61MA can only support 16GB. That's the minimum I would install. After all, it's only about $50 for two 8GB sticks.
When working with your mobo the first thing you want to do is to disable all the "C" States in the BIOS, so that it doesn't go to sleep, it doesn't Hibernate, it doesn't go into Deep Sleep, etc. With PowerSaving turned off you won't need CSM to be enabled in the BIOS, either, which should allow the PC to boot faster. Only after you have a working Mackintosh should you play around with Power Saving settings because you won't know if you're chasing a video problem, a power setting problem, a kernel panic problem, etc.
My suggestion is to look at the other threads here that discuss "Won't Boot from Hard Disk" problems. If you boot from UEFI-USB then you may want to stick with the MultiBeast Legacy boot loader so that you can use the keyboard Function key to boot individually to either disk. Otherwise the first disk will have its boot record(s) modified and if the first disk drive ever dies you will have to boot from USB to get to the second drive.
My suggestion would be:
1] Boot Multi boot and install the OS.
2] Shut down the PC, remove the Usb, power up the PC and see if it boots from the disk.
3] if it doesn't boot from USB, power down the PC, insert the USB, turn on the PC, boot into the disk.
4] Copy MultiBeast, EFMounter and Clover onto your desktop.
5] Run MultiBeast, select Legacy Bootloader, install to the disk.
6] Shutdown the PC, remove the USB stick.
7] Power up the PC and see if it boots into the disk. (Good chance that it will.)
8] See if you can get out into the Internet. (Chances are good that you can.) Set the System Sound Preferences to Output -> Built-In. Sound may not work, so start MultiBeast from your desktop, select the Audio controller, Build, Install on the disk. Shutdown and re-start the PC.
9] Login and run MultiBeast from your Desktop. Does Sound work? If so, Add any other devices, as necessary, Build, Install to the disk. Reboot.
10] Once you know everything works fine you may now install the nVidia WebDriver if necessary. Reboot and see if the Display is set correctly. If it is, now, and only now, after you know everything works (USB slots, Audio, Ethernet, Video) should you try to change the Mac system ID.
11] Start Clover from your Desktop. Select an ID closest to your CPU type. Save to the disk. Reboot. Recheck USB, Audio, Ethernet, Video. Chances are good that some drive or other will not work correctly. It's "Nuts and Bolts" time... Rerun MultiBeast until everything works.
12] Now, and only now, should you play around with enabling BIOS and Clover C States and Power Saving Settings.
How to Copy USB EFI contents to System Drive EFI
- If you can only boot from USB installer and not the system drive, boot from the USB installer to the desktop
- Mount both EFI partitions. Tools such as EFI Mounter v3 don't always like mounting two EFI partitions at once, so try terminal commands like this:
Code (Text):
mkdir /Volumes/EFI && sudo mount_msdos /dev/disk0s1 /Volumes/EFI
mkdir /Volumes/USBEFI && sudo mount_msdos /dev/disk1s1 /Volumes/USBEFI
(those IDs are for only one internal and one external drive; to identify the right disk IDs, run "diskutil list" and look for the EFI partition just before the one named for your system drive, or named for the USB drive)
- You should see both EFI partitions in Finder. The system drive EFI should have a hard drive icon and the USB EFI should have an external drive icon and an eject icon
- Go to the system drive EFI (hard drive icon) and delete everything inside EFI/CLOVER/
- Go to the USB drive EFI (external drive icon) and copy everything from inside EFI/CLOVER/ to the EFI/CLOVER/ directory of the system drive EFI (drag and drop in Finder or whatever.
http://www.tonymacx86.com/threads/big-list-of-solutions-for-el-capitan-install-problems.173991/
BTW, after you install the OS and reboot through USB, copy MultiBeast to the desktop, then run Multibeast from the desktop and after selecting your bootloader build and install to your HD. Shutdown the PC, remove the USB stick, power on the PC and use the F key to get to the boot selection. You will probably see MAC OSX as a boot selection. It didn't work for me. But when I selected the SATA channel that MultiBeast installed onto (P3 xxxxxxxxx for me) it boots fine. Once Clover has been saved to the disk that's when you can now play around with installing the rest of the drivers and changing the MAC ID. When you download and install Clover onto your desktop make sure you mount the disk EFI partition and once mounted navigate to the EFI .plist file. When you double click it you should be able to now make modifications and when you exit it will save it to the disk.
