[Solved] RAID booting problem

[RSN]

I installed a Retail 10.5.5 DVD into a RAID drive per instructions here. http://forum.insanelymac.com/index.php?showtopic=76404 (Using Chameleon latest version)

 

Good guide and everything seemed to go fine up to booting time. I have an INTEL mobo (DG35EC) and the RAID drive and their internal drives didnt even show up as bootable (apparently known issue). That is, no boot.

 

So I tried setting a boot_uuid in a another Mac installation I have and boot indirectly from that drive. Put the RAID uuid in the com.apple.boot.plist in that bootable Mac and rebooted. NOTHING. Back to the booting Mac. This went on for 2 weeks. :censored2: :censored2:

 

Da solution:

 

The idea behind a uuid is that it is disk position independent. You may add a new drive or remove one and has no effect because the selection is via a Reference Number not a hardware position (in the BIOS disk order). Well, maybe somebody can help with this problem, but the only solution was to boot with the rd=diskX option. First you can do it manually from the bootable Mac, that is, F8 during booting, and in options, rd=diskX (X being the RAID disk number as seen in Disk Utility->Info panel). It BOOTED.

 

Now to make the RAID drive INDEPENDENTLY bootable (not using another Mac) I had to fdisk -e /dev/rdiskX one of the many RAID drives. Now the disk is bootable and seen by the Mobo as such. Again, you can do a F8 and rd=diskX and boot or add the rd=diskX in the com.apple.boot.plist of the RAID volume. Boots now independently and doesnt need another Mac.

 

If you add or remove a disk unit, the diskX WILL change and hence will not boot. Need to find out what is the new diskX. Just F8 and rd=diskY until you can boot.

 

Why the boot_uuid booting parameter doesnt work I have now idea. Funny things happened when booting from the Raid Volume without the rd=diskX option and using the boot_uuid, but mostly PANIC.

 

I hope somebody can fix this problem so that a RAID Volume is bootable with the boot_uuid.

 

Hope it helps.

[ojox]

I've been racking my brain (banging head on desk) for over 4 days now. I have the same motherboard and am trying to accomplish bootable raid 0. I've followed every tutorial that google could find. I will experiment with your technique. Have you found a better solution for a bootable raid with Retail Leopard on this MB (DG35EC)?

 

Thanks

 

I installed a Retail 10.5.5 DVD into a RAID drive per instructions here. http://forum.insanelymac.com/index.php?showtopic=76404 (Using Chameleon latest version)

 

Good guide and everything seemed to go fine up to booting time. I have an INTEL mobo (DG35EC) and the RAID drive and their internal drives didnt even show up as bootable (apparently known issue). That is, no boot.

 

So I tried setting a boot_uuid in a another Mac installation I have and boot indirectly from that drive. Put the RAID uuid in the com.apple.boot.plist in that bootable Mac and rebooted. NOTHING. Back to the booting Mac. This went on for 2 weeks. :censored2:

 

Da solution:

 

The idea behind a uuid is that it is disk position independent. You may add a new drive or remove one and has no effect because the selection is via a Reference Number not a hardware position (in the BIOS disk order). Well, maybe somebody can help with this problem, but the only solution was to boot with the rd=diskX option. First you can do it manually from the bootable Mac, that is, F8 during booting, and in options, rd=diskX (X being the RAID disk number as seen in Disk Utility->Info panel). It BOOTED.

 

Now to make the RAID drive INDEPENDENTLY bootable (not using another Mac) I had to fdisk -e /dev/rdiskX one of the many RAID drives. Now the disk is bootable and seen by the Mobo as such. Again, you can do a F8 and rd=diskX and boot or add the rd=diskX in the com.apple.boot.plist of the RAID volume. Boots now independently and doesnt need another Mac.

 

If you add or remove a disk unit, the diskX WILL change and hence will not boot. Need to find out what is the new diskX. Just F8 and rd=diskY until you can boot.

 

Why the boot_uuid booting parameter doesnt work I have now idea. Funny things happened when booting from the Raid Volume without the rd=diskX option and using the boot_uuid, but mostly PANIC.

 

I hope somebody can fix this problem so that a RAID Volume is bootable with the boot_uuid.

 

Hope it helps.

[ojox]

After lots of experiments, rd=diskX is the only solution that works for me, too. I never did try updating the BIOS on the DG35EC. Which BIOS are you currently running?

 

Thanks for the tip!

 

 

I installed a Retail 10.5.5 DVD into a RAID drive per instructions here. http://forum.insanelymac.com/index.php?showtopic=76404 (Using Chameleon latest version)

 

Good guide and everything seemed to go fine up to booting time. I have an INTEL mobo (DG35EC) and the RAID drive and their internal drives didnt even show up as bootable (apparently known issue). That is, no boot.

 

So I tried setting a boot_uuid in a another Mac installation I have and boot indirectly from that drive. Put the RAID uuid in the com.apple.boot.plist in that bootable Mac and rebooted. NOTHING. Back to the booting Mac. This went on for 2 weeks. :censored2: :censored2:

 

Da solution:

 

The idea behind a uuid is that it is disk position independent. You may add a new drive or remove one and has no effect because the selection is via a Reference Number not a hardware position (in the BIOS disk order). Well, maybe somebody can help with this problem, but the only solution was to boot with the rd=diskX option. First you can do it manually from the bootable Mac, that is, F8 during booting, and in options, rd=diskX (X being the RAID disk number as seen in Disk Utility->Info panel). It BOOTED.

 

Now to make the RAID drive INDEPENDENTLY bootable (not using another Mac) I had to fdisk -e /dev/rdiskX one of the many RAID drives. Now the disk is bootable and seen by the Mobo as such. Again, you can do a F8 and rd=diskX and boot or add the rd=diskX in the com.apple.boot.plist of the RAID volume. Boots now independently and doesnt need another Mac.

 

If you add or remove a disk unit, the diskX WILL change and hence will not boot. Need to find out what is the new diskX. Just F8 and rd=diskY until you can boot.

 

Why the boot_uuid booting parameter doesnt work I have now idea. Funny things happened when booting from the Raid Volume without the rd=diskX option and using the boot_uuid, but mostly PANIC.

 

I hope somebody can fix this problem so that a RAID Volume is bootable with the boot_uuid.

 

Hope it helps.