It's the easy backup raid by Asus, i don't know the real chip, i'll
look when i'm coming back home.
I found that the id read by ata and the id named in the raid table is
different.
I'll check more, i've written a small patch to force to true this
comparaison on the 4th disk, then everything works fine for detecting
this array but it ask mme for raid456 module even if this module is
loaded, i stopped there.
It's the easy backup raid by Asus, i don't know the real chip, i'll
look when i'm coming back home.
I found that the id read by ata and the id named in the raid table is
different.
I'll check more, i've written a small patch to force to true this
comparaison on the 4th disk, then everything works fine for detecting
this array but it ask mme for raid456 module even if this module is
loaded, i stopped there.
Quoting Tormod Volden <email address hidden>:
> What is your "another controller"? /bugzilla. redhat. com/bugzilla/ show_bug. cgi?id= 219058 /bugs.launchpad .net/bugs/ 103770
>
> This bug seems to be similar, although not exactly the same:
> https:/
>
> --
> dmraid 4th disk problem
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>