ProLiant Servers (ML,DL,SL)
cancel
Showing results for 
Search instead for 
Did you mean: 

Checking the logs for the SmartArray P410i controller

Andrew Kaplan
Super Advisor

Checking the logs for the SmartArray P410i controller

Hello --

 

We are running a RAID 5 array using a P410i controller on a Proliant DL380 G7 server running the Windows 2008R2 operating system and SQL Server 2008 database. Several days ago, an unexpected shutdown occurred, which resulted in the mapped drives losing their assigned drive letters. That has since been corrected.

 

I am trying to determine the cause of the shutdown. I have already checked the Windows Event Viewer, and aside from some instances where there were problems connecting to an HP LeftHand diskarray via the iSCSI Initiator, there were no references to an event that would cause the shutdown.

 

My next step is checking the log files of the array controller. I have already done a diagnostics test via the array configuration utility, and there were no errors reported. I also checked the Integrated Management Log Viewer, and there was nothing apparent listed there.

 

What are step(s) should I take to determine what caused the shutdown, and drive letter scrambling to occur?

 

Thanks.

A Journey In The Quest Of Knowledge
1 REPLY
BigDude
Occasional Advisor

Re: Checking the logs for the SmartArray P410i controller

IT sounds like you have covered the bases overall. Generally if an unexpected shutdown has a software source there would be 'something' in the windows event logs. Obviously if you saw a BCCODE (Blue Screen) you are likely looking at a software/driver issue. If however there was really 'nothing' in the windows event logs it is more likely that you hit a hardware issue. It would have had to be an abrupt power interruption (PSU failure) or an NMI from a Motherboard component. Other than the power failure most of these things actually give signs, although in the case of a Motherboard level issue the only sign might another abrupt stop. Definitely run the online diagnostics to see if they pick up anything. You may want to do that after hours because if they do pick up something they can trigger your symptoms again (they generally don't but hardware issues are unpredictable).