I was able to fix this problem after the failed install and avoid the re-install. Ubuntu Server 10.10
I also have the 500GB drives with a RAID1. My partitions were done as default with /dev/sda1 and /dev/sdb1 as the root partitions and /dev/sda5 and /dev/sdb5 as the swap partitions. I shrunk the swap partitions (/dev/sda5 and /dev/sdb5) by 2 "Units" using fdisk and then zeroed the raid superblocks. The steps I took. Load up the rescue disk and mount the installer root. In my case it was seeing md5 and md5p1 as my raid devices. 1. run "mdadm --stop /dev/md5" 2. fdisk /dev/sda 3. delete partition 5 (/dev/sd5) 4. create a new logical partition 5 5. use the default start 6. used End - 2 (in my case 60802 - 2 = 60800) as the End 7. change type to "fd" for "Linux raid autodetect" 8-14. reapeat steps 2 - 7 with /dev/sdb 15. run mdadm --zero-superblock /dev/sda 16. run mdadm --zero-superblock /dev/sdb 17. reboot After getting this to work, and realizing that a block is about 8MB, I realize this solution loses out on 16MB on my disks. I'm sure a larger end value might work as well but who cares. It boots now. -- partman sometimes creates partitions such that there is ambiguity between whether the superblock is on the disk device or the partition device https://bugs.launchpad.net/bugs/569900 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
