Okay, so I finally managed to get Lucid installed on a RAID1 root disk, but the procedure isn't pretty...
* I booted a Desktop livecd
* Popped open a terminal
* partitioned both of my disks using fdisk, sda1 and sdb1, both 0xfd (linux raid)
* installed mdadm in the live cd environment
* mdadm --create /dev/md0 -n 2 -l 1 /dev/sda1 /dev/sdb1
* mkfs.ext4 /dev/md0
* then installed Ubuntu using the wizard
* after the install completed, drop to a shell and chroot to /target, and apt-get install mdadm
Note that the mkfs.ext4 step seems to be the critical one... If I don't do that, and I fire up the installer, it goes and tries to partition /dev/md0, yielding a /dev/md0p1 which is unusable. This seems to be the same thing the server installer did too.
Now, I'm up and running Ubuntu Desktop with / on a RAID1. Not Server. So this still isn't ideal. But this work around hopefully shows a bit more about where the bug is.
Okay, so I finally managed to get Lucid installed on a RAID1 root disk, but the procedure isn't pretty...
* I booted a Desktop livecd
* Popped open a terminal
* partitioned both of my disks using fdisk, sda1 and sdb1, both 0xfd (linux raid)
* installed mdadm in the live cd environment
* mdadm --create /dev/md0 -n 2 -l 1 /dev/sda1 /dev/sdb1
* mkfs.ext4 /dev/md0
* then installed Ubuntu using the wizard
* after the install completed, drop to a shell and chroot to /target, and apt-get install mdadm
Note that the mkfs.ext4 step seems to be the critical one... If I don't do that, and I fire up the installer, it goes and tries to partition /dev/md0, yielding a /dev/md0p1 which is unusable. This seems to be the same thing the server installer did too.
Now, I'm up and running Ubuntu Desktop with / on a RAID1. Not Server. So this still isn't ideal. But this work around hopefully shows a bit more about where the bug is.