Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Background Parity Initializing/Queued

viktor lindström
Occasional Visitor

Background Parity Initializing/Queued

I`m on a HP proliant with a "Smart Array 6i Controller"(no cluster) with one logic drive and 3 disks on a "RAID 5" After we got a message about one drive needed to be swapped we replaced it with a new drive and after the rebuild finnish we get Status message 785:

Background parity initialization is currently queued or in progress on logical drive 1 ( RAID 5 in array A). If background parity initialization is queued, it will start when I/O is performed on the drive. When background parity initialization completes, the performance of the logical drive will improve.

And i think that message has been there a couple of days how do we solve this?
22 REPLIES
Aks2
Valued Contributor

Re: Background Parity Initializing/Queued

Hi,
Please run the adu report and attach the report so that we can get more information regarding the issue.

Cheers
Akarsh
viktor lindström
Occasional Visitor

Re: Background Parity Initializing/Queued

Heres the report!
Jarv_1
Occasional Visitor

Re: Background Parity Initializing/Queued

Hi,

I just recieved the same error after a rebuild of the arrray on a ML 370 with and online spare. It is a Samrt array 642 Controller.

Any solutions???
KarloChacon
Honored Contributor

Re: Background Parity Initializing/Queued

hi viktor

what is the server model? and OS?

so try applying the latest firmware CD for your server?

also I recommend you to have the more recent Array diagnostic utility (now you have 7.4)

the idea is to get a more accurate error report.

can you get into your OS?

regards
Didn't your momma teach you to say thanks!
Sasha Knezevic
Occasional Visitor

Re: Background Parity Initializing/Queued

Hello All

I'm having the same problem on one of our old servers.

It is a ProLiant ML350 G3.

Server works. I'm able to log in and make changes. I believe I can notice it operating a little sluggish.

Any ideas?
Brian Wright_1
Frequent Advisor

Re: Background Parity Initializing/Queued

I am having the same issue on an ML370 G1, it's been there for weeks, I've copied huge files to/from, ran diskeeper, and the problem still isn't going away.
Be Patient, I'm reloading.
Michael Schepers
Occasional Visitor

Re: Background Parity Initializing/Queued

I am having the same issue with a Compaq ML370 G1. I have updated to the latest available drivers. After a very long time (about 2 weeks) this message finally went away on its own, but now that I have expanded the RAID volume I have been trying to use various partitioning tools (Acronis, Gpart, etc.) to let the operating system (Windows 2003) see the increased space. None of these tools will see this expanded partition. However, it is working within Windows at its original capacity.

Even more interesting, I have 2 RAID arrays on this same controller (C is RAID-1 and D is RAID5) and all the tools can see the C drive, but none can see the D drive.

I am not absolutely sure if these problems are related or not. Any one else seeing similar issues?

Thanks,
Mike
Brian Wright_1
Frequent Advisor

Re: Background Parity Initializing/Queued

Mine is identical Raid configuration, I have not tried to extend the 2nd Array, because there is no need, But I've never had a problem extending an array, and using diskpart to make windows use the avalaible space.
Be Patient, I'm reloading.
Srdjan_2
Advisor

Re: Background Parity Initializing/Queued

I am having same problem at DL380. After expanding RAID5 with 3 disks to RAID5 with 5 disks message appeared and stayed for allmost two months! I have latest ACU. Does anyone knows solution?

tnx
Srdjan
Víctor Cespón
Honored Contributor

Re: Background Parity Initializing/Queued

Hi, this is a summary of what I have found searching several cases.

1st, check this advisory (available only though google cache):
http://66.102.9.104/search?q=cache:a4dmEdpMAO0J:h200003.www2.hp.com/bizsupport/TechSupport/Document.jsp%3Flang%3Des%26cc%3Des%26taskId%3D110%26prodSeriesId%3D316599%26prodTypeId%3D15351%26objectID%3DPSD_EC030424_CW01+EC030424_CW01&hl=es&ct=clnk&cd=1

2nd: background parity initialization is started only after the logical unit has been idle for 15 seconds. In a cluster, it's written at least once every 3 seconds.

3rd: The background parity initialization is also not started if the logical unit has not been accessed at all.
Aks2
Valued Contributor

Re: Background Parity Initializing/Queued

The ACU messages are informational and require no action. The message is no longer displayed once the background parity initialization process completes
Yayat
Frequent Advisor

Re: Background Parity Initializing/Queued

"Still waiting the final solving from the expert"
I also have the same case on my DL380G4 with it's native SA6i configured as 1 array & 2 logical drive (100Gb and 1.4TB). I think that SA do the task sequencely, mean logical 1 first then logical 2, rebuilding or parity initializing. My logical drive 2 status is now OK, it mean rebuild & parity initial has completed successfully, am I right ? But the logical drive 1 that only 100GB status is still in "Backgroud Parity Initializing". That message had been there since a week ago, when that will get out from there . What shoud I do next ?
marvin porras
Occasional Visitor

Re: Background Parity Initializing/Queued

ok, one thing to notice here, i guess by now the issue was solved, for everyone, but one thing to notice is that everyone is having that problem with a raid 5 doesnt matter the ammount of hhd's.
one question have you guys had the change the rebuild priority in ACU to high.
cause you know that if its in "low" priority its not going to rebuild unless the server is not being use by anyone.
this is something just to point out.
Yayat
Frequent Advisor

Re: Background Parity Initializing/Queued

Hi viktor,

You're right, change rebuild priority setting to high made the rebuild process proceed more immediately. But in my case still need up to about 5x24 hours. Sorry I forgot to reply the forum when I done. BTW thank you for your reply.

Regard,
Megan Moore
Occasional Advisor

Re: Background Parity Initializing/Queued

Is it possible to monitor the progress of the parity initialization? Mine has been running for 4 days now on a 1TB volume.

I have my expand and parity set to high. Is there anything else I can do?


Yayat
Frequent Advisor

Re: Background Parity Initializing/Queued

Hi Megan,

set both expand and rebuild priority setting to HIGH, this will reduce the time to expand or rebuild the array, because it will process the expand or rebuild not only when the server idle. As I know, there is no availability to monitor parity check status. As I note from the forum that it need about 15 minutes/GB to process. After expanding is completed then the parity check begin.Maybe somebody else know how many time needed to check parity/GB.Thank you.

Yayat
Megan Moore
Occasional Advisor

Re: Background Parity Initializing/Queued

Thanks for the reply.

What is the technical difference between building an array and initializing parity?

rawahi77
Occasional Visitor

Re: Background Parity Initializing/Queued

Guys,

If i expand the Rebuild and Expand Priority; will that cause the deletion of the data currently exist in hte logical drives.
Yayat
Frequent Advisor

Re: Background Parity Initializing/Queued

Increase priority to expand and rebuild array should never delete your existing logical drive. It only sets how the array resource will be given for expand and rebuild array regards on the disk business. Hope this help.
Jon Morlan
Occasional Visitor

Re: Background Parity Initializing/Queued

Iâ m adding this update to this old thread since I believe that I have found the solution to this problem. I have been able to clear this error by doing the following, and since I could not find this process anywhere on the net; I figured I would add it here so that the next person googling would find this and be able to fix their issue.

The cause for this is that the Parity initialization is hung or frozen and some array tools do not show this since the Parity Initialization percentage complete is not shown.

I had several servers all affected by this issue and was able to clear them all be doing the following

Have Array configuration utility version 8.28.13.0 installed. This is cp010232.exe

From inside the array configuration utility, if you choose the logical drive that has the 785 alert on it and choose â More Informationâ you will see that there will be a percentage showing as to the percent complete. It seems that this process for me anyway was hung at 0 percent for several servers and 17 for another.

Other versions of the array config utility for some reason do not show this percentage readout, only that the status is â in progressâ . These versions include 8.50.5.0 and 8.50.6.0.

What cleared this issue here was a reboot. After a reboot on the affected servers was done the parity initialization took right off and ran to completion. I was able to watch this occur by refreshing the % readout from inside the 8.28.13.0 version of the ACU.

Bottom line here is that the Parity Initialization may be stuck for some unknown reason and since the only version of the ACU (8.28.13.0) that I could find shows the percentage complete. If you donâ t have a version of the ACU that shows this percentage readout it could be hung and you donâ t know it. And all it takes to resolve it is a reboot.


Searchable Keywords
Morjo15 morjo15 Array Configuration Utility stuck hung 785 cp010232.exe 8.50.5.0 8.50.6.0 8.28.13.0 solution fix
williamaperry
Occasional Visitor

Re: Background Parity Initializing/Queued

Just wait.   This message is not earth shattering.  The background parity can take a while to initialize.  It is not critical to the operation of your server; however, when finished the slight performance ding you feel will go away, and your server will have a higher degree of reliability.

 

Also, I am guessing by now it has gone away...

Mauricamo
Occasional Visitor

Re: Background Parity Initializing/Queued

I faced the same issue this morning on a G7 Bl460c using a D6000 Disk Array.  In my case the parity Initialization mismatch was due to the type of array I selected.  I came back to Raid 5 using 4 x 3 TB to create mountpoint drives and now the Background Parity Initialization started to run in the background.  After a full refresh and a server reboot the process completed successfully and now it is gone.