Raid 5 Missing after reboot

Hi,

I have just rebooted OMV this morning and it seems my Raid5 is missing. I did checked the forum and found other similar comments but none seem quite like the output I get when running cat /proc/mdstat
The ouput of the following is below. Any advise on how to get the Raid back would be apprciated, and no before you ask I dont have a back up of the Data :(.

root@HP-NAS:/dev/md# blkid
/dev/sda1: UUID="88ba4d44-0f76-4e47-b015-5c3bc8c3c457" TYPE="ext4"
/dev/sda5: UUID="55c1f1c2-e1b9-4572-89a1-2d1119896259" TYPE="swap"
/dev/sdb: UUID="d682a910-82ff-2fa8-f722-d02adc5b4052" UUID_SUB="21a320d8-3f20-2247-5f2b-3d7a8035c93f" LABEL="HP-NAS:Raid5" TYPE="linux_raid_member"
/dev/sdc: UUID="d682a910-82ff-2fa8-f722-d02adc5b4052" UUID_SUB="5c4a4aa9-efe9-0b06-54a7-ab973fe63a82" LABEL="HP-NAS:Raid5" TYPE="linux_raid_member"
/dev/sde1: LABEL="Backup" UUID="c5f3b2b2-0d98-474e-bd30-c49efedb131c" TYPE="xfs"
/dev/sdg1: LABEL="Village" UUID="428b9025-2276-4c31-b0ac-3496024fe2a9" TYPE="ext4"
/dev/sdf1: LABEL="BlueIris" UUID="279a7d31-282b-407e-a8ef-2177d2dc42a2" TYPE="ext4"
/dev/sdd: UUID="d682a910-82ff-2fa8-f722-d02adc5b4052" UUID_SUB="48623d7b-b623-0650-f4d6-af69c6005076" LABEL="HP-NAS:Raid5" TYPE="linux_raid_member"

root@HP-NAS:/dev/md# cat /proc/mdstat
Personalities :
unused devices: <none>

root@HP-NAS:/dev/md# fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 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: 0x0003d511

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 480862207 240430080 83 Linux
/dev/sda2 480864254 488396799 3766273 5 Extended
/dev/sda5 480864256 488396799 3766272 82 Linux swap / Solaris

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 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: 0x00000000

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

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 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: 0x00000000

Disk /dev/sdb 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: 3000.6 GB, 3000592982016 bytes
256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 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: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdd1 1 4294967295 2147483647+ ee GPT
Partition 1 does not start on physical sector boundary.

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

Disk /dev/sde: 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/sde1 1 1953525167 976762583+ ee GPT

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

Disk /dev/sdf: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders, total 3907029168 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: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdf1 1 3907029167 1953514583+ ee GPT
Partition 1 does not start on physical sector boundary.

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

Disk /dev/sdg: 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/sdg1 1 1953525167 976762583+ ee GPT

Hi. All sorted.

What I did not say is that prior to a reboot I had indeed edited the /etc/md/mdadm.conf file to chnage the spare=1 to spare=0. Unfortunatly I have downloaded and uploaded the file and thus changed it to DOS mod.

I found the solution on this forum on intslling dos2unix and converting the mdadm.conf file back to unix format.

I then ran
update-initramfs -u
mdadm --assemble --scan --verbose --auto=yes --symlink=no

This has retuned the RAID and all data. I now have 2 extra 3tb drives on order and will be converting the raid 5 to dual raid 1's so that I can back one raid up to the other.

Thanks and sorry for asking for help. As usual 2-3 hours of searching these forums and google found all the info I needed.

I guess like most I paniced when I lost the raid

ryecoaaron,

Will do and thanks for the tip. I had installed Vi but thats pretty dam akward to use.

All in all I have learnt a lot over the last couple of days.

First I had a drive that is showing sector errors so trying to be cleaver I removed it from the raid and wrote all "0"'s to it then all "1"'s in an atempt to get it to recover the bad sectors or at least mask it. After that I recovered the raid 5 and all seemed ok until I got the monit email stating that the raid had a spare. This lead to the editing of the mdadm.conf file and the subsequent loss of the raid after using wordpad lol.

Now its fixed it has taught me that I was wasting my time as the data is far to important to me to be faffing arround, hence two new 3tb drives should be delivered by Friday and I will be moving all the data from the current setup of 1 x raid 5 with 3 disks to 2 x raid 1. I will then run a daily backup between the two of them.

I will also chuck the drive thats on its way out (3tb drive with sector errors) in the bin as this is what I should have done from the start.

Hey ho you live and learn, thankfully I hope this time its not to late to recover

yep smartctl repoted
"SMART error (OfflineUncorrectableSector) detected on host: HP-NAS"
"The following warning/error was logged by the smartd daemon:

Device: /dev/disk/by-id/scsi-SATA_WDC_WD30EFRX-68_WD-xxxxxxxx [SAT], 26 Offline uncorrectable sectors"

The drive is still under warranty so I might try and get it replaced as well.