topic Re: Background Parity Initializing/Queued in Disk Enclosures

Background Parity Initializing/Queued

viktor lindström — Mon, 27 Aug 2007 08:39:35 GMT

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?

Re: Background Parity Initializing/Queued

Aks2 — Wed, 29 Aug 2007 04:38:02 GMT

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

Cheers
Akarsh

Re: Background Parity Initializing/Queued

viktor lindström — Wed, 29 Aug 2007 06:27:32 GMT

Heres the report!

Re: Background Parity Initializing/Queued

Jarv_1 — Tue, 11 Sep 2007 21:46:34 GMT

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???

Re: Background Parity Initializing/Queued

KarloChacon — Tue, 11 Sep 2007 23:41:03 GMT

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

Re: Background Parity Initializing/Queued

Sasha Knezevic — Fri, 02 Nov 2007 03:32:25 GMT

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?

Re: Background Parity Initializing/Queued

Brian Wright_1 — Wed, 14 Nov 2007 06:39:33 GMT

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.

Re: Background Parity Initializing/Queued

Michael Schepers — Wed, 14 Nov 2007 10:02:15 GMT

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

Re: Background Parity Initializing/Queued

Brian Wright_1 — Wed, 14 Nov 2007 16:23:58 GMT

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.

Re: Background Parity Initializing/Queued

Srdjan_2 — Tue, 27 Nov 2007 06:26:51 GMT

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

Re: Background Parity Initializing/Queued

Víctor Cespón — Fri, 24 Jan 2025 08:42:22 GMT

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.

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

Re: Background Parity Initializing/Queued

Aks2 — Wed, 05 Dec 2007 12:48:46 GMT

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

Re: Background Parity Initializing/Queued

Yayat — Thu, 03 Jan 2008 04:12:02 GMT

"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 ?

Re: Background Parity Initializing/Queued

marvin porras — Wed, 26 Mar 2008 18:27:29 GMT

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.

Re: Background Parity Initializing/Queued

Yayat — Thu, 27 Mar 2008 01:09:34 GMT

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,

Re: Background Parity Initializing/Queued

Megan Moore — Tue, 10 Jun 2008 10:18:50 GMT

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?

Re: Background Parity Initializing/Queued

Yayat — Wed, 11 Jun 2008 00:46:56 GMT

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

Re: Background Parity Initializing/Queued

Megan Moore — Wed, 18 Jun 2008 09:08:06 GMT

Thanks for the reply.

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

Re: Background Parity Initializing/Queued

rawahi77 — Mon, 09 Aug 2010 03:17:27 GMT

Guys,

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

Re: Background Parity Initializing/Queued

Yayat — Mon, 09 Aug 2010 06:11:31 GMT

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.