Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: del on September 07, 2004, 01:23:38 AM
-
Hi All,
I got this email from root today, can someone help me decipher it! Thanks
ALARM! RAID configuration problem
Current configuration is:
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hda3[0] hdc3[1]
264512 blocks [2/2] [UU]
md1 : active raid1 hda2[0] hdc2[1]
59678528 blocks [2/2] [UU]
md0 : active raid1 hda1[0](F) hdc1[1]
104320 blocks [2/1] [_U]
unused devices: <none>
Last known good configuration was:
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hda3[0] hdc3[1]
264512 blocks [2/2] [UU]
md1 : active raid1 hda2[0] hdc2[1]
59678528 blocks [2/2] [UU]
md0 : active raid1 hda1[0] hdc1[1]
104320 blocks [2/2] [UU]
unused devices: <none>
Regards,
Del
-
Read the HOWTOs at
http://mirror.contribs.org/smeserver/contribs/dmay/mitel/contrib/raidmonitor/
-
Hi Ray,
Thanks for the link, I had already looked at the howto, but what I can't work out is that in the example it shows a missing U on each line and mine only shows it on the last line:
md0 : active raid1 hda1[0](F) hdc1[1]
104320 blocks [2/1] [_U]
So I am not sure what to think. The machine is in my office and I live near Cocoa Beach, so I am unable to go there due to Hurricane Frances. I may be able to get there later today.
Regards,
Del
-
It looks like just one of your partitions has failed.
-
Did you find a solution to the corrupted partition?
Bob...
-
Hi Bob,
Not yet, I will try to get in tomorrow and have a look, then post back here.
Regards,
Del
-
Hi All,
OK I finally got power back on Tuesday, I booted up my SME Server, logged on as root and ran /usr/local/bin/raidmonitor -v and got the same result as the email body. I then rebooted and logged back in this time I ran /usr/local/bin/raidmonitor -i and then /usr/local/bin/raidmonitor -v to my surprise it came up clean and I have not had any emails or problems since! So I can only hope that everyting is OK.
Regards,
Del
-
del
> I ran /usr/local/bin/raidmonitor -i and
> then /usr/local/bin/raidmonitor -v
That will just reset the raidmonitor last known good config. If the drives have not synced or a partition is faulty then it will just stay that way.
What does
cat /proc/mdstat
tell you
-
Hi Ray,
Thanks for your help, sorry it took so long, but I have been out of town for a couple of days.
It seems that something is not still not right.
==========================================
[root@linux-server root]# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hda3[0] hdc3[1]
264512 blocks [2/2] [UU]
md1 : active raid1 hda2[0] hdc2[1]
59678528 blocks [2/2] [UU]
md0 : active raid1 hdc1[1]
104320 blocks [2/1] [_U]
unused devices: <none>
==========================
My other problem is that they are both old 30gb HDD's and I can't get a new one to match so I will probably have to buy 2 new ones and reinstall, what do you think?
Regards,
Del :cry:
-
del
> md0 : active raid1 hdc1[1]
104320 blocks [2/1] [_U]
.......what do you think?
It seems you don't understand what has happened here and you think it can just go away by resetting the RAID monitor. I don't know why one partition only has failed, I would have thought all partitions on one drive would fail. My only suggestion is to follow the instructions in the HOWTO and try to rebuild the array.
-
Del, try this:
/sbin/raidhotadd /dev/md0 /dev/hda1
then
raidmonitor -v
it will start re-syncing that partition. Probably was caused by not rebooting properly...like if the power went out.
When it is done (when you use 'raidmonitor -v' and have [UU], not [_U]) then do this:
raidmonitor -iv
Greg
-
after raidhotadd issue
cat /proc/mdstat
to watch the ongoing recovery process