Koozali.org: home of the SME Server

RAID ALARM!???

micke23

RAID ALARM!???
« on: March 30, 2005, 09:49:02 PM »
Hi!

I got this in my root-mailbox:
ALARM! RAID configuration problem

Current configuration is:

Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdb1[1] hda1[0] 264960 blocks [2/2] [UU] resync=DELAYED
md0 : active raid1 hdb5[1] hda5[0] 15936 blocks [2/2] [UU] resync=DELAYED
md1 : active raid1 hdb6[1] hda6[0] 32740352 blocks [2/2] [UU] resync=6% finish=402.8min
unused devices: <none>

Last known good configuration was:

Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdb1[1] hda1[0] 264960 blocks [2/2] [UU] resync=DELAYED
md0 : active raid1 hdb5[1] hda5[0] 15936 blocks [2/2] [UU]
md1 : active raid1 hdb6[1] hda6[0] 32740352 blocks [2/2] [UU] resync=4% finish=470.8min
unused devices: <none>


What is this???

Offline MSmith

  • *
  • 675
  • +0/-0
Relevant links
« Reply #1 on: March 30, 2005, 10:36:58 PM »
Found in this thread:

http://forums.contribs.org/index.php?topic=26679.msg109062#msg109062

Your machine may or may not have a real problem, but the RAID array has fallen out of sync for whatever reason (unexpected poweroff, perhaps?) and is now resynchronizing as evidenced by the "resync" line.
...

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: RAID ALARM!???
« Reply #2 on: March 31, 2005, 05:14:05 AM »
Quote from: "micke23"

I got this in my root-mailbox:
ALARM! RAID configuration problem


The RAID monitor package isn't clever enough in determining whether your raid pair is functioning. The "last normal" and current reports are equivalent (and both OK) - they shouldn't be expected to be exactly indentical.

You might file a bug report with the contrib author.

Offline raem

  • *
  • 3,972
  • +4/-0
RAID ALARM!???
« Reply #3 on: March 31, 2005, 11:25:07 AM »
The array has got out of sync for some reason, power down or whatever, and the first entry (6% resync) is showing you that both drives are OK but are busy resyncing.


The last step you do when you initially instigate the raidmonitor setup, is to initialse the raidmonitor so it records the good known RAID config ie
/usr/local/bin/raidmonitor -iv

I would say that you ran this command initially, BEFORE your RAID array was completely resynced.
Therefore you have an incorrect "good known RAID config", and that is the 2nd entry showing 4% resync.

Wait until the array has fully resynced and then run:

/usr/local/bin/raidmonitor -iv

Check the resync progress using
cat /proc/mdstat
...