If you boot the liveCD and then install mdadm to access an existing software raid, the install works fine until it comes time to install GRUB to the device, and it fails to recognize the mdadm raid partition, so fails and also causes ubiquity to quit without finishing its cleanup. The issue is that the generated chroot does not have mdadm installed, even if it is existing within the livecd.
I propose that ubiquity should fail gracefully if an issue occurs at grub install, still finishing the cleanup tasks that would normally take place, and alert you that your system is not bootable, and to retry installing grub manually, or better yet, have a check in place that if someone installed mdadm into the liveCD, to install it automatically into the chroot / for compatibility sake. It would not hurt someone if it was there in general, and would solve a great problem.
If you boot the liveCD and then install mdadm to access an existing software raid, the install works fine until it comes time to install GRUB to the device, and it fails to recognize the mdadm raid partition, so fails and also causes ubiquity to quit without finishing its cleanup. The issue is that the generated chroot does not have mdadm installed, even if it is existing within the livecd.
I propose that ubiquity should fail gracefully if an issue occurs at grub install, still finishing the cleanup tasks that would normally take place, and alert you that your system is not bootable, and to retry installing grub manually, or better yet, have a check in place that if someone installed mdadm into the liveCD, to install it automatically into the chroot / for compatibility sake. It would not hurt someone if it was there in general, and would solve a great problem.
Thank you!