*** This bug is a duplicate of bug 74346 *** I see in the other bug that the UUID is mis-extracted. But I do have a couple of systems here that have a wrong UUID (i.e. it looks like a 128-bit UUID but it isn't what the RAID's UUID). That's why I think it is another bug at all.
The question becomes: when is the file /etc/mdadm/mdadm.conf updated? I don't see it is anywhere in use in dapper (some of my dapper systems even don't have this file), so perhaps they will also get the same problem when I upgrade them? -- sane behavior for wrong /etc/mdadm/mdadm.conf https://launchpad.net/bugs/73710 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
