From owner-freebsd-scsi Mon Jun 21 0:10:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CFF514CC0 for ; Mon, 21 Jun 1999 00:10:22 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id BAA26020; Mon, 21 Jun 1999 01:10:17 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906210710.BAA26020@panzer.plutotech.com> Subject: Re: missing time and date in SCSI syslog messages In-Reply-To: <19990621084718.A38627@titan.klemm.gtn.com> from Andreas Klemm at "Jun 21, 1999 08:47:18 am" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Mon, 21 Jun 1999 01:10:17 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas Klemm wrote... > Hi ! > > Would it be possible, to write out time and date when reporting > scsi errors via syslog. This isn't syslog output, it's dmesg output. Syslog writes out the time and date on every line. > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x3a > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x50 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x50 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > > BTW, what do you think about that ? Time to buy a new drive ? It looks like you have a cabling or termination problem. Or perhaps a bent pin somewhere. It doesn't necessarily look like a drive problem, but more like a SCSI bus problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message