The order that mdrun starts /dev/mdx devices seems to be based on many
factors. Degraded arrays can affect the order.

Note this debian bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354705

Which has been fixed by deprecating the use of mdrun. However ubuntu
still uses mdrun (from initfs).

The new edgy boot system uses fs uuid's instead of /dev/md0 /dev/md1
etc. However currently this is not working with /dev/mdx devices.



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

-- 
boot confused after stopping array
https://launchpad.net/bugs/38438

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to