MBP, Apple software RAID 1 mirror setup, startup boot volume PROBLEMS
Hi
Looking to do following setup:
* MBP 160G internal HDD ->
1) HFS+ Volume: System (want RAID 1) 100G
2) HFS+ Volume: Public (regular) 60G
* External 100G 2.5 HDD USB2 box ->
1) RAID 1 spare for System volume
My experience after working on it for about 18 hours straight is there are some seriously wack problems with OS X being able to boot from such a setup.
At first I ASR everything to USB drive, I kill the 160G volume, create only the 100G RAID volume (thought I could add more at any time and didnt know I could just shrink the original), restored from USB2, booted off USB2 to put real system disk offline.
Load Disk Utility, drag System volume around, click Enable in RAID tab and it showed up everywhere it needed to. I was even able to boot from the internal volume while it was RAID 1-d. Yippee, methinks, now I just add the Public non-RAID volume and everything is dandy.
Yeah, right.
First of all, you apparently cannot add a partition, when you already have RAID mirror setup on the first partition. What the **** is that all about? They cant figure out how to do that?
So I destroy the internal RAID, 100G System volume turns back into normal, I add the 60G Public JHFS+ partition, re-enable RAID on System 100G, everything looks normal. Yippee, methinks, now I just reboot off the RAID volume and all is good.
Yeah, right.
RAID 1 System volume simply does not show up as a bootable device. I just stare at the screen in amazement - can Apple tech really be THIS weak? I mean I have a more complicated setup running in Linux including MD, LVM2 and LUKS encryption for a few years now, and I did not even have topay out of my arse for that.
Boot off USB, disable RAID on System, remove Public partition, enable RAID on System, reboot - again we can boot off the RAID volume. I stare at the screen in amazement.
Boot off USB, disable RAID on System, put Public partition back, enable RAID on System, reboot - nope, it cannot find a startup volume.
W... T... F.
Google datacenters must be smoking of all the Googling I did to find out what the heck kind of restrictions exist on this. The information is SO scattered and incomplete and random, it has been impossible for me to deduce conclusively whether this INCREDIBLY SIMPLISTIC SCENARIO can actually exist on Apple technology. Ive gone through loads of information describing all sorts of mirror RAID scenarios, all sorts of problems with having more than one partition/volume on the RAID disk, the fact that the setup looks like it needs a separate Apple_Boot partition to boot off of, EFI problems with RAID, SmartRAID, etc, etc. But NOTHING that describes to the point what I want to do.
QUESTION: Can anyone tell me, am I supposed to be able to put my BOOTABLE "System" Volume into RAID 1 and also have ANY other partition on ONE DISK?
Trial and error on my MBP shows EFI seems to cough blood as soon as you put anything else on the disk aside from JUST the single RAID volume. Which frankly would be WEAK as **** and more like up Microsoftish crap alley.
Looking to do following setup:
* MBP 160G internal HDD ->
1) HFS+ Volume: System (want RAID 1) 100G
2) HFS+ Volume: Public (regular) 60G
* External 100G 2.5 HDD USB2 box ->
1) RAID 1 spare for System volume
My experience after working on it for about 18 hours straight is there are some seriously wack problems with OS X being able to boot from such a setup.
At first I ASR everything to USB drive, I kill the 160G volume, create only the 100G RAID volume (thought I could add more at any time and didnt know I could just shrink the original), restored from USB2, booted off USB2 to put real system disk offline.
Load Disk Utility, drag System volume around, click Enable in RAID tab and it showed up everywhere it needed to. I was even able to boot from the internal volume while it was RAID 1-d. Yippee, methinks, now I just add the Public non-RAID volume and everything is dandy.
Yeah, right.
First of all, you apparently cannot add a partition, when you already have RAID mirror setup on the first partition. What the **** is that all about? They cant figure out how to do that?
So I destroy the internal RAID, 100G System volume turns back into normal, I add the 60G Public JHFS+ partition, re-enable RAID on System 100G, everything looks normal. Yippee, methinks, now I just reboot off the RAID volume and all is good.
Yeah, right.
RAID 1 System volume simply does not show up as a bootable device. I just stare at the screen in amazement - can Apple tech really be THIS weak? I mean I have a more complicated setup running in Linux including MD, LVM2 and LUKS encryption for a few years now, and I did not even have topay out of my arse for that.
Boot off USB, disable RAID on System, remove Public partition, enable RAID on System, reboot - again we can boot off the RAID volume. I stare at the screen in amazement.
Boot off USB, disable RAID on System, put Public partition back, enable RAID on System, reboot - nope, it cannot find a startup volume.
W... T... F.
Google datacenters must be smoking of all the Googling I did to find out what the heck kind of restrictions exist on this. The information is SO scattered and incomplete and random, it has been impossible for me to deduce conclusively whether this INCREDIBLY SIMPLISTIC SCENARIO can actually exist on Apple technology. Ive gone through loads of information describing all sorts of mirror RAID scenarios, all sorts of problems with having more than one partition/volume on the RAID disk, the fact that the setup looks like it needs a separate Apple_Boot partition to boot off of, EFI problems with RAID, SmartRAID, etc, etc. But NOTHING that describes to the point what I want to do.
QUESTION: Can anyone tell me, am I supposed to be able to put my BOOTABLE "System" Volume into RAID 1 and also have ANY other partition on ONE DISK?
Trial and error on my MBP shows EFI seems to cough blood as soon as you put anything else on the disk aside from JUST the single RAID volume. Which frankly would be WEAK as **** and more like up Microsoftish crap alley.
MBP 2.4, Mac OS X (10.5.4)