mdadm --update=uuid (plus replacing the uuid in /etc/mdadm/mdadm.conf) fixes the problem.
However, that still leaves people who had a perfectly working Feisty system, which happened to have this inconsistency, with a machine that cannot boot after upgrading to Gutsy. -- "No devices listed in conf file were found" due to mdadm RAID1 array UUID different from actual UUID reported by vol_id https://bugs.launchpad.net/bugs/126499 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
