@whoop, will you please do the following:
1) copy your mdadm.conf somewhere safe
2) run /usr/share/mdadm/mkconf and see if the definition of md0 is in place. If 
so please use "generate" with mkconf to generate a new mdadm.conf. 

While updating initramfs, the mdadm's initramfs hook expects that the
mdadm.conf has *uuid's* instead of /dev/<node> kind of names. As you can
see this is a warning which asks you to verify the array definition,
just in case its not present. This is just to prevent the case  that
your array cannot be auto assembled (which at present it cant be with
the current mdadm-2.6.7).

Meanwhile, I shall also look at what can be done about devices instead
of uuids. Thanks a lot for filing this bug!

** Changed in: mdadm (Ubuntu)
       Status: New => Confirmed

** Changed in: mdadm (Ubuntu)
     Assignee: (unassigned) => Surbhi Palande (csurbhi)

-- 
mdadm update is scaring me: "YOUR SYSTEM IS NOW UNBOOTABLE!"
https://bugs.launchpad.net/bugs/652327
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to