Original post below.
Thanks to Alan Davis who suggested that power management
was the culprit.
After turning off spin down using "dxpower" a week ago, no
SCSI errors have appeared.
The pwr mgmt settings may have gotten reset during installation
of du40F patch kit 1.
-------------------------------------------------------------
> System: DPW 500au, DU4.0F with patch kit 1.
>
> Concern: Getting CAM SCSI errors on Seagate 9GB.
> Five events recorded in 10 days. This system had shown no
> disk errors until applying patch kit 1. All errors
> appear to be identical to the dia excerpt below.
>
> ******************************** ENTRY 119 ********************************
>
>
> Logging OS 2. Digital UNIX
> System Architecture 2. Alpha
> Event sequence number 1434.
> Timestamp of occurrence 20-AUG-1999 07:58:06
> Host name coltrane
>
> System type register x0000001E Systype 30. (Miata)
> Number of CPUs (mpnum) x00000001
> CPU logging event (mperr) x00000000
>
> Event validity 1. O/S claims event is valid
> Event severity 5. Low Priority
> Entry type 199. CAM SCSI Event Type
>
>
> ------- Unit Info -------
> Bus Number 2.
> Unit Number x0088 Target = 1.
> LUN = 0.
> ------- CAM Data -------
> Class x00 Disk
> Subsystem x00 Disk
> Number of Packets 10.
>
> ------ Packet Type ------ 258. Module Name String
>
> Routine Name cdisk_rec_status
>
> ------ Packet Type ------ 256. Generic String
>
> Recovery progress event, this is NOT an
> error
>
> ------ Packet Type ------ 262. Info Error String
>
> Error Type Information Message Detected (recovered)
>
> ------ Packet Type ------ 257. Device Name String
>
> Device Name SEAGATE ST39173W 6244
>
> ------ Packet Type ------ 256. Generic String
>
> Active CCB at time of error
>
> ------ Packet Type ------ 256. Generic String
>
> CCB request completed with an error
>
> ------ Packet Type ------ 1. SCSI I/O Request CCB(CCB_SCSIIO)
> Packet Revision 76.
>
> CCB Address xFFFFFC0013F0BA00
> CCB Length x00C0
> XPT Function Code x01 Execute requested SCSI I/O
> CAM Status x84 CCB Request Completed WITH Error
> Autosense Data Valid for Target
> Path ID 2.
> Target ID 1.
> Target LUN 0.
> CAM Flags x000054C0 Data Direction (11: no data)
> Disable the SIM Queue Frozen State
> Place CCB at head of SIM Queue
> Attempt Sync Data Xfer - SDTR
> *pdrv_ptr xFFFFFC0013F0B6A8
> *next_ccb x0000000000000000
> *req_map x0000000000000000
> void (*cam_cbfcnp)() xFFFFFC00004CE6F0
> *data_ptr x0000000000000000
> Data Transfer Length 0.
> *sense_ptr xFFFFFC0013F0B6D0
> Auotsense Byte Length 64.
> CDB Length 6.
> Scatter/Gather Entry Cnt 0.
> SCSI Status x02 Check Condition
> Autosense Residue Length x2E
> Transfer Residue Length x00000000
> (CDB) Command & Data Buf
>
> 15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
> 0000: 00000000 00000000 00000000 * ............*
>
> Timeout Value x00000014
> *msg_ptr x0000000000000000
> Message Length 0.
> Vendor Unique Flags x0000
> Tag Queue Actions x00
>
> ------ Packet Type ------ 256. Generic String
>
> Error, exception, or abnormal condition
>
> ------ Packet Type ------ 256. Generic String
>
> NOT READY - Logical unit is NOT ready
>
> ------ Packet Type ------ 768. SCSI Sense Data
> Packet Revision 0.
>
> Error Code x70 Current Error
> Segment # x00
> Information Byte 3 x00
> Byte 2 x00
> Byte 1 x00
> Byte 0 x00
> Sense Key x02 Not Ready
> Additional Sense Length x0A
> CMD Specific Info Byte 3 x00
> Byte 2 x00
> Byte 1 x00
> Byte 0 x00
> ASC & ASCQ x0402 ASC = x0004
> ASCQ = x0002
> Logical Unit Not Ready, Initializing
> Command Required
> FRU Code x02
> Sense Key Specific Byte 0 x00 Sense Key Data NOT Valid
> Byte 1 x00
> Byte 2 x00
>
> Addition Sense Data Size Allocated by Driver
>
> Count of valid bytes: 46.
>
>
> 15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
> 0000: 00000000 00000000 00000000 00000000 *................*
> 0010: 00000000 00000000 00000000 00000000 *................*
> 0020: 00000000 00000000 00000000 00000000 *................*
Received on Mon Aug 30 1999 - 19:23:53 NZST