Missing Raid after power issues...suggestions gratefully received

Hi
Faulty safety circuit in my house caused some power issues. My OMV server powered back on ok, but hung during startup with a filesystem error. Managed to access the OMV GUI but no Raid visible. Output of Raid and disk status as below. Any help would be gratefully received. Cheers

root@NASStoragee:~# cat /proc/mdstat
Personalities :
unused devices: <none>

root@NASStorage:~# blkid
/dev/sda: UUID="8a0e8e7a-f1b8-9c9d-72a9-254f2a010001" LABEL="HPNas:Data" TYPE="linux_raid_member" UUID_SUB="c50a3a94-20af-dcdd-b1b9-1b3779ed5373"
/dev/sdb: UUID="8a0e8e7a-f1b8-9c9d-72a9-254f2a010001" LABEL="HPNas:Data" TYPE="linux_raid_member" UUID_SUB="1523e887-a7fe-eacf-cd34-79405a71c4d1"
/dev/sdc: UUID="8a0e8e7a-f1b8-9c9d-72a9-254f2a010001" LABEL="HPNas:Data" TYPE="linux_raid_member" UUID_SUB="878d77a6-1d50-0354-53d6-72783f018864"
/dev/sdd1: UUID="d011d943-de32-46a3-a8f9-22ea2a4e1f46" TYPE="ext4" LABEL="ScratchDisk"
/dev/sde1: LABEL="ScratchDisk" UUID="022410e0-b183-4b5f-881c-f63e8382c413" TYPE="ext4"
/dev/sde5: UUID="bae448c1-680b-4f61-9a24-90f4e9ea56a8" TYPE="swap"

root@NASStorage:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 4294967295 2147483647+ ee GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
256 heads, 63 sectors/track, 121126 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x71ca4da8

Device Boot Start End Blocks Id System
/dev/sdb1 1 4294967295 2147483647+ ee GPT

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/sda doesn't contain a valid partition table

WARNING: GPT (GUID Partition Table) detected on '/dev/sdd'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sdd: 750.2 GB, 750156374016 bytes
256 heads, 63 sectors/track, 90845 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdd1 1 1465149167 732574583+ ee GPT

WARNING: GPT (GUID Partition Table) detected on '/dev/sde'! The util fdisk doesn't support GPT. Use GNU Parted.

Disk /dev/sde: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000eccee

Device Boot Start End Blocks Id System
/dev/sde1 * 2048 473036799 236517376 83 Linux
/dev/sde2 473038846 488396799 7678977 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sde5 473038848 488396799 7678976 82 Linux swap / Solaris

I am assuming this is the issue:

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisk identifier: 0x00000000Disk /dev/sda doesn't contain a valid partition table

If the disk is dead shouldn't the raid continue to do it's thing...? I had three disks set up in a raid 5.

Cheers

Ok...think I have at least got things running again so am putting this here as it might help someone

ran this command: mdadm --assemble --run --force /dev/md0 /dev/sd[abc]

This assembled the array. Then in omv vault I force mounted the array and my shares are back Looks like sdb has carked it. I have two drives sda/sdc listed in array with status active/degraded.

Am copying transitioning my data as I type.

Cheers