[HELP] RAID1 (Mirror) 10.6.x Chameleon RC5 / Panics / ACPI

[zurie]

I have a beautiful working EP35-DS3P with a DSDT that is so tuned that I only need two kexts (FakeSMC, and a Realtek dummy 889a kext). I originally put my extras in a EFI partition and booted flawlessly from there.

 

Recently I just purchased 2TB x 2 drives and created a Raid1 Mirrored Set. I then proceeded to do a byte clone of my previous HD. Everything is successful.

 

So i attempted to install Chameleon on both raid members Disk0s3 and Disk1s3 (The macos X boot section of each raid device) I followed quite a few tutorials and ended up erasing my EFI partitions of my raid volumes and rendering them as active visible partitions (terrible advice) I even went as far as deleting the EFI partitions completely from my drives and removing them from the partition map completely... so now I have Disk0s1 is the 2TB section of a slice and Disk0s2 is the Mac Boot section of the slice (rather than Disk0s3) EFI is totally gone.

 

Now assuming EFI isn't really used anyway I proceeded. I can get chameleon to boot but when the countdown timer starts to run on my raid boot volume if I hit any key it freezes the counter and never brings up the menu. Also, if i let the timer continue I see that it loads my DSDT and then next screen is a immediate KP "unable to find driver for this platform: ACPI"

 

now if i put chameleon on a USB stick and boot up with the stick and point the UUID of the stick to my raid it works perfectly. 100%

 

