Raid degraded after reboot, may be this time I won't lost al

Hi, I build a new server since I lost everything a month ago.
Today, another shut-off due to power-supply.

The server restart with a problem: this time I have my filesystem clean and mounted, but my raid is clean degraded.
I got a raid 5, and I have only 2 disks listed under the web-interface.
I tryed to click on "repair" but I can't see the missing list in the opening windows (I see it under the disks tab)

Since i had a so bad experience a month ago, I prefer asking before doing stuping tests.
Help would be much appreciated.

Once I could fix-it, I'll gladly take advice on how to secure this thing, and how I could have a reliable backup of my files.
I know a raid5 is not the optimal way of doing it, I was thinking it was secure enough and this cause me the lost of3To of data. I search for a way to secure 3 to 6 To of data in an easy and not too expensive way.

Sorry for my english skills.

PS: i turn off the server just in case.

My disk dev/sdb is listed on my "disk drives" tab, but not under my raid tab.

When I tryed to repair, the windows don't show me tha sdb drive, so I can't add it.

md127:activ red5 sdc[1 sdd[2
5860530176 blocs super 1.2 level5, ...

I assume this is what you need?

Thank you

Version : 1.2
Creation Time : Fri May 24 19:00:23 2013
Raid Level : raid5
Array Size : 5860530176 (5589.04 GiB 6001.18 GB)
Used Dev Size : 2930265088 (2794.52 GiB 3000.59 GB)
Raid Devices : 3
Total Devices : 2
Persistence : Superblock is persistent

Update Time : Mon Jun 24 08:58:52 2013
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Name : openmediavault:serveur (local to host openmediavault)
UUID : b88241e7:d2d61ff9:2ec5bfbc:22f4b7de
Events : 440764

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 32 1 active sync /dev/sdc
2 8 48 2 active sync /dev/sdd

Here is the detail report.

My samba shares are still working, that's the good news.

root@openmediavault:~# fdisk -l

Disk /dev/sda: 80.0 GB, 80025280000 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e1e99

Device Boot Start End Blocks Id System
/dev/sda1 * 1 9330 74935296 83 Linux
/dev/sda2 9330 9730 3211265 5 Extended
/dev/sda5 9330 9730 3211264 82 Linux swap / Solaris

Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 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

Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x44864486

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

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes
255 heads, 63 sectors/track, 364801 cylinders
Units = cylinders of 16065 * 512 = 8225280 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/md127: 6001.2 GB, 6001182900224 bytes
2 heads, 4 sectors/track, 1465132544 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disk identifier: 0x00000000

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

Thanks, I launch a recovery.

Just in case...if anythime i have power trouble my server is near death, may be I have to change something...

The repair failed at 15%:
disk failure continuing with 2 disks.

in cat /proc/mdstat I have my 3 disks but sdb[3](f)

I don't know what an UPS is, I assume it's what we call "onduleur": a battery that keep the computer running whete the power shut down.

Something I have to do to check it?

I'll try to do the repair another time, but I think I have to first take the sdb disk out of the raid.
I format another time the dev/sdb (quick format) using the web gui, it said that the GPT is destroyed and I can use fdisk to create partitions (I didn't do it since I don't know how to do it), but since the disk is already add to the raid, I can't launch the repair from the GUI.

Here is my details tab:

Version : 1.2
Creation Time : Fri May 24 19:00:23 2013
Raid Level : raid5
Array Size : 5860530176 (5589.04 GiB 6001.18 GB)
Used Dev Size : 2930265088 (2794.52 GiB 3000.59 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Tue Jun 25 10:45:27 2013
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 1
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 512K

Name : openmediavault:serveur (local to host openmediavault)
UUID : b88241e7:d2d61ff9:2ec5bfbc:22f4b7de
Events : 445368

Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 32 1 active sync /dev/sdc
2 8 48 2 active sync /dev/sdd

3 8 16 - faulty spare /dev/sdb

Zitat von "davidh2k"

Yep, you were right. An Uninterruptible Power Supply/Source, short UPS.

Greetings
David

Thanks

Thanks, and then I add it in the web interface to the raid, or I should use some sort of command line?

Is it normal that the zero superblock command took a very long time?

I tryed to rebuild another time, I have the "event" that grows up:

Version : 1.2
Creation Time : Fri May 24 19:00:23 2013
Raid Level : raid5
Array Size : 5860530176 (5589.04 GiB 6001.18 GB)
Used Dev Size : 2930265088 (2794.52 GiB 3000.59 GB)
Raid Devices : 3
Total Devices : 3
Persistence : Superblock is persistent

Update Time : Tue Jun 25 17:45:28 2013
State : clean, degraded, recovering
Active Devices : 2
Working Devices : 3
Failed Devices : 0
Spare Devices : 1

Layout : left-symmetric
Chunk Size : 512K

Rebuild Status : 0% complete

Name : openmediavault:serveur (local to host openmediavault)
UUID : b88241e7:d2d61ff9:2ec5bfbc:22f4b7de
Events : 455792

Number Major Minor RaidDevice State
3 8 16 0 spare rebuilding /dev/sdb
1 8 32 1 active sync /dev/sdc
2 8 48 2 active sync /dev/sdd

Then a few minutes later the recovery ended, and my sdb is listed as faulty spare.

I assume an error message should be somewhere but I don't know where. May be I do something wrong during the rebuild? (accessing some files,etc)

On the server I got thoses messages:
End request disk sdb failure sector8
Ata3.0 exception Emask 0x0 .... frozen
failed command: read dma
cmd c8/00:08:...
status: DRDY

Thanks for answer.

You know any command to test it? I don't want to sent it to WD back if it's still working.