raid10 support should be added to installer

There's a separate bug for the general task of adding RAID support to Ubiquity, but RAID10 would also need to be added to d-i (mdcfg).

Thanks! In and of itself, this patch looks fine, though it'll need a feature freeze exception.

Shouldn't there be some kind of control over spare devices here? http://cgi.cse.unsw.edu.au/~neilb/01093607424 says that Linux raid10 supports that, and since we're already doing that for RAID1 it seems to make sense to support it here too.

FFe granted, with or without the further changes Colin suggests regarding spare device settings.

Is there any hope of seeing translations of the newly-added debconf question? Perhaps submitting the changes to Debian and using the d-i translation infrastructure there would be most effective, but I'm not sure how effective that would be after all while Debian is in the lenny freeze?

Will the patch work with grub too? With hardy, grub didnt support booting off a raid10 partition. I thought thats why it wasn't included in the installer, but I would love to see this make it in.

GRUB still isn't able to boot from RAID10 partitions, however this needs avoiding for /boot or / (if there is no /boot). Thus, the installed should certainly allow RAID10 partitions to be created for other mount points.

Arguably, linux's RAID10 format is one of the two most all-round performant formats (with RAID5), and we should develop, integrate and test this patch for Jaunty Jackalope.

I'd be suprised if GRUB is ever able to boot from RAID10. That type of heavy block swapping logic would be very out of place in GRUB... and you'd not be able to get the boot sector working right anyways. The /boot partition will need to be a mirror or plain partition. I don't see this changing.

The installer should just make sure that /boot is something compatible. RAID1 or plain partition, with compatible file system.

Informative comments, thank you. Along with adding RAID10 support, we should also show a warning that stops the user from the /boot mount to be on a raid10 partition, or the root mount being on the raid10 partition if there is no /boot mount selected. Currently, the installer will continue, and the user will get a critical failure at the boot loader install portion of the installer, that doesn't describe why grub failed.

Please let's get this into the next LTS release.