Windows 2016 Smart Array P440 controller and failed IOCTL errors in StorDiag event log

[deadpete]

Hi folks,

New ProLiant DL180 Gen9 server, Smart Array P440 controller, OS Windows 2016 Standard, all drivers and firmware completely up to date through SPP2017.04.

Under the StorDiag folder and in the log Microsoft-Storage-ClassPnP/Operational, the following error event is logged about 600 times/hour:

"Completing a failed IOCTL request." Event ID=504

The XML is

<quote>

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Microsoft-Windows-StorDiag" Guid="{F5D05B38-80A6-4653-825D-C414E4AB3C68}" />

  <EventID>504</EventID>

  <Version>1</Version>

  <Level>2</Level>

  <Task>200</Task>

  <Opcode>101</Opcode>

  <Keywords>0x800000040000000</Keywords>

  <TimeCreated SystemTime="2017-08-22T16:39:52.784190400Z" />

  <EventRecordID>61057</EventRecordID>

  <Correlation />

  <Execution ProcessID="7596" ThreadID="9320" />

  <Channel>Microsoft-Windows-Storage-ClassPnP/Operational</Channel>

  <Computer>SRV201701.atmos.local</Computer>

  <Security UserID="S-1-5-18" />

  </System>

- <EventData>

  <Data Name="DeviceGUID">{5990E365-D304-8CEE-B0EB-DB1E0DCEBC2D}</Data>

  <Data Name="DeviceNumber">0</Data>

  <Data Name="Vendor">HP</Data>

  <Data Name="Model">LOGICAL VOLUME</Data>

  <Data Name="FirmwareVersion">5.52</Data>

  <Data Name="SerialNumber">PDNMF0ARH752OZ</Data>

  <Data Name="IrpStatus">0xc0000185</Data>

  <Data Name="IoctlControlCode">0x74080</Data>

  </EventData>

  </Event>

</quote>

Is this a serious error, or only informative? When there are problems with IOCTLs, it use to indicate hardware problems, and I don't want to deploy something I must throw out next week.

Any suggestions welcome.

Best regards,

Pete

[deadpete]

Hi folks,

I've been digging a bit more trying to pinpoint the problem. I uninstalled the HP ProLiant Agentless Management Service, and the errors stopped filling up the log. It also seemed that this service flooded the PowerShell log with informational messages (~40000 per day), which now is down to the occasional logging of "normal" PowerShell events.

But the question remains, whether there are issues with the controller or motherboard interface, or buggy software. Running diagnostics on the controller gives nothing, everything in good order.

Checking on the temperatures, sensor 25 reports a temperature of 75 °C. IMHO it seems a bit high, but still well within limits.

Any comments very welcome.

Best regards,

Pete