From owner-freebsd-questions Tue May 25 12:22:29 1999 Delivered-To: freebsd-questions@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 8D54A151AB; Tue, 25 May 1999 12:22:17 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2190.bossig.com [208.26.242.190]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id MAA03578; Tue, 25 May 1999 12:15:56 -0700 (PDT) Message-ID: <374AF6E8.9CD7300C@3-cities.com> Date: Tue, 25 May 1999 12:15:52 -0700 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: Donald Burr , FreeBSD Questions , FreeBSD SCSI Subject: Re: Help! - "parity error during data-in phase" when using CD-Rdrv References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. > > > SCSI: Adaptec AHA-2940AU PCI SCSI controller > > SCSI disk 0: Quantum Viking 4.5 GB > > SCSI disk 1: Quantum Viking 4.5 GB > > SCSI disk 2: IBM 0662 S12 1.0 GB > > SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive > > SCSI Scanner 5: UMAX Astra 1200S > > SCSI DAT drive 6: Wangtek 6200-HS > > (Yes, the bus is properly terminated and all that, I checked.) > > Did you check it again? There are a few people I know that have been having problems with Adaptec AHA-2940AU/UW controller's unless power is supplied to the terminator. Using bus power created problems for those systems. I have also had a bad power connector on an internal power supply. It is usually the one on the end of the daisy chain. If you have a free power connector you might replace the connector you are using to power the CDROM with a free one. If you don't, add a Y cable and then use the new connector for power. I have also hooked a scsi cable incorrectly. Nothing on the scsi controller worked when I did that. You can't hook a scsi cable up to a CDROM off one pin like you can some devices. Nothing worked when you do that either. It seems like you end up with a ground on a data line or power. Kent > > > 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? > > > The drive does not work under Windows either. > > Hm, perhaps the entire drive is bad. > > > It seems to me, then, that I somehow managed to damage the drive while > > moving it between cases. But I thought I had better post this anyway, in > > case someone else out there has any ideas as to what I'm doing wrong, or > > how I might go about fixing this. > > Cable on upside down? > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message