On 19 April 2015 at 16:54, Ted <email address hidden> wrote:
> This is not a bug, please check the following discussion:
>
> https://lists.ubuntu.com/archives/ubuntu-devel/2014-February/038095.html
>
> "...This cycle a few things were done in mdadm & dmraid packages to
> prepare for transition from dmraid to mdadm for a few formats that
> mdadm supports.
>
> At the moment it trusty, mdadm has full support to assemble Intel
> Matrix Raid and DDF fakeraid arrays, instead of dmraid. At the moment
> however, mdadm codepath is disable via a kernel cmdline options..."
>
> Explanation of how to fix it is in the thread.
>
However we ought to start using mdadm alone, preferably early in 15.10
cycle such that by 16.04 LTS it is stable.
Hello,
On 19 April 2015 at 16:54, Ted <email address hidden> wrote: /lists. ubuntu. com/archives/ ubuntu- devel/2014- February/ 038095. html
> This is not a bug, please check the following discussion:
>
> https:/
>
> "...This cycle a few things were done in mdadm & dmraid packages to
> prepare for transition from dmraid to mdadm for a few formats that
> mdadm supports.
>
> At the moment it trusty, mdadm has full support to assemble Intel
> Matrix Raid and DDF fakeraid arrays, instead of dmraid. At the moment
> however, mdadm codepath is disable via a kernel cmdline options..."
>
> Explanation of how to fix it is in the thread.
>
However we ought to start using mdadm alone, preferably early in 15.10
cycle such that by 16.04 LTS it is stable.
--
Regards,
Dimitri.