From owner-freebsd-scsi Mon Apr 2 17:49:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from post.webmailer.de (natmail2.webmailer.de [192.67.198.65]) by hub.freebsd.org (Postfix) with ESMTP id 0576B37B71F for ; Mon, 2 Apr 2001 17:49:42 -0700 (PDT) (envelope-from wk@xtweb.de) Received: from balu ([195.27.60.246]) by post.webmailer.de (8.9.3/8.8.7) with SMTP id CAA15687 for ; Tue, 3 Apr 2001 02:49:40 +0200 (MET DST) From: "Wolfram Kraushaar" To: Subject: Need help with an error message Date: Tue, 3 Apr 2001 02:50:35 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0000_01C0BBE8.DB6ACBF0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C0BBE8.DB6ACBF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello, can you help me with the message at the bottom? Right now I'm running the GENERIC 4.2 STABLE kernel. Does it mean the disk is too slow or faulty? When I ran this disk on Linux (before switching to FreeBSD) there were no messages like this. The disk (da7) is placed in a concatenated vinum-plex. When I launch vinum it tells me the drive is up (without problems) Attached is compete dmesg printout. ahc1: port 0xe800-0xe8ff mem 0xea001000-0xea001fff irq 10 at device 10.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs ... da7 at ahc1 bus 0 target 5 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da7: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) ... This message appears in the kernel log after some hours running without problems: << (da7:ahc1:0:5:0): SCB 0x3 - timed out while idle, SEQADDR == 0x4 STACK == 0x1, 0x189, 0x159, 0x0 SXFRCTL0 == 0x80 SCB count = 20 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 1:3 QOUTFIFO entries: Sequencer Free SCB List: 3 0 2 4 5 6 7 8 9 10 11 12 13 14 15 Pending list: 3 Kernel Free SCB list: 7 14 6 8 5 9 15 16 17 18 19 0 1 2 13 12 11 10 sg[0] - Addr 0x6008800 : Length 1024 (da7:ahc1:0:5:0): Queuing a BDR SCB (da7:ahc1:0:5:0): Bus Device Reset Message Sent (da7:ahc1:0:5:0): no longer in timeout, status = 34b ahc1: Bus Device Reset on A:5. 1 SCBs aborted >> The following Message appears after running for 3 days: > (da7:ahc1:0:5:0): SCB 0x66 - timed out while idle, SEQADDR == 0x4 > STACK == 0x1, 0x189, 0x159, 0x181 > SXFRCTL0 == 0x80 > SCB count = 230 > QINFIFO entries: > Waiting Queue entries: > Disconnected Queue entries: 7:102 > QOUTFIFO entries: > Sequencer Free SCB List: 4 11 14 10 12 5 8 3 13 15 0 6 1 9 2 > Pending list: 102 > Kernel Free SCB list: 204 74 84 147 68 43 193 49 15 153 217 82 114 59 143 145 31 177 195 165 72 19 97 155 174 182 1 69 70 216 215 181 134 183 80 50 142 208 56 48 3 136 38 98 139 229 211 196 57 63 179 52 93 128 127 11 91 156 168 218 124 191 46 112 150 58 23 160 149 209 125 138 214 10 54 206 199 202 5 100 154 163 85 213 119 158 44 39 42 210 205 164 133 51 137 99 190 64 7 86 115 37 17 66 175 67 135 116 162 192 34 201 120 45 71 169 167 33 121 178 41 94 219 8 62 9 110 203 185 92 151 141 140 157 166 198 129 122 197 30 212 36 144 29 55 180 111 20 25 28 35 194 146 26 176 75 87 4 184 130 96 47 113 123 126 2 159 65 95 73 118 83 152 161 117 200 53 81 88 207 186 187 188 189 170 171 172 173 27 18 89 148 40 6 22 103 131 132 32 0 24 104 13 16 14 90 105 106 107 108 109 21 12 61 76 77 78 79 60 228 227 226 225 224 223 222 221 220 > sg[0] - Addr 0xa87c00 : Length 1024 > (da7:ahc1:0:5:0): Queuing a BDR SCB > (da7:ahc1:0:5:0): Bus Device Reset Message Sent > (da7:ahc1:0:5:0): no longer in timeout, status = 34b > ahc1: Bus Device Reset on A:5. 1 SCBs aborted Thx in advance for any help, Wolfram Kraushaar ------=_NextPart_000_0000_01C0BBE8.DB6ACBF0 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.txt" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 4.2-RELEASE #0: Mon Nov 20 13:02:55 GMT 2000 jkh@bento.FreeBSD.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (399.32-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x652 Stepping =3D 2 = Features=3D0x183f9ff real memory =3D 268435456 (262144K bytes) config> di pcic0 config> di lnc0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> q avail memory =3D 257085440 (251060K bytes) Preloaded elf kernel "kernel" at 0xc0436000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc043609c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on = pci0 pci1: on pcib1 pci1: at 0.0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 = on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xe000-0xe01f at = device 7.2 on pci0 uhci0: Invalid irq 255 uhci0: Please switch on USB support and switch PNP-OS to 'No' in BIOS device_probe_and_attach: uhci0 attach returned 6 chip1: port 0x5000-0x500f at = device 7.3 on pci0 ahc0: port 0xe400-0xe4ff mem = 0xea000000-0xea000fff irq 11 at device 9.0 on pci0 aic7880: Single Channel A, SCSI Id=3D7, 16/255 SCBs ahc1: port 0xe800-0xe8ff mem = 0xea001000-0xea001fff irq 10 at device 10.0 on pci0 aic7870: Wide Channel A, SCSI Id=3D7, 16/255 SCBs xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xec00-0xec3f irq 5 at = device 11.0 on pci0 xl0: Ethernet address: 00:60:97:b4:47:e5 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ad0: 6204MB [13446/15/63] at ata0-master UDMA33 ad1: 9671MB [19650/16/63] at ata0-slave UDMA33 ad2: 9671MB [19650/16/63] at ata1-master UDMA33 ad3: 9671MB [19650/16/63] at ata1-slave UDMA33 Waiting 15 seconds for SCSI devices to settle sa0 at ahc1 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 8) Mounting root from ufs:/dev/ad0s1a da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da4: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 8.064MB/s transfers (8.064MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing = Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da5 at ahc1 bus 0 target 3 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da5: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da2: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) da6 at ahc1 bus 0 target 4 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da6: 1001MB (2050860 512 byte sectors: 64H 32S/T 1001C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing = Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da7 at ahc1 bus 0 target 5 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da7: 2050MB (4199760 512 byte sectors: 255H 63S/T 261C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing = Enabled da3: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) vinum: loaded vinum: reading configuration from /dev/da7s1e vinum: updating configuration from /dev/da6s1e vinum: updating configuration from /dev/da5s1e vinum: updating configuration from /dev/da4s1e vinum: updating configuration from /dev/da3s1e vinum: updating configuration from /dev/da2s1e vinum: updating configuration from /dev/da1s1e vinum: updating configuration from /dev/da0s1e vinum: updating configuration from /dev/ad3s2e vinum: updating configuration from /dev/ad3s1e vinum: updating configuration from /dev/ad2s2e vinum: updating configuration from /dev/ad2s1e vinum: updating configuration from /dev/ad1s2e vinum: updating configuration from /dev/ad1s1e (da7:ahc1:0:5:0): SCB 0x3 - timed out while idle, SEQADDR =3D=3D 0x4 STACK =3D=3D 0x1, 0x189, 0x159, 0x0 SXFRCTL0 =3D=3D 0x80 SCB count =3D 20 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 1:3 QOUTFIFO entries: Sequencer Free SCB List: 3 0 2 4 5 6 7 8 9 10 11 12 13 14 15 Pending list: 3 Kernel Free SCB list: 7 14 6 8 5 9 15 16 17 18 19 0 1 2 13 12 11 10 sg[0] - Addr 0x6008800 : Length 1024 (da7:ahc1:0:5:0): Queuing a BDR SCB (da7:ahc1:0:5:0): Bus Device Reset Message Sent (da7:ahc1:0:5:0): no longer in timeout, status =3D 34b ahc1: Bus Device Reset on A:5. 1 SCBs aborted ------=_NextPart_000_0000_01C0BBE8.DB6ACBF0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 4 11:49:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 2255F37B71F; Wed, 4 Apr 2001 11:48:56 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f34Imln72065; Wed, 4 Apr 2001 11:48:47 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3ACB6C90.750FF100@vpop.net> Date: Wed, 04 Apr 2001 11:48:48 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org, scsi@freebsd.org Subject: Possibly SCSI-related hang Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One of our boxes has been hanging, apparently in connection with some SCSI parity errors which appear in the logs before the hangs. This machine is running -stable from around March 4, with two disks da1 and da2 comprising a vinum mirror. The parity errors all pertain to da2, which is on its own controller: ahc0: port 0x1400-0x14ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x1800-0x18ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0x1080-0x10bf mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 10 at device 14.0 on pci0 fxp0: Ethernet address 00:a0:c9:fb:26:e6 ahc2: port 0x2000-0x20ff mem 0xf4103000-0xf4103fff irq 5 at device 16.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs ... sa0 at ahc2 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) ch0 at ahc2 bus 0 target 1 lun 0 ch0: Removable Changer SCSI-2 device ch0: 3.300MB/s transfers ch0: 8 slots, 1 drive, 1 picker, 0 portals da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) When the box hangs, we are able to break into the debugger; below are two traces I got while the machine was hung (trace, continue, trace): db> trace siointr1(c164d400,ce08df64,c020ef46,c164d400,ce080010) at siointr1+0xf2 siointr(c164d400,ce080010,1887,2,2) at siointr+0xb Xfastintr4(c163f400,81) at Xfastintr4+0x16 ahc_platform_intr(c163f400,6c0820,4faf8,bfbffdc0,bfbfc78c) at ahc_platform_intr+ 0x11e intr_mux(c0a35960,0,2f,2f,2f) at intr_mux+0x1d Xresume11() at Xresume11+0x2b --- interrupt, eip = 0x2828836f, esp = 0xce08dfe0, ebp = 0xbfbfc78c --- db> trace siointr1(c164d400,ce08df18,c020ef46,c164d400,10) at siointr1+0xf2 siointr(c164d400,10,183e,27,0) at siointr+0xb Xfastintr4(c163f400,ce08df48) at Xfastintr4+0x16 ahc_handle_seqint(c163f400,81) at ahc_handle_seqint+0x19 ahc_platform_intr(c163f400,6c0820,4faf8,bfbffdc0,bfbfc78c) at ahc_platform_intr+ 0x11e intr_mux(c0a35960,0,2f,2f,2f) at intr_mux+0x1d Xresume11() at Xresume11+0x2b --- interrupt, eip = 0x2828836f, esp = 0xce08dfe0, ebp = 0xbfbfc78c Are these traces consistent with the recently fixed vinum deadlock? Below are the errors that appeared in the logs before the hangs: Apr 2 09:06:39 ring /kernel: (da2:ahc1:0:2:0): WRITE(06). CDB: a 5 1 88 10 0 Apr 2 09:06:39 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:06:39 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:06:41 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 2 4b 3 b8 0 0 10 0 Apr 2 09:06:41 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:06:41 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:06:42 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 bd 1 a8 0 0 10 0 Apr 2 09:06:42 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:06:42 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:07:10 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 c2 1 88 0 0 10 0 Apr 2 09:07:10 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:07:10 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:07:11 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 1 28 1 e8 0 0 10 0 Apr 2 09:07:11 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:07:11 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:07:13 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 bd 3b 38 0 0 80 0 Apr 2 09:07:13 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:07:13 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:07:24 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 bd 3c 88 0 0 80 0 Apr 2 09:07:24 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:07:24 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:50:03 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 38 1 88 0 0 10 0 Apr 2 09:50:03 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 09:50:03 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 09:56:04 ring /kernel: (da2:ahc1:0:2:0): parity error detected in Data-in phase. SEQADDR(0x8a) SCSI Apr 2 09:56:05 ring /kernel: (da2:ahc1:0:2:0): READ(10). CDB: 28 0 0 bc 4a 82 0 0 4 0 Apr 2 09:56:05 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:48,0 Apr 2 09:56:05 ring /kernel: (da2:ahc1:0:2:0): Initiator detected error message received Apr 2 10:01:04 ring /kernel: (da2:ahc1:0:2:0): parity error detected in Data-in phase. SEQADDR(0x89) SCSI Apr 2 10:01:04 ring /kernel: (da2:ahc1:0:2:0): READ(10). CDB: 28 0 2 e8 3e 48 0 0 80 0 Apr 2 10:01:04 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:48,0 Apr 2 10:01:04 ring /kernel: (da2:ahc1:0:2:0): Initiator detected error message received Apr 2 12:19:40 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 3 89 1 d8 0 0 10 0 Apr 2 12:19:40 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 12:19:40 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 12:25:03 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 2 ce 1 e8 0 0 10 0 Apr 2 12:25:03 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 12:25:03 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error Apr 2 12:27:34 ring /kernel: (da2:ahc1:0:2:0): WRITE(10). CDB: 2a 0 0 bd 3e 48 0 0 80 0 Apr 2 12:27:34 ring /kernel: (da2:ahc1:0:2:0): ABORTED COMMAND asc:47,0 Apr 2 12:27:34 ring /kernel: (da2:ahc1:0:2:0): SCSI parity error At this point I told vinum not to use da2 any more (vinum stop -f fatmirror.p1.s0); predictably, since then no parity errors have occurred and the kernel has not hung. I ran "dd bs=65536 if=/dev/da2e of=/dev/null" which completed successfully, reading all 36G with no errors. Questions: 1. Should the kernel hang because of parity errors? 2. What is causing the hang: a bug in the SCSI code, or vinum, or ...? 3. Do parity errors indicate SCSI bus problems? 4. Might these parity errors indicate that da2 is bad? 5. Is it possible for a bad SCSI device to affect other devices on the bus? About eight months ago da2 used to be on the same controller with da0 and da1, but da0 and da1 started having strange problems ("swap_pager: indefinite wait buffer" on da0 where swap is, and "timed out while idle" on da1). Installing a new LVD cable didn't help, but moving da2 to its own bus did (but now we get parity errors on da2's bus). Thanks for any help you can give. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 5 14:41:36 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C4B037B423 for ; Thu, 5 Apr 2001 14:41:24 -0700 (PDT) (envelope-from mauri@inspiral.net) Received: from inspiral.net (tigris-isdn-99.uninet.ee [194.204.61.99]) by ns.uninet.ee (Postfix) with ESMTP id B55B42584E for ; Thu, 5 Apr 2001 23:41:16 +0200 (EET) Message-ID: <3ACCD7F4.767DA2A9@inspiral.net> Date: Thu, 05 Apr 2001 23:39:16 +0300 From: Lauri Laupmaa X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: IOI-4203U and FreeBSD driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I'm having problems with this controller... it has freebsd driver source on its cd-rom, but it has some old instructions which result in 'obsolete flag' when I run config KERNEL. when i include in sys/conf/files: pci/i91u.c optional iha device-driver What should I put there ? btw. Is there any particular problem or smth. that this driver is not part of standard freebsd kernel source ? btw2. The box has sticker which says: 'Best FreeBSD PCI SCSI controller' or smth like that. -- L. [When buying and selling are controlled by legislation, the first things to be bought and sold are legislators.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 6 3:23:38 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D060637B509 for ; Fri, 6 Apr 2001 03:23:34 -0700 (PDT) (envelope-from mauri@inspiral.net) Received: from inspiral.net (tigris-isdn-188.uninet.ee [194.204.61.188]) by ns.uninet.ee (Postfix) with ESMTP id A5F4A25823 for ; Fri, 6 Apr 2001 12:23:30 +0200 (EET) Message-ID: <3ACD8AA1.477B3709@inspiral.net> Date: Fri, 06 Apr 2001 12:21:37 +0300 From: Lauri Laupmaa X-Mailer: Mozilla 4.75 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Re: IOI-4203U and FreeBSD driver References: <3ACCD7F4.767DA2A9@inspiral.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Lauri Laupmaa wrote: > 'obsolete flag' when I run config KERNEL. > when i include in sys/conf/files: > pci/i91u.c optional iha device-driver I got it working...: iha0: port 0xde00-0xdeff mem 0xeffff000-0xeff fffff irq 10 at device 16.0 on pci0 iha0: Reset SCSI Bus ... iha0: driver is using old-style compatibility shims -- L. [When buying and selling are controlled by legislation, the first things to be bought and sold are legislators.] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 6 6:22: 2 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by hub.freebsd.org (Postfix) with ESMTP id 508DC37B42C for ; Fri, 6 Apr 2001 06:21:59 -0700 (PDT) (envelope-from kenm@icarz.com) Received: from newken (dhcp113.icarz.com [207.99.22.113]) by hercules.icarz.com (8.10.1/8.10.1) with SMTP id f36DLq219162 for ; Fri, 6 Apr 2001 09:21:52 -0400 (EDT) Message-ID: <009f01c0be9c$8d5e0a60$711663cf@icarz.com> From: "Ken Menzel" To: Subject: can't use sa0 (tape) on -stable-rc1 fresh install Date: Fri, 6 Apr 2001 09:21:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am re-posting this on the 'freebsd-scsi' as I got no answers on freebsd-stable. (I also changed the subject line to be more clear). sa0 doesn't work! Thought I would try out my new FreeBSD release. I just installed FreeBSD on two new Dell servers here. (The same as all my other servers). But the tapes drives won't work! Any ideas on what I did wrong? I have three other servers running FreeBSD-stable with the same DELL hardware (2400) and tape drives that work fine (Installed on FBSD4.2) . Here is the error: janeway# mt status mt: /dev/nsa0: Device not configured janeway# However dmesg says differently: Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) pass1 at ahc0 bus 0 target 6 lun 1 pass1: Removable Changer SCSI-2 device pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) pass4 at asr0 bus 0 target 6 lun 0 pass4: Fixed Processor SCSI-2 device output of uname FreeBSD janeway.icarz.com 4.3-RC FreeBSD 4.3-RC #0: Thu Apr 5 12:24:51 EDT 2001 sysadm@janeway.icarz.com:/usr/obj/usr/src/sys/GENERIC i386 I tried rebuilding the kernel and sh MAKEDEV all, and a cvsup to today. What else should I do? Any suggestions appreciated! Thanks! ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 6 6:38:44 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 68F6137B443 for ; Fri, 6 Apr 2001 06:38:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id GAA13104; Fri, 6 Apr 2001 06:38:29 -0700 Date: Fri, 6 Apr 2001 06:38:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ken Menzel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: can't use sa0 (tape) on -stable-rc1 fresh install In-Reply-To: <009f01c0be9c$8d5e0a60$711663cf@icarz.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Have you a tape inserted? Build a CAMDEBUG kernel and do camcontrol debug -Ic 0:6:0 do the 'mt stat', with a tape inserted, and send me the output. -matt On Fri, 6 Apr 2001, Ken Menzel wrote: > I am re-posting this on the 'freebsd-scsi' as I got no answers on > freebsd-stable. (I also changed the subject line to be more clear). > sa0 doesn't work! > > Thought I would try out my new FreeBSD release. I just installed > FreeBSD on two new Dell servers here. (The same as all my other > servers). But the tapes drives won't work! Any ideas on what I did > wrong? I have three other servers running FreeBSD-stable with the same > DELL hardware (2400) and tape drives that work fine (Installed on > FBSD4.2) > . Here is the error: > janeway# mt status > mt: /dev/nsa0: Device not configured > janeway# > > However dmesg says differently: > > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 6 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > pass1 at ahc0 bus 0 target 6 lun 1 > pass1: Removable Changer SCSI-2 device > pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > pass4 at asr0 bus 0 target 6 lun 0 > pass4: Fixed Processor SCSI-2 device > > > output of uname > > FreeBSD janeway.icarz.com 4.3-RC FreeBSD 4.3-RC #0: Thu Apr 5 > 12:24:51 EDT 2001 > sysadm@janeway.icarz.com:/usr/obj/usr/src/sys/GENERIC i386 > > I tried rebuilding the kernel and sh MAKEDEV all, and a cvsup to > today. > > What else should I do? Any suggestions appreciated! > > Thanks! > > ----------------------------------------------------- > Ken Menzel ICQ# 9325188 > www.icarz.com kenm@icarz.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 6 7:36:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from hercules.icarz.com (ns1.icarz.com [207.99.22.7]) by hub.freebsd.org (Postfix) with ESMTP id 5EF3C37B43E for ; Fri, 6 Apr 2001 07:36:04 -0700 (PDT) (envelope-from kenm@icarz.com) Received: from newken (dhcp113.icarz.com [207.99.22.113]) by hercules.icarz.com (8.10.1/8.10.1) with SMTP id f36EZv221268; Fri, 6 Apr 2001 10:35:58 -0400 (EDT) Message-ID: <016601c0bea6$e79dc920$711663cf@icarz.com> From: "Ken Menzel" To: Cc: References: Subject: Re: can't use sa0 (tape) on -stable-rc1 fresh install Date: Fri, 6 Apr 2001 10:36:01 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks Matthew, we just figured out that the problem really was "the device is not configured", well sort of. All the other tape drive in the past from Dell have arrived pre-programmed to autoload the tape when a cartridge is inserted. These two did not arrive that way! The message I would have expected was a media error, not a "Device not configured" error. Really sent me down the wrong path! Should I look into this more? I really want to use these tape drives with the 'ch' driver and get Amanda installed and working! Confused, but wanting to help in NJ, BTW is it a good idea/OK to run with CAMDEBUG options on my test servers anyway? Do you still want that output to see why it said "Device not configured" when mt status should have given a status, and dump should have told me to mount the volume! Could it be a bug in the drive? Thanks Ken ----------------------------------------------------- Ken Menzel ICQ# 9325188 www.icarz.com kenm@icarz.com ----- Original Message ----- From: "Matthew Jacob" To: "Ken Menzel" Cc: Sent: Friday, April 06, 2001 9:38 AM Subject: Re: can't use sa0 (tape) on -stable-rc1 fresh install > > Have you a tape inserted? > > Build a CAMDEBUG kernel and do > > camcontrol debug -Ic 0:6:0 > > do the 'mt stat', with a tape inserted, and send me the output. > > -matt > > > On Fri, 6 Apr 2001, Ken Menzel wrote: > > > I am re-posting this on the 'freebsd-scsi' as I got no answers on > > freebsd-stable. (I also changed the subject line to be more clear). > > sa0 doesn't work! > > > > Thought I would try out my new FreeBSD release. I just installed > > FreeBSD on two new Dell servers here. (The same as all my other > > servers). But the tapes drives won't work! Any ideas on what I did > > wrong? I have three other servers running FreeBSD-stable with the same > > DELL hardware (2400) and tape drives that work fine (Installed on > > FBSD4.2) > > . Here is the error: > > janeway# mt status > > mt: /dev/nsa0: Device not configured > > janeway# > > > > However dmesg says differently: > > > > Waiting 15 seconds for SCSI devices to settle > > sa0 at ahc0 bus 0 target 6 lun 0 > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > > pass1 at ahc0 bus 0 target 6 lun 1 > > pass1: Removable Changer SCSI-2 device > > pass1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > > pass4 at asr0 bus 0 target 6 lun 0 > > pass4: Fixed Processor SCSI-2 device > > > > > > output of uname > > > > FreeBSD janeway.icarz.com 4.3-RC FreeBSD 4.3-RC #0: Thu Apr 5 > > 12:24:51 EDT 2001 > > sysadm@janeway.icarz.com:/usr/obj/usr/src/sys/GENERIC i386 > > > > I tried rebuilding the kernel and sh MAKEDEV all, and a cvsup to > > today. > > > > What else should I do? Any suggestions appreciated! > > > > Thanks! > > > > ----------------------------------------------------- > > Ken Menzel ICQ# 9325188 > > www.icarz.com kenm@icarz.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 6 11:56:42 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9F1ED37B424 for ; Fri, 6 Apr 2001 11:56:39 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA14352; Fri, 6 Apr 2001 11:56:40 -0700 Date: Fri, 6 Apr 2001 11:56:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Ken Menzel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: can't use sa0 (tape) on -stable-rc1 fresh install In-Reply-To: <016601c0bea6$e79dc920$711663cf@icarz.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 6 Apr 2001, Ken Menzel wrote: > Thanks Matthew, we just figured out that the problem really was "the > device is not configured", well sort of. All the other tape drive in > the past from Dell have arrived pre-programmed to autoload the tape > when a cartridge is inserted. These two did not arrive that way! The > message I would have expected was a media error, not a "Device not > configured" error. Really sent me down the wrong path! Should I look > into this more? I really want to use these tape drives with the 'ch' > driver and get Amanda installed and working! > > Confused, but wanting to help in NJ, BTW is it a good idea/OK to run > with CAMDEBUG options on my test servers anyway? Nope, but it should be a FAQ that CAMDEBUG like this is needed to diagnose tape problems. > > Do you still want that output to see why it said "Device not > configured" when mt status should have given a status, and dump > should have told me to mount the volume! Could it be a bug in the > drive? > Bug in the spec for tapes && Unix, not the driver. (translation: I'd change it, but the conservatives within freebsd would hang me from the nearest tree, instead of searching for the highest as they usually do). -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 7 10:57:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 9EEC137B42C for ; Sat, 7 Apr 2001 10:57:35 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 22D9217D3F; Sat, 7 Apr 2001 19:57:34 +0200 (CEST) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.11.1/8.11.1) id f37HugM01329 for freebsd-scsi@freebsd.org; Sat, 7 Apr 2001 19:56:42 +0200 (CEST) (envelope-from schweikh) Date: Sat, 7 Apr 2001 19:56:42 +0200 From: Jens Schweikhardt To: freebsd-scsi@freebsd.org Subject: Trouble with timeouts after installing an U160LVD Message-ID: <20010407195642.A1309@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello, world\n I bought me a brand new shiny IBM DDYS-T18350N Ultra160LVD drive. My host adapter at this time does not support U160 SCSI, it's an ASUS P2L97S with on-board SCSI provided by an Adaptec AIC 7880. My understanding however is that the U160 drive will adapt to the slower bus (I may well be doing something silly here...) , which it apparently does (snippet from dmesg): da2 at ahc0 bus 0 target 12 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 17422MB (35680750 512 byte sectors: 255H 63S/T 2221C) da0 at ahc0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Unfortunately, with the new drive installed, I seem to have problems with another drive in the system, the IBM DCAS-34330. After a short time after boot (~1 min) I get the following: (da0:ahc0:0:2:0): SCB 0x1a - timed out in Data-out phase, SEQADDR == 0x77 STACK == 0x93, 0x18c, 0x15c, 0x0 SXFRCTL0 == 0xa0 SCB count = 30 QINFIFO entries: 25 10 29 22 27 16 3 24 4 1 7 6 5 14 15 2 18 28 Waiting Queue entries: Disconnected Queue entries: QOUTFIFO entries: Sequencer Free SCB List: 15 9 5 4 6 2 8 1 10 7 13 14 11 0 12 Pending list: 28 18 2 15 14 5 6 7 1 4 24 3 16 27 22 29 10 25 26 Kernel Free SCB list: 9 13 12 11 23 17 0 19 21 20 Untagged Q(2): 26 sg[0] - Addr 0x1b9a000 : Length 4096 sg[1] - Addr 0x1bdb000 : Length 3072 (da0:ahc0:0:2:0): BDR message in message buffer (da0:ahc0:0:2:0): SCB 0x1a - timed out in Data-out phase, SEQADDR == 0x76 STACK == 0x93, 0x18c, 0x15c, 0x0 SXFRCTL0 == 0xa0 SCB count = 30 QINFIFO entries: 25 10 29 22 27 16 3 24 4 1 7 6 5 14 15 2 18 28 Waiting Queue entries: Disconnected Queue entries: QOUTFIFO entries: Sequencer Free SCB List: 15 9 5 4 6 2 8 1 10 7 13 14 11 0 12 Pending list: 28 18 2 15 14 5 6 7 1 4 24 3 16 27 22 29 10 25 26 Kernel Free SCB list: 9 13 12 11 23 17 0 19 21 20 Untagged Q(2): 26 sg[0] - Addr 0x1b9a000 : Length 4096 sg[1] - Addr 0x1bdb000 : Length 3072 (da0:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 19 SCBs aborted My cabling is aic7880(50pin)--cd1--cd0--da0(Terminated) aic7880(68pin)--da1--da2--ActiveTerminationPlug and the board manual says that aic7880(68pin) is always terminated. I've played around with the "Force Single Ended" jumper of the da2, but to no avail. Even with only one device on each bus I get timeouts about every minute on both cables, e.g. aic7880(50pin)--cd0(Terminated) aic7880(68pin)--DDYS:ID9--ActiveTerminationPlug When installing FreeBSD from a cd in cd0 every now and then: (da0:ahc0:0:9:0): SCB 0x43 - timed out in Data-In Phase, SEQADDR == 0x14 (da0:ahc0:0:9:0): BDR Message in Message Buffer (da0:ahc0:0:9:0): SCB 0x43 - timed out in Data-In Phase, SEQADDR == 0x15 (da0:ahc0:0:9:0): no longer in timeout, status = 34b Can anyone please clue me in what I am doing wrong or what else I can try to get all devices to work? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 7 11:19: 4 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 9DB2737B43C for ; Sat, 7 Apr 2001 11:18:57 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f37IIas88838; Sat, 7 Apr 2001 12:18:42 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104071818.f37IIas88838@aslan.scsiguy.com> To: Jens Schweikhardt Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Trouble with timeouts after installing an U160LVD In-Reply-To: Your message of "Sat, 07 Apr 2001 19:56:42 +0200." <20010407195642.A1309@schweikhardt.net> Date: Sat, 07 Apr 2001 12:18:36 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >hello, world\n > >I bought me a brand new shiny IBM DDYS-T18350N Ultra160LVD drive. My >host adapter at this time does not support U160 SCSI, it's an ASUS P2L97S with >on-board SCSI provided by an Adaptec AIC 7880. My understanding however >is that the U160 drive will adapt to the slower bus (I may well be doing >something silly here...) , which it apparently does (snippet from >dmesg): What version of FreeBSD are you using? If you boot verbose, what messages are printed while probing the SCSI controller? It may be that the driver is not properly enabling termination. It could also be that one of your cables is marginal. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message