Date: Fri, 8 Sep 2000 17:03:54 -0300 (ADT) From: The Hermit Hacker <scrappy@hub.org> To: Matthew Jacob <mjacob@feral.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive or bad termination? Message-ID: <Pine.BSF.4.21.0009081656160.493-100000@thelab.hub.org> In-Reply-To: <Pine.LNX.4.21.0009081002150.15477-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Okay, more on this (hadn't thought about cabling, thanks, will look at
that on Monday) ...
First off, this drive used to be the root drive of the system for the past
year or so, running Solaris7/x86, with no problems. We recently removed a
drive out off that bus, moved the root drive to da2 and installed a new
9gig as root drive, with FreeBSD ...
I seem to be able to very easily recreate the bug ... the machine is used
as a news server, using INN and its cyclic buffers ... on da3, if I use dd
to create a new buffer, after a period of time (2+gig into creating
~3.9gig buffer, those 6 lines will pop onto the screen. The build will
eventually finish, with no more errors being produced ... during "normal
operation", I don't see those errors popping up ... on Monday, I'll try to
build on da4 and see if I can force the errors to happen again, but am
wondering if maybe that makes a difference? Still sound like cabling, or
maybe something else?
On Fri, 8 Sep 2000, Matthew Jacob wrote:
>
> Bad cable maybe?
>
>
> >
> > Just looking for an opinion on this error message:
> >
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): WRITE(06). CDB: a 14 89 0 80 0
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): ABORTED COMMAND info:148900 asc:47,0
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3
> > Sep 8 06:37:33 poseidon /kernel: (da2:dpt0:0:2:0): SCSI parity error field replaceable unit: 3
> >
> > bad drive sort of error messsage, or bad scsi termination? or really not able
> > to determine from the error? :(
> >
> > thanks ...
> >
> >
> > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> > Systems Administrator @ hub.org
> > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-scsi" in the body of the message
> >
>
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009081656160.493-100000>