I forgot to mention that the modules should be loaded before you run the update-initramfs command.
This is the result of my examine command:
/dev/sda:
MBR Magic : aa55
Partition[0] : 497664 sectors at 2048 (type 83)
Partition[1] : 62029826 sectors at 501758 (type 05)
/dev/sda2:
MBR Magic : aa55
Partition[0] : 62029824 sectors at 2 (type 83)
/dev/sdb:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : cfb1a241:b1f4a374:e84097c2:3f55fa82
Name : openmediavault:mdomv01 (local to host openmediavault)
Creation Time : Fri Apr 24 00:37:06 2015
Raid Level : raid10
Raid Devices : 4
Avail Dev Size : 1250001584 (596.05 GiB 640.00 GB)
Array Size : 1250000896 (1192.09 GiB 1280.00 GB)
Used Dev Size : 1250000896 (596.05 GiB 640.00 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 5c3de8f7:6be5630e:3c300ddc:867f3d67
Update Time : Fri Apr 24 14:03:23 2015
Checksum : 5eaf156e - correct
Events : 19
Layout : near=2
Chunk Size : 512K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing)
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : cfb1a241:b1f4a374:e84097c2:3f55fa82
Name : openmediavault:mdomv01 (local to host openmediavault)
Creation Time : Fri Apr 24 00:37:06 2015
Raid Level : raid10
Raid Devices : 4
Avail Dev Size : 1250001584 (596.05 GiB 640.00 GB)
Array Size : 1250000896 (1192.09 GiB 1280.00 GB)
Used Dev Size : 1250000896 (596.05 GiB 640.00 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 05e1ff5b:fcf4d640:a970417d:e8fe62f7
Update Time : Fri Apr 24 14:03:23 2015
Checksum : 26938878 - correct
Events : 19
Layout : near=2
Chunk Size : 512K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing)
/dev/sdd:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : cfb1a241:b1f4a374:e84097c2:3f55fa82
Name : openmediavault:mdomv01 (local to host openmediavault)
Creation Time : Fri Apr 24 00:37:06 2015
Raid Level : raid10
Raid Devices : 4
Avail Dev Size : 1250001584 (596.05 GiB 640.00 GB)
Array Size : 1250000896 (1192.09 GiB 1280.00 GB)
Used Dev Size : 1250000896 (596.05 GiB 640.00 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : d7af56db:13b36800:b4306fc6:ed074843
Update Time : Fri Apr 24 14:03:23 2015
Checksum : fa8ede71 - correct
Events : 19
Layout : near=2
Chunk Size : 512K
Device Role : Active device 2
Array State : AAAA ('A' == active, '.' == missing)
/dev/sde:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : cfb1a241:b1f4a374:e84097c2:3f55fa82
Name : openmediavault:mdomv01 (local to host openmediavault)
Creation Time : Fri Apr 24 00:37:06 2015
Raid Level : raid10
Raid Devices : 4
Avail Dev Size : 1250001584 (596.05 GiB 640.00 GB)
Array Size : 1250000896 (1192.09 GiB 1280.00 GB)
Used Dev Size : 1250000896 (596.05 GiB 640.00 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
State : clean
Device UUID : dd19ae9b:51b2b129:c9de9d70:2fee926a
Update Time : Fri Apr 24 14:03:23 2015
Checksum : b5a8dc0d - correct
Events : 19
Layout : near=2
Chunk Size : 512K
Device Role : Active device 3
Array State : AAAA ('A' == active, '.' == missing)
and for my events check:
mdadm --examine /dev/sd[abcde]* | egrep -i 'Event|/dev/sd'
mdadm: No md superblock detected on /dev/sda1.
mdadm: No md superblock detected on /dev/sda5.
/dev/sda:
/dev/sda2:
/dev/sdb:
Events : 19
/dev/sdc:
Events : 19
/dev/sdd:
Events : 19
/dev/sde:
Events : 19
Also as you may have noticed, your drives don't have any RAID metadata so will probably not be combined in an array since there isn't any information on how to reassemble them. Had there been metadata then the event would have shown you if the difference between data writes had the integrity of the array been altered.
Correct me if I'm wrong, but is /dev/sde your new boot disk? If from the RAID failure you didn't now shuffle the physical order of the drive then you should turn off or remove the members of the RAID array and make sure that your boot/OS disk is /dev/sda; then make the drives available. If the /dev/sda allocation doesn't persists then you should make it persistent via UDEV.
I have to go out but will be back later in the day.