From owner-freebsd-questions Sun May 23 6:15:30 1999 Delivered-To: freebsd-questions@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 9F8A21532D; Sun, 23 May 1999 06:15:20 -0700 (PDT) (envelope-from dburr@pobox.com) Received: from pm0-47.sba1.avtel.net (pm0-47.sba1.avtel.net [207.71.218.47]) by beach.silcom.com (Postfix) with ESMTP id B4B787F7; Sun, 23 May 1999 06:15:17 -0700 (PDT) Date: Sun, 23 May 1999 06:15:15 -0700 (PDT) From: Donald Burr X-Sender: dburr@control.colossus.dynip.com To: FreeBSD Questions Cc: FreeBSD SCSI Subject: Help! - "parity error during data-in phase" when using CD-R drv Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. Before I continue, let me mention my system's configuration. EPoX EP-MVP3G Motherboard (VIA MVP3 chipset) AMD K6-2/300 CPU (100 bus * 3 multiplier) 128 MB PC100 SDRAM DIMM NO IDE HARD DRIVES IDE CD-ROM: Creative Labs PC-DVD Encore Dxr2 (Primary master) 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.) OS: FreeBSD 3.1-RELEASE 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... The drive does not work under Windows either. Here's something interesting: This same hardware configuration (except the motherboard) was, up until a few weeks ago, installed in an AT case with a Tyan Titan Turbo S1571 motherboard, and it worked fine (CD burner and all). However in mid-April I got myself a new ATX motherboard (the EPoX one) and case, and I moved all of my hardware into that. I don't really use the CD-burner that often, so it was only just yesterday (when I wanted to grab some audio tracks from a music CD to burn a "greatest hits" type cd), that I noticed the errors. 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. Thanks in advance for whatever help you may be able to provide. -- Donald Burr | PGP: Your *NEW* WWW HomePage: http://more.at/dburr/ ICQ #16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message