Windows Server 2003
Showing results for 
Search instead for 
Did you mean: 

adu showing background parity initilization running, why ?

Lynn Storey_1
Occasional Advisor

adu showing background parity initilization running, why ?

I have already posted this under hardware , but have not yet had a response.

Proliant server has 32GB of memory running SQL database. Looks like SQL is using 29Gb of the 32Gb of available memory. Rebooting the server seems to fix the slow response for a period of time.

Ran ADU and found that there was a background parity check running on logical drive 1 which is running off of a Smart Array P400.

The logical is 4 - 72gb SAS drives in a raid 5 configuration.

The firmware version for the P400 is 5.20.

Just wondering why this would be happening to begin with and if this might be related to the occasional performance issue. But one would think that if the background parity check was causing this it would resume after the reboot and the performance issue would still be observed.

I will attach the ADU log files.

I don't know if it is a issue with the background parity checks, or is it a SLQ performance issue.
Frequent Advisor

Re: adu showing background parity initilization running, why ?

SQL is well known that it eats the cpu. Have you tired rather than rebooting the server. Cycling the SQL services to see if it is SQL or ADU.

Also have the drives\storage controller got the latest firmware