From owner-freebsd-scsi Sun Jul 9 23:46:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Post-Office.UH.EDU (Post-Office.UH.EDU [129.7.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 942F637B671 for ; Sun, 9 Jul 2000 23:46:27 -0700 (PDT) (envelope-from zdenko@CS.UH.EDU) Received: from CONVERSION-DAEMON by Post-Office.UH.EDU (PMDF V5.2-32 #40812) id <0FXG00O01YTCY1@Post-Office.UH.EDU> for freebsd-scsi@freebsd.org; Mon, 10 Jul 2000 01:46:24 -0500 (CDT) Received: from CS.UH.EDU (zeus.cs.uh.edu [129.7.192.1]) by Post-Office.UH.EDU (PMDF V5.2-32 #40812) with SMTP id <0FXG00J7MYTCO0@Post-Office.UH.EDU> for freebsd-scsi@freebsd.org; Mon, 10 Jul 2000 01:46:24 -0500 (CDT) Received: from heracles.CS.UH.EDU by CS.UH.EDU (COSC/UH-zeus) id AA16551; Mon, 10 Jul 2000 01:44:56 -0500 (CDT) Received: by heracles.CS.UH.EDU (4.1/UH-heracles) id AA11520; Mon, 10 Jul 2000 01:44:47 -0500 (CDT) Date: Mon, 10 Jul 2000 01:44:56 -0500 (CDT) From: Zdenko Tomasic Subject: sym: scsi parity errors for cdrom To: freebsd-scsi@freebsd.org Reply-To: zdenko@CS.UH.EDU Message-id: <10007100644.AA16551@CS.UH.EDU> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It was suggested I redirect my inquiry from -stable to -scsi, so there it is: I see unrecovered SCSI parity errors under both 3.4- and 4.0 FBSD. I checked cables, connectors and termination and all seem to be okay. There are other devices on this scsi bus but only cdrom shows errors. It looks like my UltraPlex PX 32CS is at fault. Audio works fine (even while scsi errors abound). Can anyone interpret the following errors codes from sym driver? tnx. Jul 8 20:21:27 localhost /kernel: sym0: SCSI parity error detected: SCR1=1 DBC11000000 SBCL=29 Jul 8 20:21:27 localhost /kernel: sym0: SCSI parity error detected: SCR1=1 DBC11000000 SBCL=29 Jul 8 20:21:27 localhost /kernel: sym0: unexpected disconnect Jul 8 20:21:27 localhost /kernel: sym0: unexpected disconnect Jul 8 20:21:27 localhost /kernel: (pass0:sym0:0:0:0): unrecovered SCSI parity rror. Jul 8 20:21:27 localhost /kernel: (pass0:sym0:0:0:0): unrecovered SCSI parity rror. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 10 12:56:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 918C237B850 for ; Mon, 10 Jul 2000 12:56:00 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-1-152.club-internet.fr (Guyancourt-1-152.club-internet.fr [195.36.205.152]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA18759; Mon, 10 Jul 2000 21:55:50 +0200 (MET DST) Date: Mon, 10 Jul 2000 21:34:50 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Zdenko Tomasic Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym: scsi parity errors for cdrom In-Reply-To: <10007100644.AA16551@CS.UH.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 10 Jul 2000, Zdenko Tomasic wrote: > It was suggested I redirect my inquiry from -stable to -scsi, so there > it is: >=20 > I see unrecovered SCSI parity errors under both 3.4- and 4.0 FBSD. > I checked cables, connectors and termination and all seem to be okay. > There are other devices on this scsi bus but only cdrom shows errors. > It looks like my UltraPlex PX 32CS is at fault. Audio works fine (even > while scsi errors abound). Can anyone interpret the following > errors codes from sym driver? > tnx. >=20 > Jul 8 20:21:27 localhost /kernel: sym0: SCSI parity error detected: > SCR1=3D1 host status =3D HS_BUSY (quite normal) > DBC=3D11000000 SCRIPTS currently executing a MOVE FROM ? WHEN DATA_IN=20 > SBCL=3D29 Phase=3DDATA_IN, ATN asserted, SEL deasserted, BSY assert= ed=20 At this step, the driver should have tried to send a INITIATOR DETECTED ERROR Message to the device. > Jul 8 20:21:27 localhost /kernel: sym0: unexpected disconnect For some reason the device disconnect the BUS when this was not expected. > Jul 8 20:21:27 localhost /kernel: (pass0:sym0:0:0:0): unrecovered SCSI p= arity rror. The driver told you that it decided to return a CAM_UNCOR_PARITY. Note that if both the UNEXPECTED DISCONNECTION condition and the UNCORRECTED PARITY error condition are present when the SCSI I/O finishes, the driver elects to return the UNCORRECTED PARITY status to CAM. Excepted for the SCSI parity error and the fact the driver and the device didn't agree on recoverying from it 'on the fly', all seems quite normal to me here. ;-) Anyway, CAM should have retried the SCSI/IO that failed and, if your system is still alive after the problem, the retry should have recovered from the parity error. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 10 14:11: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (64-51-67-2.client.dsl.net [64.51.67.2]) by hub.freebsd.org (Postfix) with ESMTP id EA96C37B5B4; Mon, 10 Jul 2000 14:10:56 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id RAA44612; Mon, 10 Jul 2000 17:11:08 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <396A3C00.DA8C7D51@falcon.niksun.com> Date: Mon, 10 Jul 2000 21:11:28 +0000 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-smp@freebsd.org, freebsd-scsi@freebsd.org Subject: Adaptec 3950 and SMP... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, i have a L440GX+ intel server motherboard running 2 P3. The motherboard has an on-board scsi controller aic7896 (ahc0, ahc1). Additionally i have added an "Adaptec 3950 scsi controller" board(ahc2, ahc3). When i boot an uniprocessor kernel everything works fine. However when i boot a multiprocessor kernel everything seems ok till the boot mesg shows "Waiting for scsi devices to settle". But after waiting for some time the boot msg shows a lot of SCB timeouts and hangs. IF i remove the additional scsi controller things start working again (except that the system complains about unable to mount root partition...but it boots). Since things work in a UP kernel i think it is an SMP related problem. The mptable output is :-# Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs dmesg on the UP kernel shows ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.12.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc2: rev 0x00 int a irq 10 on pci0.13.0 ahc2: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc3: rev 0x00 int a irq 10 on pci0.13.1 ahc3: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs Irq 10 is not used by anything else. What can be the problem ?? thanx in advance joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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 Mon Jul 10 16:16:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from arjun.niksun.com (64-51-67-2.client.dsl.net [64.51.67.2]) by hub.freebsd.org (Postfix) with ESMTP id 76A4937B607; Mon, 10 Jul 2000 16:16:48 -0700 (PDT) (envelope-from joy@niksun.com) Received: from falcon.niksun.com (falcon.niksun.com [10.0.0.167]) by arjun.niksun.com (8.9.3/8.9.3) with ESMTP id TAA46308; Mon, 10 Jul 2000 19:17:01 -0400 (EDT) (envelope-from joy@falcon.niksun.com) Message-ID: <396A5981.19AD6985@falcon.niksun.com> Date: Mon, 10 Jul 2000 23:17:21 +0000 From: Joy Ganguly X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers , freebsd-smp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Adaptec 3950 and SMP... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi all, i have a L440GX+ intel server motherboard running 2 P3. The motherboard has an on-board scsi controller aic7896 (ahc0, ahc1). Additionally i have added an "Adaptec 3950 scsi controller" board(ahc2, ahc3). When i boot an uniprocessor kernel everything works fine. However when i boot a multiprocessor kernel everything seems ok till the boot mesg shows "Waiting for scsi devices to settle". But after waiting for some time the boot msg shows a lot of SCB timeouts and hangs. IF i remove the additional scsi controller things start working again (except that the system complains about unable to mount root partition...but it boots). Since things work in a UP kernel i think it is an SMP related problem. The mptable output is :-# Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs dmesg on the UP kernel shows ahc0: rev 0x00 int a irq 11 on pci0.12.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.12.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc2: rev 0x00 int a irq 10 on pci0.13.0 ahc2: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc3: rev 0x00 int a irq 10 on pci0.13.1 ahc3: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs Irq 10 is not used by anything else. What can be the problem ?? thanx in advance joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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 Mon Jul 10 23:35:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Post-Office.UH.EDU (Post-Office.UH.EDU [129.7.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 3C12F37B6F3 for ; Mon, 10 Jul 2000 23:35:21 -0700 (PDT) (envelope-from zdenko@CS.UH.EDU) Received: from CONVERSION-DAEMON by Post-Office.UH.EDU (PMDF V5.2-32 #40812) id <0FXI00J01SYU75@Post-Office.UH.EDU> for freebsd-scsi@FreeBSD.ORG; Tue, 11 Jul 2000 01:35:19 -0500 (CDT) Received: from CS.UH.EDU (zeus.cs.uh.edu [129.7.192.1]) by Post-Office.UH.EDU (PMDF V5.2-32 #40812) with SMTP id <0FXI00GE1SYU3N@Post-Office.UH.EDU>; Tue, 11 Jul 2000 01:35:18 -0500 (CDT) Received: from heracles.CS.UH.EDU by CS.UH.EDU (COSC/UH-zeus) id AA01765; Tue, 11 Jul 2000 01:33:50 -0500 (CDT) Received: by heracles.CS.UH.EDU (4.1/UH-heracles) id AA12846; Tue, 11 Jul 2000 01:33:41 -0500 (CDT) Date: Tue, 11 Jul 2000 01:33:50 -0500 (CDT) From: Zdenko Tomasic Subject: Re: sym: scsi parity errors for cdrom In-reply-to: To: groudier@club-internet.fr Cc: freebsd-scsi@FreeBSD.ORG Reply-To: zdenko@CS.UH.EDU Message-id: <10007110633.AA01765@CS.UH.EDU> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the explanation. Unfortunately, uncorrected parity errors do appear quite uncorrectable as they keep being repeated as expected.:-) Eventually, I guess, CAM turns the incorrigible device off which is quite normal :-) I guess I will be looking for the (ATAPI?) substitute which is quite normal and expected :-(( ZT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 11 4:53:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp.www-service.de (smtp.www-service.de [212.77.161.16]) by hub.freebsd.org (Postfix) with SMTP id CD4A437B9BB for ; Tue, 11 Jul 2000 04:53:50 -0700 (PDT) (envelope-from thz@lennartz-electronic.de) Received: (qmail 11918 invoked from network); 11 Jul 2000 11:53:47 -0000 Received: from p3e9e134a.dip.t-dialin.net (HELO fw.tue.le) (62.158.19.74) by smtp.www-service.de with SMTP; 11 Jul 2000 11:53:47 -0000 Received: from mezcal.tue.le (mezcal.tue.le [192.168.201.20]) by fw.tue.le (8.8.8/8.8.8) with ESMTP id NAA02072; Tue, 11 Jul 2000 13:52:02 +0200 (CEST) (envelope-from thz@mezcal.tue.le) Received: (from thz@localhost) by mezcal.tue.le (8.9.3/8.9.3) id NAA04255; Tue, 11 Jul 2000 13:52:02 +0200 (CEST) (envelope-from thz) Date: Tue, 11 Jul 2000 13:46:28 +0200 From: Thomas Zenker To: scsi@FreeBSD.ORG Cc: mjacob@feral.com Subject: Re: Invalidating pack weirdness Message-ID: <20000711134628.A4128@.tue.le> References: <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Mailer: Mutt 1.0.1i X-Mailer: Mutt 1.0.1i In-Reply-To: ; from mjacob@feral.com on Sat, Jul 08, 2000 at 01:03:11AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 08, 2000 at 01:03:11AM -0700, Matthew Jacob wrote: > > > 1) driver problem > > 2) hardware misconfig > > 3) hardware problem > > #3 is most likely . You have to get details about the actual device for us to > guess about #2's likelihood. > > The driver should work harder at avoiding this situation. > See also following PRs: PR misc/18786 PR i386/19226 PR kern/19579 I myself get the Adaptec aic7892 / Seagate combination only working by turning off tagged queuing. The same drives work with aic7890! -- Thomas Zenker c/o Lennartz electronic GmbH Bismarckstrasse 136, D-72072 Tuebingen, Germany Phone: +49-(0)7071-93550 Email: thz@lennartz-electronic.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 11 13: 7: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id D540E37B8AC for ; Tue, 11 Jul 2000 13:07:02 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from Guyancourt-1-192.club-internet.fr (Guyancourt-1-192.club-internet.fr [195.36.205.192]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA02493; Tue, 11 Jul 2000 22:06:40 +0200 (MET DST) Date: Tue, 11 Jul 2000 21:45:44 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Zdenko Tomasic Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sym: scsi parity errors for cdrom In-Reply-To: <10007110633.AA01765@CS.UH.EDU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 11 Jul 2000, Zdenko Tomasic wrote: > Thanks for the explanation. Unfortunately, uncorrected parity errors > do appear quite uncorrectable as they keep being repeated as expected.:-) SCSI parity errors are the consequence of something being not good on your SCSI BUS. Btw, repeating the command is a perfectly safe recovery procedure and may-be more safe than trying to recover on the fly by telling the device about the error and it sending again the data without disconnecting the BUS. The UNEXPECTED DISCONNECT could perfectly be the decision of the device to force recovery by repeating the whole command. > Eventually, I guess, CAM turns the incorrigible device off which is=20 > quite normal :-) I will check, but I donnot think CAM does throw away a device on SCSI parity errors. It does so on SELECTION timeout since it means that the device is no longer responding. If you didn't lose any data and your system didn't crash with the bonus of the driver having given you information about the SCSI BUS problem, as reported by controller and device, then the O/S did behave quite well, in my opinion. > I guess I will be looking for the (ATAPI?) substitute which is quite > normal and expected :-(( Facing a broken BUS, the ATAPI device will indeed normally fail. :-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 12 3:16:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (Postfix) with ESMTP id B645537B6FA for ; Wed, 12 Jul 2000 03:16:35 -0700 (PDT) (envelope-from freepix@sirius.com) Received: from jasons-pc.sirius.com (ppp-astk02-099.sirius.net [205.134.247.99]) by mail1.sirius.com (8.9.3/8.9.1) with ESMTP id DAA31352 for ; Wed, 12 Jul 2000 03:12:35 -0700 (PDT) Message-Id: <4.3.2.7.2.20000712025610.01e54650@mail.sirius.com> X-Sender: freepix@mail.sirius.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 12 Jul 2000 02:56:17 -0700 To: scsi@freebsd.org From: Jason Scott Subject: SCSI Drive - Device not configured Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have my system setup with two IDE drives, and now two SCSI drives. The first SCSI drive works great, but upon adding the second one, and installing it (from The Complete FreeBSD book) I can access the drive, and even have a few small sites on it without a problem. But when I tried to copy a 2 gigabyte directory to it, I received the following errors, and then the drive could not be read: cp: /homes2/ps/data/avs/hotpnl/secret/ppp6/tn_ppp638eb_jpg.jpg: Device not configured cp: /homes2/ps/data/avs/hotpnl/secret/ppp6/ppp6.html: Device not configured cp: /homes2/ps/data/avs/hotpnl/secret/ppp9: Device not configured The files being copied are on a drive called homes, and this new drive is called homes2. I didn't add the drive to the kernel, but I didn't see anything in the book about doing that, could there be some type of problem with the drive? After I reboot the system it needs to be fsck'd to mount this drive, and the 'messages' file contains this after reboot: Jul 6 22:16:43 www /kernel: (da1:ahc0:0:1:0): Invalidating pack Jul 6 22:17:14 www last message repeated 10 times Jul 6 22:18:04 www last message repeated 15 times Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 12 3:40:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131]) by hub.freebsd.org (Postfix) with ESMTP id 76C1837C071; Wed, 12 Jul 2000 03:40:09 -0700 (PDT) (envelope-from freepix@sirius.com) Received: from jasons-pc.sirius.com (ppp-astk02-099.sirius.net [205.134.247.99]) by mail1.sirius.com (8.9.3/8.9.1) with ESMTP id DAA37651; Wed, 12 Jul 2000 03:36:10 -0700 (PDT) Message-Id: <4.3.2.7.2.20000712031132.01e552b0@mail.sirius.com> X-Sender: freepix@mail.sirius.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 12 Jul 2000 03:18:24 -0700 To: msmith@freebsd.org From: Jason Scott Subject: RE: Invalidating pack weirdness Cc: scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Alfred had posted this message for me... At this point, I wondered what I could do to add more storage to my system. I don't know what a 'U160' disk is. If that is a particular type of SCSI disk, I would like to stay away from it so that I can add another drive right away. Our primary drive only has 2% disk space left and we have to add a new disk within 2 days. If you have any brand/model recommendations I would appreciate it. Thank You If this is a new SCSI disk and an Adaptec controller - yes, it's a known problem. At this point in time, I don't think you can buy a U160 disk from anyone that will work with an Adaptec controller and our driver. Justin is at work on the problem at the moment. > Someone just tossed me an email saying they're getting the dreaded > "Invalidating pack" kernel messages followed by: > > "Device not configured" > > errors from 'cp' > > Doing a search of the lists turns up a bunch of people having these > problems, but no solution/fix posted. > > Does anyone know if this is most likely coming from: > > 1) driver problem > 2) hardware misconfig > 3) hardware problem > > thanks, > -Alfred > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 12 8:58:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 939CC37BF27 for ; Wed, 12 Jul 2000 08:58:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA05193; Wed, 12 Jul 2000 08:58:37 -0700 Date: Wed, 12 Jul 2000 08:58:39 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Scott Cc: scsi@FreeBSD.ORG Subject: Re: SCSI Drive - Device not configured In-Reply-To: <4.3.2.7.2.20000712025610.01e54650@mail.sirius.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 you have to say what SCSI h/w you're using. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 12 8:59:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7236037BEFE; Wed, 12 Jul 2000 08:59:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id IAA05213; Wed, 12 Jul 2000 08:59:34 -0700 Date: Wed, 12 Jul 2000 08:59:36 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Scott Cc: msmith@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: RE: Invalidating pack weirdness In-Reply-To: <4.3.2.7.2.20000712031132.01e552b0@mail.sirius.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 > > At this point in time, I don't think you can buy a U160 disk from anyone > that will work with an Adaptec controller and our driver. Justin is at > work on the problem at the moment. > Both the LSI-Logic (53c1010) and the Qlogic 12160 cards support U160. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message