01-04-2012 06:52 AM
We have had these servers deployed since mid-March with no problems until we started updating the firmware and BIOS in late October. Since then, we have averaged about 1 server failure every 6 weeks with this error. HP tries to insist that it is the controller’s fault. We have found through troubleshooting that if we install known good drives into the box, the problem goes away. If we install the failed drives into another known good box, this error will follow the drives, not the controller. The drives (both of them) are unusable at this point.
We can remove the drives from the box, run SmartStart utility and the controller is visible. If we reinsert the drives and run SmartStart, the controller is not visible.
The following message is displayed during POST, it appears to be very specific with the dlu code, but I haven't been able to find any kind of information:
1783 – Slot 0 Drive Array Controller Failure! Command failure (cmd=0h, err=00h, dlu=013:5h)
ProLiant ML350 G6 (2011.05.05 – D22)
Smart Array p410i (5.06) (RAID 0+1)
2 x 300GB SAS drives(various, EF0300FATFD – HPD2, EF0300FARMU – HPD3)
Windows Server 2008 (W32 – Standard) – SP2
01-04-2012 09:38 AM
Have you run the firmware upgrade (version 9.3) to update the FW on the drives? make sure they have updated firmware too. There has been quite a bit of chatter on drive FW incompatibility with the new P series of controllers (which are not HP, but just branded HP).
You have to put the drivers into the box and then boot with the FW DVD to update the FW on the drive. The FW update manager will automatically update the FW on the drives.
I think you have FW HPD2 and HPD3 on your drives. Not sure where the current revision is for your type of drive.
Have you tried a new controller?
01-04-2012 12:06 PM
Thanks for the info on the controller, I will look into it. Back when all of this started, we were pushing the drive f/w updates through HPSIM. That was when we had our first occurance. The controller is integrated on the system board, no cache module, but when we move drives to another system, problem follows the drives.. Known good drives work fine.