On Thu, Jan 14, 2016 at 6:02 PM, Ryan Harper <email address hidden> wrote:
> If you reset like I suggested and then modprobe raid0, can you re-run the
> create command successfully?
No, as I said, the image that is running during deployment has no RAID
modules in /lib/modules.
> And finally, THAT seems to be the root cause. There are no software RAID
> modules that I can find on the ephemeral:
>
> root@supermicro:/lib/modules/3.19.0-43-generic/kernel/drivers/md# ls
> bcache dm-crypt.ko
>
The ONLY contents of the md directory is for bcache and the dm-crypt
module. The raidX.ko modules are completely missing. So I think this
is an image problem, RAID is probably OK.
On Thu, Jan 14, 2016 at 6:02 PM, Ryan Harper <email address hidden> wrote:
> If you reset like I suggested and then modprobe raid0, can you re-run the
> create command successfully?
No, as I said, the image that is running during deployment has no RAID
modules in /lib/modules.
> And finally, THAT seems to be the root cause. There are no software RAID :/lib/modules/ 3.19.0- 43-generic/ kernel/ drivers/ md# ls
> modules that I can find on the ephemeral:
>
> root@supermicro
> bcache dm-crypt.ko
>
The ONLY contents of the md directory is for bcache and the dm-crypt
module. The raidX.ko modules are completely missing. So I think this
is an image problem, RAID is probably OK.