Negative, in the bios setup where the raid is located it is set to enable or disable. Additionally for each disk is the same, enable or disable. I have read that this is possibly set up by default in the os but in either case I have raid disabled in my bios as it was causing issues, for instance I tried to transfer a large file and it unmounted the disk and the other issue was it refusing to accept the boot1h command.
I think but not sure, that if you use the chameleon installer and then enter the raid id that, that is all you have to do to get it to boot without ever having to use the terminal. I would test it but I have reset the drive many times and I would like to get moving forward if you know what I mean. I just recently solved an issue where the computer would randomly freeze while playing c&c3 "real headache" I thought that I would never have it stable but I learned about the 4gb not being addressed in 64 bits.
I will share all of my work on the wiki compatibility page.
Hi, I was having some difficulty. I read in one of your earlier posts about how the bus has limits. I put an additional drive in there and now I get random lockups when copying data to the disk. I cant copy hardly anything to it because it just stops copying but thinks it is. I have read in other posts that the sata isnt stable with an nforce board but didnt have too many problems until now. Now it locks up regularly. Do you think that the bus could be overloaded or mabe the driver I have is just unstable. I did have freezing problems before but not to this degree.
The resource busy error was due to me booting with the drive in raid. You have to create the raid while osx is running and you cant reboot because for some horrible reason osx uses the disk and you cant fix it. I was also having trouble restoring images to the raid where it would time out so I had to boot up from a ide drive and then copy it to the raid. All in all I have had quite alot of problems all related to the sata controller. I was able to run xbench with the 3 drives but only scored a 180 woohoo
I had 4 x Samsung 1TB drives raided with my Asus P5E3 wireless @n board for 6 months and it never put a foot wrong. I would think your stability problems are most definitely caused by the Nvidia chipset. With those drives and 9800 GTX + Quad Core @ 3.6 I was scoring 310 in X Bench. Having said that, X Bench is totally unreliable as it has not been updated for years and for the current crop of graphics cards.
Thanks! I'm writing now from raid0 booted hackintosh! One thing that took a while to figure out is what to do with the modified com.apple.boot.plist. First I copied it to the Library/Preferences/SystemConfiguration on the raid volume, but that didn't work. After a while I found out that you should modify the com.apple.boot.plist in the mounted disk2S3 and disk3S3 partitions.
Oh, and as someone mentioned before ~/desktop should be ~/Desktop
I can confirm now that all you have to do is input the raid id and then run the chameleon installer on it. Although worth noting that it wont boot unless you manually tell the bios to boot on the first drive only.
I really would prefer the code way so I can learn but this nforce chipset man. thanks for the journey.
Hi guys, first time poster here aka a noobe, so bare with me. I'm very interested in giving this a try BUT I have Leo 10.5.6 operating on my system that was installed using a variation of the Boot 132 method. Can this be done with a retail install? If so do I follow the same steps.
aquamac, Thx for the breakdown. I've bounced around two a few postings about using the Unique Identifier vs the Raid Identifier, and I've been back and forth trying to get mine to fly. Closest I seem to get is it giving me the 5 seconds to add boot options then it shows: h(0,3) Boot OSX, and wants me to add options. It doesn't seem to recognize the mach_kernel.voodoo, so I fire it up with just mach_kernel but it bails out part way thru saying the UUID of the on-disk kernel, and proceeds to have several link/load errors.
I attempted to CCC from a working Disk to a Raid Stripe, and chased it with a Universal OSx86, then your uuid= reference with both the Unique or Raid Idendifiers. Do you only get one shot with the UUID / Raid Identifier and fdisk stuff? Currently running (2) 320Gig WD HDD's on a Asus P5N32-SLI Deluxe (nforce4)