System error

[Boon Lee]

We have a cluster server in our company and this started last week. On node2 in the event viewer\system we are experiencing error log of this nature.

Event ID: 15
Source : cpq32fs2

"The device, \Device\Scsi\cpq32fs21, is not ready for access yet.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

and

Event ID : 11
Source : disk

"The driver detected a controller error on \Device\Harddisk2.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

Is this a sure sign that the controller card is going to go out soon or is the harddisk 2 going to go out soon?

Any help is very much appreciated.

Thanks
Boon Lee

[HGN]

Hi

Even if the error points to the controller it is mostly the hard drive which will have issues, very rare case the controller can have issues.

Rgds

HGN

[Daniel Thrun]

Greetings. Using Eventid.net website I found the below for you... Hope this helps.

Comments Anonymous (Last update 7/28/2004):
This problem is usually linked to hardware issues. In almost all of my experiences, rechecking cables, trying another SCSI ID, and changing the PCI or SCSI port of the attached device (tape drive, etc..) have fixed this.

Jonathan Marrott (Last update 3/18/2004):
In our case, this occured on a Compaq ProLiant cluster server. It was caused by poor shared array access. Sometimes one node will not boot. The cluster services would often fail. It turned out that the SCSI ID# of the two nodes were both set to ID# 7. We modified the SCSI ID# of the first node to ID# 6. Compaq support confirmed.

Woodrow Wayne Collins (Last update 4/30/2003):
This event happens right before event 15 (source dlttape-VRTS) and at the same time as event 57665 (source Backup Exec). Systems exhibiting this behavior should be checked for hardware and specifically SCSI related issues. In almost all cases, these messages are being posted due to hardware problems with either the controller or, more likely, a device that is attached to the controller in question. The hardware problems can be associated with poor cabling, incorrect termination or transfer rate settings, lazy or slow device responses to relinquish the SCSI bus, a faulty device, or, in some cases, a poorly written device driver. See Q154690.
Links Q154690


http://support.microsoft.com/default.aspx?scid=kb;en-us;Q154690

Dan