We have an ES40 running Tru64 5.1a. This morning when I arrived at work
the system was OK. But after a few minutes, NFS became unavailable. I
could still ping the system, but I could not login via ssh or xdm at the
console.
So for lack of any other options, I rebooted the system. Once it was
back up, I looked in the log files for a hint as to why the system became
unresponsive. Seeing nothing interesting in /var/adm/messages prior to
the freeze, I looked at the boot messages. I saw the following:
Feb 27 08:18:35 structure vmunix: cam_logger: SCSI event packet
Feb 27 08:18:35 structure vmunix: cam_logger: hardware_id=57 bus 3 target 0 lun
+0
Feb 27 08:18:35 structure vmunix: cdisk_op_spin
Feb 27 08:18:35 structure vmunix: Device Not Ready
Feb 27 08:18:35 structure vmunix: Hard Error Detected
Feb 27 08:18:35 structure vmunix: Hardware ID = 57
Feb 27 08:18:35 structure vmunix: COMPAQ CRD-8402B 1.03
Feb 27 08:18:35 structure vmunix: Active CCB at time of error
Feb 27 08:18:35 structure vmunix: CCB request completed with an error
Feb 27 08:18:35 structure vmunix: Error, exception, or abnormal condition
Feb 27 08:18:35 structure vmunix: NOT READY - Logical unit is NOT ready
Any idea what this means? How can I tell which device is:
hardware_id=57 bus 3 target 0 lun 0
Also, any other hints as to where to look for the cause of the freeze?
Thanks.
--
Steve Feehan
Unix Systems Administrator
Structural Biology and Bioinformatics Group
University of Vermont
Received on Wed Feb 27 2002 - 13:47:53 NZDT