so i can easily just boot off the USB stick and keep it as a boot drive (its also got a system on it that doesn't boot but if i use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] or another boot CD i can get the USB stick to boot fine) Maybe this is a blessing in disguise? I'd just like to solve why can't i get my raid1 to boot. I've been doing hackintosh's for 4 or 5 years now and have built 7 hackintosh's for friends and family and always gotten a 100% build. never had problems like this before?

 

Anyone have any RAID1 experience and chameleon - most tutorials are for Leopard, or Striped Raids.. haven't seen a perfect tutorial yet.

 

in my Raid Slice #1 and #2 in my extra / com.apple.boot.plist

 

I have this:

 

DSDT

hd(0,2)/DSDT.aml

 

this gets recognized... also it seems Apple makes a folder called

 

com.apple.boot.S and puts mach_kernel inside it, but if i try and add that to my kernel in the .plist it doesn't like it. if i delete that folder and kernel on reboot its back added by apple.

 

also my kernal flags have my boot-uuid.

 

I can boot off a USB stick and in that stick i added the boot-uuid to the mem stick and it will successfully boot my main drive.

[xenophex]

I run a raid stripe on a few boxes.

 

Things I've had to look out for with Gigabyte UD5/UD7:

1. BIOS needed to use SATA 1 instead of 0 for boot order, or I couldn't even get Chameleon to pop.

2. I've had to move the Extra folder to both disk0s3, disk1s3 aka Boot OSX

3. I use the RAID Identifier and put that in the com.apple.Boot.plist in kernel flags "boot-uuid=YOURUNIQUEID".

 

I notice on every boot the disk order changes on my systems. I run 3 raid stripes in one system (6 drives) and they appear in a different order every time I boot up. Sometimes its disk1s3 and disk3s3 that are my paired "Macintosh HD" stripe.

 

Then there is the question with how it behaves since SATA 1 is possibly the mirror of SATA 0. Thats a interesting one and I'm not certain how that would play out or if you use the bootloader from SATA 1, but tell it to use the default partition of hd(0,2).

 

I recently had fun with the Installer versions of Chameleon. I pull down RC5 r700, and just let it install. All its doing from what i can tell is copying a boot file to my RAID Stripe. I then manually copy that boot file to each Boot OSX. Since as you mention thats not the EFI partition surprise, when I reboot it still said Chameleon RC4 r684. I ended up having to take that boot file, shove it in chameleon RC4's i386 folder, and retrace the directions for a RAID install. Now everything is fine, and Chameleon RC5 r700 shows up.

 

USB sticks are always a nice way to recover from mistakes like this, sounds like your close just figuring out which disk to boot off of. There was only one time on RC4 I just had it state 1 drive even though it was a RAID Stripe, and since, I've only seen DRIVENAME 1 and DRIVENAME 2 or a variation of NAME 1 and Boot OSX.

 

I have a beautiful working EP35-DS3P with a DSDT that is so tuned that I only need two kexts (FakeSMC, and a Realtek dummy 889a kext). I originally put my extras in a EFI partition and booted flawlessly from there.

 

Recently I just purchased 2TB x 2 drives and created a Raid1 Mirrored Set. I then proceeded to do a byte clone of my previous HD. Everything is successful.

 

So i attempted to install Chameleon on both raid members Disk0s3 and Disk1s3 (The macos X boot section of each raid device) I followed quite a few tutorials and ended up erasing my EFI partitions of my raid volumes and rendering them as active visible partitions (terrible advice) I even went as far as deleting the EFI partitions completely from my drives and removing them from the partition map completely... so now I have Disk0s1 is the 2TB section of a slice and Disk0s2 is the Mac Boot section of the slice (rather than Disk0s3) EFI is totally gone.

 

Now assuming EFI isn't really used anyway I proceeded. I can get chameleon to boot but when the countdown timer starts to run on my raid boot volume if I hit any key it freezes the counter and never brings up the menu. Also, if i let the timer continue I see that it loads my DSDT and then next screen is a immediate KP "unable to find driver for this platform: ACPI"

 

now if i put chameleon on a USB stick and boot up with the stick and point the UUID of the stick to my raid it works perfectly. 100%

 

so i can easily just boot off the USB stick and keep it as a boot drive (its also got a system on it that doesn't boot but if i use [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] or another boot CD i can get the USB stick to boot fine) Maybe this is a blessing in disguise? I'd just like to solve why can't i get my raid1 to boot. I've been doing hackintosh's for 4 or 5 years now and have built 7 hackintosh's for friends and family and always gotten a 100% build. never had problems like this before?

 

Anyone have any RAID1 experience and chameleon - most tutorials are for Leopard, or Striped Raids.. haven't seen a perfect tutorial yet.

 

in my Raid Slice #1 and #2 in my extra / com.apple.boot.plist

 

I have this:

 

DSDT

hd(0,2)/DSDT.aml

 

this gets recognized... also it seems Apple makes a folder called

 

com.apple.boot.S and puts mach_kernel inside it, but if i try and add that to my kernel in the .plist it doesn't like it. if i delete that folder and kernel on reboot its back added by apple.

 

also my kernal flags have my boot-uuid.

 

I can boot off a USB stick and in that stick i added the boot-uuid to the mem stick and it will successfully boot my main drive.

[zurie]

booting off the USB stick with the raid UUID makes the Mac assume its booting off the actual drive. the extras are definetally pulling from the RAID, ie: if i delete some properties in my com.apple.boot.plist off my raid drive it updates accordingly. its almost like the USB stick is just a boot loader and thats it. which I guess is fine :\ kinda wish it was all drive, but its not the end of the world. I feel like the drives being 2TB are the issue??? don't really want to format the drives to find out for sure. There is no reason why it can't boot off the raid other than that.. anyone got a 2 TB drive booting chameleon?

 

why would my 2TB drive throw a immediate KP "ACPI" literally at line 0... yet if i boot from that stick its money.

[zurie]

ok update.

 

I pulled one of the Raid drives out, took the second drive and unmarried it from the raid and turned it into a NORMAL 2 TB HD. installed chameleon to it, EFI partition, the works, booted it up flawlessly!! no kernal panic, no errors.

 

Also, I was getting the Debug_DSDT screen on Chameleon RC5 when I had both drives plugged in but I don't get it with one drive.

 

here is my com.apple.boot.plist It was like in Raid1 it wasn't finding my DSDT properly, even though it showed it loaded it, i was getting debug_dsdt and then a KP about ACPI... Maybe there is another way to load the DSDT path wise. being that a raid was Disk0s1 - EFI / Disk 0s2 - TBdrive / Disk0s3 - Boot Mac os X (a raid thing apple does)

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>GeneratePStates</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GraphicsEnabler</key>
<string>No</string>
<key>SystemID</key>
<string>00000000-0000-1000-8000-001D7D017A2A</string>
<key>DSDT</key>
<string>hd(0,1)/DSDT.aml</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>1Kernel Flags</key>
<string>arch=X86_64</string>
<key>Theme</key>
<string>Default</string>
<key>Timeout</key>
<string>5</string>
</dict>
</plist>

 

also in my plist I have my raid UUID but i took it out because i copied and pasted this from my working EFI partition on my single drive.