[RESOLVED] Degraded RAID5

Guys I got the following emails from my OMV box:

Zitat

A DegradedArray event had been detected on md device /dev/md0.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sda[0] sdb[4] sdd[3] sdf[2](F) sdc[1]
3907041280 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UU_UU]

unused devices: <none>

Alles anzeigen

Zitat

This is an automatically generated mail message from mdadm

A Fail event had been detected on md device /dev/md0.

It could be related to component device /dev/sdf.

P.S. The /proc/mdstat file currently contains the following:

Personalities : [raid6] [raid5] [raid4]
md0 : active raid5 sda[0] sdb[4] sdd[3] sdf[2](F) sdc[1]
3907041280 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UU_UU]
[>....................] check = 0.0% (4/976760320) finish=1017458.6min speed=4K/sec

unused devices: <none>

Alles anzeigen

I have a RAID5 with 5 disks. In the UI, the state is "clean, degraded". This means a drive is bad? right?

In the "Physical Disks" area, OMV is showing serial numbers for all disks, except one (/dev/sdf). Could that be the drive with the problem?

Anything else I can do to figure out what the problem is? One more thing, once the drive is identify, what are the steps to replace it in OMV?

EDIT: I am not using hardware raid, just OMV (software) raid. From reading carefully about it does seem the problem is /dev/sdf. What are the steps to follow when I get the replacement drive?

EDIT: I rebooted OMV, and now /dev/sdf is not shown anywhere in "Physical Disks". RAID5 is "clean,degraded"

Here is the mdadm output:

root@openmediavault:~# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Sat Jun 23 08:57:58 2012
     Raid Level : raid5
     Array Size : 3907041280 (3726.05 GiB 4000.81 GB)
  Used Dev Size : 976760320 (931.51 GiB 1000.20 GB)
   Raid Devices : 5
  Total Devices : 4
    Persistence : Superblock is persistent


    Update Time : Sun Aug  5 10:53:53 2012
          State : clean, degraded
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0


         Layout : left-symmetric
     Chunk Size : 512K


           Name : openmediavault:DATA  (local to host openmediavault)
           UUID : f360549e:3b1df2cd:8495cc03:e5a0267c
         Events : 202


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

Zitat von "ryecoaaron"

You are definitely missing a drive according to mdadm. I am guessing /dev/sdf was the fifth drive and it failed??

Right so do I just connect the new drive where the failed one was and start the system? Was wondering if I had to do any admin tasks to have the bad drive replaced

Zitat von "bigcat"

Right so do I just connect the new drive where the failed one was and start the system? Was wondering if I had to do any admin tasks to have the bad drive replaced

Well, bought a new drive, put it in, it shows up in the "physical disks" now as /dev/sdf, however RAID5 still shows degraded with 4 disks only, doesn't show /dev/sdf. Looks like something has to be done to add the new drive (replace old one) and rebuild the array. Appreciate any help.

Zitat von "bigcat"

Well, bought a new drive, put it in, it shows up in the "physical disks" now as /dev/sdf, however RAID5 still shows degraded with 4 disks only, doesn't show /dev/sdf. Looks like something has to be done to add the new drive (replace old one) and rebuild the array. Appreciate any help.

I ran the following from command line and now shows "clean,degraded,recovering()"

mdadm --add /dev/md0 /dev/sdf

root@openmediavault:~# cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] 
md0 : active raid5 sdf[5] sda[0] sdb[4] sdd[3] sdc[1]
      3907041280 blocks super 1.2 level 5, 512k chunk, algorithm 2 [5/4] [UU_UU]
      [>....................]  recovery =  0.0% (386432/976760320) finish=210.5min speed=77286K/sec

unused devices: <none>

The information here http://bugtracker.openmediavau…t_bug_page.php?bug_id=201 was useful.

I am not sure that's what I wanted to do, mdadm shows now as rebuilding a "spare", does that sound right?

root@openmediavault:~# mdadm --detail /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Sat Jun 23 08:57:58 2012
     Raid Level : raid5
     Array Size : 3907041280 (3726.05 GiB 4000.81 GB)
  Used Dev Size : 976760320 (931.51 GiB 1000.20 GB)
   Raid Devices : 5
  Total Devices : 5
    Persistence : Superblock is persistent


    Update Time : Sun Aug  5 17:30:17 2012
          State : clean, degraded, recovering
 Active Devices : 4
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 1


         Layout : left-symmetric
     Chunk Size : 512K


 Rebuild Status : 3% complete


           Name : openmediavault:DATA  (local to host openmediavault)
           UUID : f360549e:3b1df2cd:8495cc03:e5a0267c
         Events : 480


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

Zitat von "bigcat"

I am not sure that's what I wanted to do, mdadm shows now as rebuilding a "spare", does that sound right?

never mind, recovery is done and it's all good now.