I'm running OMV 2.0.15 on a raspberry pi with 3 harddisks in 4-bay sata harddisk-to-usb box. (probox with sata usb hub only)
The harddisks are visible as /dev/sda - c
The issue is now that obviously at system start up the raspberry (1GB version) is faster than the harddisks are starting up and getting visible as devices, so md0 will not get started at boot time.
As this fails I'm doing a mdadm --assemble md0 to get the raid up and running (only after all 3 devices are visible). Now because of that startup of md0 failed at boot time, the array will not be created as md0, but md127 on top of everything...
So my questions are:
- What is the official way for the raspberry image of omv to get usb drives started within a raid? Producing an image for raspberry a connection of an USB storage device was probably not so unexpected.
- Do I really need to run a bash-script after start checking if all devices are visible and the reassmble the raid or is there any other consideration of that part of OMV already?
What I specifically don't like about that, is that configuration is partly in the web-gui, partly in bash script to get the raid configuration alive again, after system reboot...
Any thoughts about this?