Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 May 1999 14:22:16 -0600 (MDT)
From:      "Kenneth D. Merry" <ken@plutotech.com>
To:        grog@lemis.com (Greg Lehey)
Cc:        dwhite@resnet.uoregon.edu (Doug White), dburr@pobox.com (Donald Burr), freebsd-questions@FreeBSD.ORG (FreeBSD Questions), freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI)
Subject:   Re: Help! - "parity error during data-in phase" when using CD-R drv
Message-ID:  <199905252022.OAA04678@panzer.plutotech.com>
In-Reply-To: <19990526053742.R95827@freebie.lemis.com> from Greg Lehey at "May 26, 1999 05:37:43 am"

next in thread | previous in thread | raw e-mail | index | archive | help

I think y'all must have all missed this thread on the -scsi list.  Donald
already posted this to -scsi, and Justin suggested that it may be a bent
pin on the connector on the CD-R drive.

That would explain why the other devices work fine, but the CD-R doesn't.

Greg Lehey wrote...
> On Tuesday, 25 May 1999 at 11:03:15 -0700, Doug White wrote:
> > On Sun, 23 May 1999, Donald Burr wrote:
> >
> >> I have suddenly started getting the following types of error messages when
> >> trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable,
> >> cd writer) device.
> >>
> >> May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase.
> >> May 23 03:01:51 control /kernel: SEQADDR == 0x110
> >> May 23 03:01:52 control /kernel: SCSIRATE == 0xf
> >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153
> >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer
> >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153
> >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b
> >> May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted
> >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase.
> >> May 23 03:02:35 control /kernel: SEQADDR == 0x110
> >> May 23 03:02:35 control /kernel: SCSIRATE == 0xf
> >> [...]
> >>
> >> Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE.
> >
> > Hm, this implies that the CDR is busted.  My guess is that it's the
> > cable.
> 
> If it were the cable, the other devices wouldn't work either.  And it
> wouldn't explain why this happened suddenly.

It could be the connector on the CD-R, and not the cable.  Unfortunately
narrow SCSI devices have the pins on the device instead of the cable.  It's
much better, IMO, to have fragile things like pins on the cable, which is
much cheaper to replace.

> >> Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are
> >> working fine.  The ATAPI DVD-ROM drive is also working fine.  It's only
> >> the SCSI CD-recorder that does not work.  It fails when accessing mounted
> >> CD's (doing a 'du' of the CD will bring the error on really quickly), and
> >> also I cannot use tosha to grab audio tracks off of it (same error).  I
> >> don't dare trying to write a CD on it...
> >
> > It may not support those operations.  How old is the CDR?
> 
> If it doesn't support the operation, it would say so.  A parity error
> suggests that there's something wrong with the connection or the
> device.  We've ruled out the connection.

It doesn't rule out the connection, since the cable can be good and the
drive connector can be bad.

Ken
-- 
Kenneth Merry
ken@plutotech.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905252022.OAA04678>