Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: beckynet on May 07, 2010, 11:39:03 AM
-
Helo World I need your help,
I've a strange issue with my software raid.
The rebuild can't start because an half part of good situation is on other disk, how can I solve that ?
Thanks a lot
Beeckmans Olivier
[root@bersrv001 subsys]# mdadm -D /dev/md1
/dev/md1:
Version : 00.90.01
Creation Time : Wed Sep 10 11:30:16 2008
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Device Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Fri May 7 09:59:38 2010
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 81ee50fb:078e48d8:39e189ce:caaa65b7
Events : 0.3420
Number Major Minor RaidDevice State
0 0 0 - removed
1 8 17 1 active sync /dev/sdb1
[root@bersrv001 subsys]# mdadm -D /dev/md2
/dev/md2:
Version : 00.90.01
Creation Time : Wed Sep 10 11:30:16 2008
Raid Level : raid1
Array Size : 244035264 (232.73 GiB 249.89 GB)
Device Size : 244035264 (232.73 GiB 249.89 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Fri May 7 11:31:17 2010
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 49cdeb5c:e77464a4:79fd61f7:d6c538b5
Events : 0.23358228
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 0 0 - removed
-
first of all be sure to have a working backup
then try
mdadm -a /dev/md1 /dev/sda1
check rebuilding process with
cat /proc/mdstat
if something goes wrong, check /var/log/messages for errors
then
mdadm -a /dev/md2 /dev/sdb2
and, again check rebuilding status
if something goes wrong, make a backup, do a fresh installation with 2 new hd and restore
HTH
-
The rebuild can't start because an half part of good situation is on other disk, how can I solve that ?
I'm sorry Beeckmans, I don't understand what you are saying here. Could you please explain again what you think the problem is?
-
Stefano thank you for the quick response. And especially for the solution you gave me and worked perfectly.
I bookmark this topic for future purposes.
Another big thank you.
For Charlie Bardy. Sorry for my bad english, it's not my first language. But I think that the mdadm report, explain my trouble... Now all is OK
Olivier Beeckmans
-
I'm sorry Beeckmans, I don't understand what you are saying here. Could you please explain again what you think the problem is?
As far as I understand, OP has this situation:
md2 : active raid1 sda2[1]
156183808 blocks [2/2] [U_]
md1 : active raid1 sdb1[0]
104320 blocks [2/2] [_U]
in this case the "manage disk redudancy" doesn't work
Beckynet, is this the case?
-
As far as I understand, OP has this situation:
md2 : active raid1 sda2[1]
156183808 blocks [2/2] [U_]
md1 : active raid1 sdb1[0]
104320 blocks [2/2] [_U]
in this case the "manage disk redudancy" doesn't work
Yes, that does seem to be the case. In that case, there is potentially a problem with both disks, and he should tred very carefully. [I expect an Army tech to fully understand the importance of tredding carefully.]
-
In fact the problem comes from a system running without UPS and suffered many inappropriate reboot.
The recommendations have been made to the server owner.
But he does not assess the risk of this critical situation.
The day the server does not restart and it will have to wait the necessary time to reconfigure, it will perhaps purchase necessary.
Thanks to you.
Olivier Beeckmans
-
[I expect an Army tech to fully understand the importance of tredding carefully.]
lol