Date: Fri, 03 Jan 2003 14:56:38 From: R P <rpsbsd@cox.net> To: freebsd-stable@freebsd.org Subject: Re: SCSI parity error; software- or hardware-problem? Message-ID: <3.0.5.32.20030103145638.0093e470@pop.west.cox.net>
next in thread | raw e-mail | index | archive | help
References: 20021124193031.GA18148@nvg.ntnu.no On Nov 24, 2002 in freebsd-stable, taliesin@nvg.ntnu.no wrote: >Then these turned up today: > >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x56) SCSIRATE(0x93) >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8a) SCSIRATE(0x93) >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8a) SCSIRATE(0x93) >(da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 8f df 22 0 0 70 0 >(da0:ahc0:0:0:0): ABORTED COMMAND asc:48,0 >(da0:ahc0:0:0:0): Initiator detected error message received >(da1:ahc0:0:1:0): parity error detected in Data-in phase. SEQADDR(0x8b) SCSIRATE(0x93) >etc. I'm having the same problem since adding a second hard drive to the 68-pin LVD/SE cable on an Adaptec 29160 on Dec. 20th. At this point, I believe it to be a software problem. The machine has two PPro 200 cpus, 384MB ram, Linksys lne100tx NIC, generic PCI USB card, Elsa Synergy II-32 PCI video card, Adaptec 1510 ISA SCSI controller (for a scanner) and SoundBlaster Vibra16 ISA card. There are two drives on the LVD/SE cable and neither is terminated as the cable is terminated. There is a SCSI CDRW on the 50-pin SE connector and a 9.2GB drive on the 68-pin SE connector. Both are terminated. Many months before, 4.0 was installed on the 18Gb drive and upgraded to 4.4. When I tried 4.4 from the HD, after adding the second LVD drive, parity errors over-ran the screen and the machine automatically rebooted. Trying the 4.0 CD produced the same parity errors and a stall. Removing _all_ drives and cables but drive 0, the 18GB drive containing the earlier FreeBSD didn't work. There are now no circumstances that allow FreeBSD to install on that drive. Booting the 4.7 CD didn't work, but allowed getting debug output. All unnecessary cards were removed from the machine, leaving just the Adaptec and video card in hopes that something would improve, but it didn't. The Adaptec 29160 has the latest BIOS, 3.1, but this issue started with BIOS V 2.57.2. Before adding the drive, there was one device per cable. 4.0 and 4.4 ran fine from the 18GB SCSI 160 drive. Here's the debug output (hand copied on another machine, please excuse typos) from vtty2 when 4.7R CD was booted to install on the new drive. There was nothing interesting from the generic kernel DMESG, it was so much to copy and I couldn't get it all: DEBUG: ioctl(3, TIOCCONS, NULL) = 0 (success) DEBUG: Loading module if_wi.ko (Lucent WaveLAN/IEEE 8082.11 PCMCIA card) (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x6f) SCSIRATE (0xc2) CRC Value Mismatch (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8d) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): DEBUG: Loading module cd9660.ko (ISO 9660 Filesystem) cd0 at ahc0 bus 0 target 6 lun 0 cd0: <HP CD-Writer+ 9600 1.0a> Removable CD-ROM SCSI-4 device cd0: 10.000MB\s transfers (10.000MHZ. offset 15) cd0: Attempt to query device size failed: NOT READY, (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8e) SCSIRATE (0xc2) CRC Value Mismatch DEBUG: Loading module msdos.ko (MSDOS filesystem) DEBUG: Loading module if_typ.ko (3Com 3cR990 (``Thphoon'') PCI Ethernet) DEBUG: Loading module mlx.ko (Mylex DAC960 family RAID) DEBUG: Loading module amr.ko (AMI MegaRAID) DEBUG: Loading module twe.ko (3Ware Escalade RAID) DEBUG: Loading module mly.ko Mylex AcceleRAID/eXtremeRAID) DEBUG: Loading module if_an.ko (Aironet 4500/4800 8092.11 PCMCIA/ISA/PCI card) DEBUG: Can't open PC-card controller /dev/card0. (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x71) SCSIRATE (0xc2) CRC Value Mismatch (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8d) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8e) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x71) SCSIRATE (0xc2) CRC Value Mismatch (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8d) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8d) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x6f) SCSIRATE (0xc2) CRC Value Mismatch (da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8d) SCSIRATE (0xc2) CRC Value Mismatch (da0:ahc0:0:0:0): got CAM status 0x50 (da0:ahc0:0:0:0): fatal error, failed to attach to device (da0:ahc0:0:0:0): lost device (da0:ahc0:0:0:0): removing device entry (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): da2 at ahc0 bus 0 target 2 lun 0 da2: <FUJITSU MAN3367MP 0108> Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHZ, offset 127, 16 bit) da2: Attempt to query device size failed: ABORTED COMMAND, (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x71) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): (da2:ahc0:0:2:0): parity error detected in Data-in phase. SEQADDR(0x71) SCSIRATE (0xc2) CRC Value Mismatch (da2:ahc0:0:2:0): . CDB: 25 0 0 0 0 0 0 0 0 0 (da2:ahc0:0:2:0): ABORTED COMMAND asc:48,0 (da2:ahc0:0:2:0): DEBUG: Add mapping for /dev/cuaa0 to sl0 DEBUG: Add mapping for /dev/cuaa1 to sl0 DEBUG: Unable to open disk cd0DEBUG: Unable to open disk da2 At this point, only the 9.1GB drive was available to 4.7 with no free space on it Everything works with MSDOS, Windows NT, and 2000 using supplied drivers from Adaptec and no drive parity or other drive errors were detected. Any help or constructive ideas are appreciated. Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20030103145638.0093e470>