ClearFoundation

Could anybody please point me in the right direction, I ma not sure where to go from here.

RAID is in a degraded state.


/dev/md0 101.9 MB /boot RAID-1 Clean

/dev/md1 463.7 GB / RAID-1 Degraded (/dev/sdb3 failed)

Hi Matthew, it appears your drive (sdb) has failed, if it has indeed failed (i.e. hardware problem) then you will need to replace it. There are threads on the forum for replacing RAID drives using the tool mdadm.

Can you post the output of:-

I have the same problem, but mine is RAID 5, this happen after I tried to test RAID by upplugging power cable on one of disk members and then plug it back in. Both were done when the system completely shutdown. Here is the output:

[root@mymail ~]# mdadm --detail /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Wed Apr 6 15:57:45 2011
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Fri Apr 8 04:30:55 2011
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : ef564f3f:c8f9b009:441bbe81:ec629752
Events : 0.120

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 0 0 2 removed
[root@mymail ~]# mdadm --detail /dev/md1
/dev/md1:
Version : 0.90
Creation Time : Wed Apr 6 15:24:54 2011
Raid Level : raid5
Array Size : 92164608 (87.90 GiB 94.38 GB)
Used Dev Size : 46082304 (43.95 GiB 47.19 GB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent

Update Time : Fri Apr 8 13:33:06 2011
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 256K

UUID : 022e2134:a9c9de92:9b0c34c5:59b6426e
Events : 0.43046

Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 0 0 2 removed
[root@mymail ~]# mdadm --detail /dev/md2
/dev/md2:
Version : 0.90
Creation Time : Wed Apr 6 15:26:27 2011
Raid Level : raid5
Array Size : 1844374016 (1758.93 GiB 1888.64 GB)
Used Dev Size : 922187008 (879.47 GiB 944.32 GB)
Raid Devices : 3
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent

Update Time : Fri Apr 8 04:31:00 2011
State : clean, degraded
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 256K

UUID : 113bc85c:f4e14fd8:fd3faa83:3bdb2744
Events : 0.168

Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
1 8 21 1 active sync /dev/sdb5
2 0 0 2 removed

Angus, it looks like you'll need to re-join your drive (sdc?) back to the arrays



Then monitor resync by looking at 'cat /proc/mdstat'

Thank you, works great

Hi Tim

Here is the output of mstat.

Hi Matthew, can you post the output of the other two (mdadm) commands I requested?

Sorry, here they are.

Ok - you have a slightly odd situation, /dev/sdb3 was labelled as failed by the webconfig in your first post, however appears to be functioning as the only partition in array md1. Have you rebooted since your original post? that would explain the drive letter changes

We can try to rejoin your other partition if your certain the drive is still OK?

Then monitor the resync with 'cat /proc/mdstat' and any I/O errors in 'dmesg'

Thanks for all your help Tim, I will try and see if I can get it to work.

On the same topic but different matter, I have installed a fresh installation on a RAID 1 configuration following the instruction on the clearos site. I have installed grub on sdb but if i remove sda the system won't boot GRUB hard disk error.

Do you perhaps know how I can make them both bootable in case of a primary disk fail.