I ran into the same issues as you, and similarly was able to successfully create my RAID arrays using another Linux distro (Gentoo). I struggled with this for hours, and finally came to the realization that mdadm likes to auto assemble RAID arrays, whether during booting, or as part of the partitioning process during installation. Since my drives had been part of a past array (as entire disks) and part of several RAID setup attempts (using partitions) they were littered with data that mdadm used to create arrays that I did not want.
So during OS installation, the previous use of the entire disks in a RAID array caused the RAID portion of the partitioner to create the unwanted whole-disk array, and throw up the error that no "Linux RAID autodetect" partitions were available. Similarly, during booting, the whole-disk array, which was a hold over of the previous use of the drives, took over the whole disk and thus my boot partition (in my case not part of the RAID), could not be found. That is why reboots failed. I ended up booting the liveCD, installing mdadm, and using mdadm --zero- superblock on my physical disk devices /dev/sda and /dev/sdb, and on each of the drives' partitions that previously had the "mdraid" partition type set. This removes the information mdadm uses to auto assemble RAID arrays. >From what I have read, but not tried myself, is that the mdadm --stop command will take partitions out of a raid array so that the partitions can be reused as other partition types (or in another RAID array). --Eric S. -- raid config fails with debian-installer/mdadm https://bugs.launchpad.net/bugs/182376 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
