- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Proliant Windows 2003 Server cqpcissm timeout
ProLiant Servers (ML,DL,SL)
1753894
Members
7730
Online
108809
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
12-02-2004 01:36 AM
12-02-2004 01:36 AM
Proliant Windows 2003 Server cqpcissm timeout
Hi
We have a Proliant DL380 G2 with the following raid config -
5 disks(2 - raid 1 36.4Gb, 3 - raid 5 72.8Gb) + DDS4 20/40 Hot tape drive plug on a Smart Array 5300 Controller.
During heavy drive access (e.g. exchange cleanup, av scan) we get 'The device, \Device\Scsi\cpqcissm2, did not respond within the timeout period.' numerous times.
The device drivers for the Smart Array 5300 are at version 5.62.0.32 which I believe to be the latest.
On a number of occasions the server has shutdown after a number timeout errors in the event log
Can anyone shed any light on this ? (I've looked around hp etc, but cannot find anything specific).
Thanks in advance
We have a Proliant DL380 G2 with the following raid config -
5 disks(2 - raid 1 36.4Gb, 3 - raid 5 72.8Gb) + DDS4 20/40 Hot tape drive plug on a Smart Array 5300 Controller.
During heavy drive access (e.g. exchange cleanup, av scan) we get 'The device, \Device\Scsi\cpqcissm2, did not respond within the timeout period.' numerous times.
The device drivers for the Smart Array 5300 are at version 5.62.0.32 which I believe to be the latest.
On a number of occasions the server has shutdown after a number timeout errors in the event log
Can anyone shed any light on this ? (I've looked around hp etc, but cannot find anything specific).
Thanks in advance
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2005 10:50 AM
04-14-2005 10:50 AM
Re: Proliant Windows 2003 Server cqpcissm timeout
I'm having the exact same problem on a DL380 G3 with an MSA20 attached.
What device is the cpqissm2 driver for exactly?
I have a Smart Array 6400 Controller, and a Smart Array 5i controller, as well as an LSI Logic 53C1010-33.
The MSA20 contains 10x 250GB SATA Disks, and there is also a Quantam LTO2 Superloader attached.
From the scarce information i've read on the net, it seems to be something with either termination, or a driver issue.
If anyone could shed some light on this I'd be grateful.
Thanks.
What device is the cpqissm2 driver for exactly?
I have a Smart Array 6400 Controller, and a Smart Array 5i controller, as well as an LSI Logic 53C1010-33.
The MSA20 contains 10x 250GB SATA Disks, and there is also a Quantam LTO2 Superloader attached.
From the scarce information i've read on the net, it seems to be something with either termination, or a driver issue.
If anyone could shed some light on this I'd be grateful.
Thanks.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP