- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL370 G6 with SAS p410i HpCISSs2 129
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-19-2009 07:52 AM
тАО10-19-2009 07:52 AM
DL370 G6 with SAS p410i HpCISSs2 129
DL370 G6
HP P401i controller (firmware 2.50) with 512MB of cache.
Hot-swap 16 of 15K 146.8GB SAS disks.
OS:
Windows 2003 Standard Edition R2 with SP2
When testing the IO subsystem using SQLIO.exe tool every once in awhile we are able to hang the server and see the following errors in the error log:
Source: HpCISSs2
EventID: 129
The description for Event ID ( 129 ) in Source ( HpCISSs2 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\RaidPort0.
The error appears every 30 seconds.
When the error appears and we try to open the Array Configuration Utilities they do not open up. The only way to get rid of the error is to hard-reboot the server.
Installed latest version of the RAID Controller driver (6.18.0.32) and of controller firmware (2.50).
Not sure how to proceed.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2009 06:29 AM
тАО12-17-2009 06:29 AM
Re: DL370 G6 with SAS p410i HpCISSs2 129
Ours is still running on old Firmware (1.66) and driver (6.14.0.64), and after reading a number of posts ion this, I am not too eager to upgrade, since it doesn't seem to fix anything......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2009 07:20 AM
тАО12-17-2009 07:20 AM
Re: DL370 G6 with SAS p410i HpCISSs2 129
We have resolved the issue by getting HP support to send us a replacement battery-backed-up-caching module. I think the problem was in that device.
Let me know if it resolves your problem.
Thanks,
Arsen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2009 11:06 AM
тАО12-17-2009 11:06 AM
Re: DL370 G6 with SAS p410i HpCISSs2 129
Thanks,
Karl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2009 02:22 PM
тАО12-17-2009 02:22 PM
Re: DL370 G6 with SAS p410i HpCISSs2 129
For us the problem did not disappear (when using SQLIO) after upgrade of the firmware to 2.50. After many hours on the phone with HP support, they thought that the problem is with the caching module whose firmware cannot be upgraded. So they sent us a replacement that fixed the problem.