BMI-IT
asked on
Background Parity Initializing/Queued
OK.. So at 7am I got an alert that I hot swappable SAS drive was removed!! (no one was in at this time) It then tels me that a new drive was inserted and it has started the rebuild, again no one was around.. What the heck??
Rebuild completes, All fine... it then gives the Background parity initialization is currently queued or in progress (code 758) so ok... Hour and half later Its still at 0%, this is a 750 GB array. I did a phusical check on the server and saw that although the server is functioning fine, every LED is blue on the server.
I logged a case with HP, but would like opinions why the parity initialization has not started.
server 2008 R2
Smart array P410i
ACU Version - 8.30.5.0
Rebuild completes, All fine... it then gives the Background parity initialization is currently queued or in progress (code 758) so ok... Hour and half later Its still at 0%, this is a 750 GB array. I did a phusical check on the server and saw that although the server is functioning fine, every LED is blue on the server.
I logged a case with HP, but would like opinions why the parity initialization has not started.
server 2008 R2
Smart array P410i
ACU Version - 8.30.5.0
ASKER
rebuild priority to Medium, since this is an exchanger server its busy 95% of the time, I'm hesitant to reboot it in case it fails to come back up, never delt with the parity initialization taking so long before.
Similar problem is posted in this thread:
http://h30499.www3.hp.com/t5/Disk-Array/Background-Parity-Initializing-Queued/td-p/4060811#.Umk6sjLLV0w
You can try to change rebuild priority to high and see if any progress.
More the server is busy, slower will be the RAID array rebuild.
Every reboot can be risky. But normally the reboot would not have any effect on RAID array that is rebuilding except that it will start to rebuild it again.
Another risk is that you currently don't have any redundancy on your disk array. So if another disk dies or is removed from array before the array is rebuild you will have a problem.
But you can wait for a second opinion.
http://h30499.www3.hp.com/t5/Disk-Array/Background-Parity-Initializing-Queued/td-p/4060811#.Umk6sjLLV0w
You can try to change rebuild priority to high and see if any progress.
More the server is busy, slower will be the RAID array rebuild.
Every reboot can be risky. But normally the reboot would not have any effect on RAID array that is rebuilding except that it will start to rebuild it again.
Another risk is that you currently don't have any redundancy on your disk array. So if another disk dies or is removed from array before the array is rebuild you will have a problem.
But you can wait for a second opinion.
ASKER
ok next question, can i swap out the offending disk, as it appears that the drive failed before a few days ago and then rebuild it self again!, this error was not noticed!.
given that the Background parity initialization is still at 0 can i hot swap that drive?
given that the Background parity initialization is still at 0 can i hot swap that drive?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad to hear that. I feel much better when an array is back in good shape.
Sorry for not being sooner back to you.
Sorry for not being sooner back to you.
ASKER
this has been resolved
ASKER
.
Some have reported that this rebuild "hang" was resolved with server reboot.