From owner-freebsd-scsi Mon Jun 21 10: 4:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 38462150A7 for ; Mon, 21 Jun 1999 10:04:15 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id TAA15491; Mon, 21 Jun 1999 19:04:13 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id SAA53832; Mon, 21 Jun 1999 18:28:59 +0200 (CEST) (envelope-from andreas) Date: Mon, 21 Jun 1999 18:28:59 +0200 From: Andreas Klemm To: "Kenneth D. Merry" Cc: Andreas Klemm , scsi@FreeBSD.ORG Subject: Re: missing time and date in SCSI syslog messages Message-ID: <19990621182858.B53772@titan.klemm.gtn.com> References: <19990621084718.A38627@titan.klemm.gtn.com> <199906210710.BAA26020@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <199906210710.BAA26020@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Jun 21, 1999 at 01:10:17AM -0600 X-Operating-System: FreeBSD 3.2-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jun 21, 1999 at 01:10:17AM -0600, Kenneth D. Merry wrote: > 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. Oh, you're right ... sorry. I was confused about xconsole. I always thought xconsole is syslog output .... Since there are other services, that write out a date, even when displaying things on xconsole window (i4b for example). > > (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. Hmm, didn't touch the system for about weeks ... Two weeks ago the system got additional ram ... > It doesn't necessarily look like a drive problem, but more like a SCSI bus > problem. Hmm... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Latest song from our band: http://www.freebsd.org/~andreas/mp3/schaukel.mp3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message