See also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781172#35
** Bug watch added: Debian Bug tracker #781172
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781172
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Possible cause: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=784070#49
"The problem is that with incremental array assembly, when not all
devices are present, we need some timer, and have to run the array
with whatever number of devices available as we currently have."
--
You received this
Note: "Installing mdadm package from Ubuntu 16.10 fixes the problem." is
probably incorrect. It seems that the above steps cause boot to fail
even aftern installing mdadm version 3.4.
** Bug watch added: Debian Bug tracker #784070
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070
--
You
Note that this bug report was created on another desktop Ubuntu install.
The block devices on this computer do not match the bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700921
Title:
