Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Robert Field on January 28, 2002, 07:17:27 PM
-
Can any body please advise how to read the following. How do I tell which drive is giving the problem.
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] 59769728 blocks [2/2] [UU] resync=4% finish=622.8min
unused devices:
Last known good configuration was:
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdb1[1] hda1[0] 264960 blocks [2/2] [UU]
md0 : active raid1 hdb5[1] hda5[0] 15936 blocks [2/2] [UU]
md1 : active raid1 hdb6[1] hda6[0] 59769728 blocks [2/2] [UU]
unused devices:
-
I've just read a thread from Mahmood Al-Yousif about his RAID/DIALUP problems.
I've just been setting up Freeswan/IPSEC on a couple of SME5 boxes (see earlier postings http://www.e-smith.org/bboard//read.php?v=t&f=3&i=11016&t=9708 ).
I just got the tunnel to connect and one of the servers completly locked. When the box was rebooted I started getting the RAID error as posted earlier.
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] 59769728 blocks [2/2] [UU] resync=4% finish=622.8min
unused devices:
Last known good configuration was:
Personalities : [raid1]
read_ahead 1024 sectors
md2 : active raid1 hdb1[1] hda1[0] 264960 blocks [2/2] [UU]
md0 : active raid1 hdb5[1] hda5[0] 15936 blocks [2/2] [UU]
md1 : active raid1 hdb6[1] hda6[0] 59769728 blocks [2/2] [UU]
unused devices:
Could this be connected with problem Mahmood noted or am I barking up the wrong tree.
-
Well, it just looks like your drives are resyncing... it "appears" normal.
if you do a cat /proc/mdstat it will print out your config.
wait until the resyncing is done.
-
Thanks Fred
Rob