Date: Fri, 07 Jan 2005 17:28:00 -0700 (MST) From: Warner Losh <imp@harmony.village.org> To: scsi@freebsd.org Subject: Worrisome or no? Message-ID: <20050107.172800.74744432.imp@harmony.village.org>
next in thread | raw e-mail | index | archive | help
I think I have something wrong with my system. I'm not sure what, and am trying to diagnose it. I have a 19190 card with one drive on it. The drive is connected via a cable that's believed good, through an SCA adapter that's likely believed to be good to a 36GB drive that's wide Ultra (40MB/s): da0 at ahc0 bus 0 target 0 lun 0 da0: <FUJITSU MAF3364L SUN36G 1213> Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Every so often (once every few hours) I'm getting the following in dmesg: (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x1a7) SCSIRATE(0x95) (da0:ahc0:0:0:0): READ(10). CDB: 28 0 2 81 97 c7 0 0 80 0 (da0:ahc0:0:0:0): CAM Status: SCSI Status Error (da0:ahc0:0:0:0): SCSI Status: Check Condition (da0:ahc0:0:0:0): ABORTED COMMAND asc:48,0 (da0:ahc0:0:0:0): Initiator detected error message received (da0:ahc0:0:0:0): Retrying Command (per Sense Data) What do these indicate? A bad path to disk? A bad disk? A bad controller? Space alien fucking with me? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050107.172800.74744432.imp>