software raid 5 degraded
Posted by Hikaru-71 on 2012/6/20 10:51:48
Hi, i has got following question:
There is fresh installation of CentOS 6.2 with software raid 5 configured with anaconda, and it is degraded from the beginning (although it has spare device)
/proc/mdstat doesn't show that raid is rebuilding.
Seems to me there is something wrong, but i don't know what should be done in this situation. All disks are working.
There is fresh installation of CentOS 6.2 with software raid 5 configured with anaconda, and it is degraded from the beginning (although it has spare device)
/dev/md1:
Version : 1.1
Creation Time : Wed Jun 20 09:59:33 2012
Raid Level : raid5
Array Size : 975744000 (930.54 GiB 999.16 GB)
Used Dev Size : 487872000 (465.27 GiB 499.58 GB)
Raid Devices : 3
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Wed Jun 20 14:40:27 2012
State : active, degraded
Active Devices : 2
Working Devices : 4
Failed Devices : 0
Spare Devices : 2
Layout : left-symmetric
Chunk Size : 512K
Name : mail:1 (local to host mail)
UUID : 4df78011:4219ff72:edb6c4f9:a18ad234
Events : 1605
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
4 8 34 2 spare rebuilding /dev/sdc2
3 8 50 - spare /dev/sdd2
/proc/mdstat doesn't show that raid is rebuilding.
Seems to me there is something wrong, but i don't know what should be done in this situation. All disks are working.
Re: software raid 5 degraded
Posted by WhatsHisName on 2012/6/20 21:56:39
Quote:
No, completely normal.
The parity information does not exist when the raid is created and must be calculated de novo for the entire raid.
Just let it finish rebuilding before you reboot. To monitor:
There is fresh installation of CentOS 6.2 with software raid 5 configured with anaconda, and it is degraded from the beginning (although it has spare device)
...
Seems to me there is something wrong, but i don't know what should be done in this situation. All disks are working.
No, completely normal.
The parity information does not exist when the raid is created and must be calculated de novo for the entire raid.
Just let it finish rebuilding before you reboot. To monitor:
# cat /proc/mdstat
This Post was from: https://www.centos.org/newbb/viewtopic.php?forum=57&topic_id=37878