LogicalDisk BusyTime Failed (19008)

[Mitch James]

What is this error and how to I fix it?

[Rob Buxton]

Your disk is busy.
Find the application and stop it.

Typically you might get this during Backups, in which case it would be expected.

[Frank Neubert_1]

We are getting these alerts a lot as well.
Other than the obvious below, would added more disk space to this help. this is not the busiest server we have either, any ideas.


Event Name: LogicalDisk BusyTime Failed (19008)
Event originator: "server name"
Event Severity: Critical
Event received: 28-Sep-2005, 00:41:08

Event description: The LogicalDisk BusyTime performance property is set to critical.

Disk Instance: S:
Disk Busy percent: 100

[Rob Buxton]

I've started seeing this a lot more since I moved to PSP 7.40A.
I've got PMP on one of the Servers and this did not seem to back up the alert generated from the Agent.
I'm seeing more CPU threshold alerts as well, but I've not yet had time to assess these against PMP.
But they're equally suspicious as some of the Servers are our DR Servers, and they're hardly used.

[Francis Nickels]

We are seeing alot more threshold exceeded events, such as the one noted here, after installing the 7.4 agents.

Does anyone know if there is a way to configure how long the threshold should be exceeded for before triggering an event?

It was working fine for us with 7.2 & 7.3, now we are getting so many, what I call false alarms, that it is rendering the notifications useless.

[Hense, Klaus]

I have the same Problem after Install PSP 7.4!
I can´t find the reasons.
It must be a PSP 7.4 Problem....

[Rodolphe_1]

Francis Nickels :

"Does anyone know if there is a way to configure how long the threshold should be exceeded for before triggering an event?"

Same question : this error appears on our servers during the backup at night, but it could be interesting to know the "limit time" before event...

[Brian Kerr_1]

Just add another data point to this thread. We're seeing the same thing having gone to v7.40 on disks that were fine on v7.3. The MIB suggests that disc activity should be greater than the thresholds for 15 consecutive time periods, I suspect it may only be looking at 1 time period.

[Christopher Knight]

Has anyone found a solution to this?

I am having the same problem with 7.40b agents.

thanks,

[Megan Graye]

We have SIM agent 6.40.0.0 deployed and are getting this notification as well.

[Eichinger Sebastian]

We have this Problem with PSP 7.51a.

Has someone tried to change the RAID controller settings to 100% "read chache" and solve this the problem?

[sandeep_raman]

Hello Eichinger,

Whats the:

# Server model
# Os
# Smart array controller

SRH

[Eichinger Sebastian]

Server ML370 G4
OS W2k3
SA 642

[sandeep_raman]

The latest smart array controller firmware ver 2.74 cured the problem for me.
See if it makes a difference on your server.

http://h18007.www1.hp.com/support/files/storage/us/download/26499.html

SRH

[Eichinger Sebastian]

Okay I'm on 2.68

I will try it as soon as posible

Sebastian

[sandeep_raman]

Sure,please do not forget to post the outcome.

[Eichinger Sebastian]

I have update both controller on this server,
SA642 and 6400 to firmware 2.74 form 2.68.

But I get the same messages:

Event Name: LogicalDisk BusyTime Failed (19008)
Event originator: mgag11
Event Severity: Critical
Event received: 23-Jan-2007, 02:32:02

Event description: The LogicalDisk BusyTime performance property is set to critical.

Disk Instance: D:
Disk Busy percent: 97


What can I try else?
Should I also use the latests PSP?

Sebastian

[Eichinger Sebastian]

Today I get following message at a server restart:
1734-Slot 1 Drive Array Disk Drive(s) Responding to Incorrect SCSI ID
Back up Data, Replace faulty drive, Reconfigure array and Restore SCSI Port 1: SCSI IDs 4, 5

see attachment MGAG11-HD-Error.jpg

I have update the HD firmware from HPB7 to HPBC on this HDs (BD14687B52)

What could be wrong?

Sebastian

[sandeep_raman]

Hmmm,wierd.

# If it loads the Os thereafter,attach the HP Adu log
# Screenshot from HP Acu of both physical and logical view
# What was the reason for the server restart?

SRH

[Eichinger Sebastian]

It's also weird for me!

But the OS starts.
You will find the ADU-report.zip, the ACU-logic.jpg and the ACU-phys.jpg in the attached ADU-ACU.zip.

Teh reason for the restart was the upgrade from PSP 7.51 to 7.70.

Sebastian

[Eichinger Sebastian]

Now I'm looking for a soultion.

Therefore I have changed the 2 HD's with the SCSI ID 4 and 5, but the boot-message still the same.
I think the new SA6400 firmware 2.74 have a problem with 2 Raids, special with first Raid as Raid5 and second as Raid1.

Could that be, how can I check this?

Sebastian

[jd653687]

Have the same problem. After update the Smart array 6400 firmware to 2.74 the raid 1 disks give the same error: Drive responding to incorrect SCSI ID. But everything seems to work fine. When removing one disk and replace it the new disk is only recognized after reboot.

[jd653687]

Some more info.
ML370 G4
Smart Array 6400
2 arrays A 2 36GB 15 rpm raid1+0
B 3 36GB 15 rpm raid 5
All drives have the latest firmware.
On the B-Array (failing disk) only the "Arrow" light is lighting up, the "disk" light is off. No amber color is shown.

[Eichinger Sebastian]

It's the same by me.

That mast be a SA6400 problem with FW 2.74, because now I use older 9.1GB HD's with latest firmware.

[Server-Support]

ok, shall I update the software and the firmware to get rid of this problem ?

since this seems to be a software bug rather than actual hardware error.