Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: BobWilliams on August 25, 2004, 09:39:05 PM

Title: SME 6 Raid 1 Monitor How To
Post by: BobWilliams on August 25, 2004, 09:39:05 PM
Can somebody tell me where to find Darrell May's "Raid1 Monitor How To"? I have looked on the forum and Contribs but can't seem to find it.

Thanks

Bob...
Title: SME 6 Raid 1 Monitor How To
Post by: Henk on August 25, 2004, 10:19:21 PM
http://mirror.contribs.org/smeserver/contribs/dmay/mitel/contrib/raidmonitor/
Title: SME 6 Raid 1 Monitor How To
Post by: BobWilliams on August 25, 2004, 10:26:08 PM
Thats it. Thanks. I didn't see it before when I looked.

Bob...
Title: SME 6 Raid 1 Monitor How To
Post by: BobWilliams on August 31, 2004, 10:38:41 PM
OK, I read Darrell May's "Raid Monitor How To" and installed RaidMonitor. Works great. But now I receive 10 consecutive messages from RaidMonitor with the following content every day:
 
ALARM! RAID configuration problem

Current configuration is:

Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hda3[0] hdc3[1]
      262016 blocks [2/2] [UU]
     
md1 : active raid1 hda2[0] hdc2[1]
      32662656 blocks [2/2] [UU]
     
md0 : active raid1 hda1[0] hdc1[1]
      102208 blocks [2/2] [UU]
     
unused devices: <none>

Last known good configuration was:

Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdc3[1] hda3[0]
      262016 blocks [2/2] [UU]
     
md1 : active raid1 hdc2[1] hda2[0]
      32662656 blocks [2/2] [UU]
     
md0 : active raid1 hdc1[1] hda1[0]
      102208 blocks [2/2] [UU]
     
unused devices: <none>

Only thing I can see different is that the dev addresses are reversed. i.e. good entry hdc3[1] hda3 [1] bad entry hda3
I don't understand whats wrong. Raid-1 seems to be working just fine.

Bob Williams...
Title: SME 6 Raid 1 Monitor How To
Post by: Boris on September 01, 2004, 12:22:19 AM
run raidmonitor -iv to save the current status.
Title: SME 6 Raid 1 Monitor How To
Post by: BobWilliams on September 01, 2004, 12:36:31 AM
Thanks Boris..
Yes, I do that but the messages come back again!
So far everything worked out great. I simulated a primary master and secondary master disk drive failure and recovered from both with out any problem.
I feel confident that I can support this server as far as disk failures are concerned. Even used the Emergency Boot diskette when the primary master failed and the server wouldn't boot. My configuration has a spare disk drive with the exact same drive as both masters and I have it partitioned and formated ready to go in case of a failure. On my next server build if I have to, can I use a larger drive as a spare in case I can't find an exact same drive for a replacement?

Bob...
Title: SME 6 Raid 1 Monitor How To
Post by: Boris on September 01, 2004, 08:07:17 PM
>>> On my next server build if I have to, can I use a larger drive as a spare in case I can't find an exact same drive for a replacement?

Yes you can. Some space on it will be left unused, but otherwise it would work.
Title: SME 6 Raid 1 Monitor How To
Post by: mbachmann on September 02, 2004, 09:25:39 AM
Quote from: "BobWilliams"
.... but the messages come back again ...


I solved it the following way. Not elegant, but it worked out for me and raidmonitor now keeps quit. I think it is a config issue with lilo sometimes recognizing false partition data/drive geometry/partition tables reported through the bios.

- take a look cat /proc/mdstat for your convenience
- take a look here for
Code: [Select]
lsraid and
Code: [Select]
mdadm and other raid-related data http://www.tldp.org/HOWTO/Software-RAID-HOWTO.html#toc6

I had to rebuild the array, you don't have to as i see from your posting.

- uninstall raidmonitor via rpm -e.
- delete the raidmon cron-entry in /etc/cron.d
- make a backup of /etc/lilo.conf
- issue /sbin/lilo to write a new lilo.conf
- post-upgrade, reboot, reinstall raidmon an raidmonotor -iv it.
- wait

hope it helps