From owner-freebsd-scsi Sun Aug 10 03:42:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA15721 for freebsd-scsi-outgoing; Sun, 10 Aug 1997 03:42:20 -0700 (PDT) Received: from DonaldBurr.DonaldBurr.dyn.ml.org (ppp6229.la.inreach.net [199.107.160.229]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA15714; Sun, 10 Aug 1997 03:42:11 -0700 (PDT) Received: from localhost (dburr@localhost) by DonaldBurr.DonaldBurr.dyn.ml.org (8.8.5/8.8.5) with SMTP id DAA06884; Sun, 10 Aug 1997 03:42:13 -0700 (PDT) X-Authentication-Warning: DonaldBurr.DonaldBurr.dyn.ml.org: dburr owned process doing -bs Date: Sun, 10 Aug 1997 03:42:13 -0700 (PDT) From: Donald Burr X-Sender: dburr@DonaldBurr.DonaldBurr.dyn.ml.org Reply-To: Donald Burr To: FreeBSD Questions cc: FreeBSD SCSI Subject: "El Torrito" (bootable CD-ROM), how to use it? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I understand that the FreeBSD 2.2.2 CD-ROM is a bootable CD-ROM, using "El Torrito" technology. I just purchased a new SCSI adapter for my machine (Adaptec AHA-2940AU PCI UltraSCSI adapter) and I understand that it supports "bootable CD-ROMs" I have tried booting the FreeBSD CD-ROM (after, of course, enabling the "Support for bootable CD-ROMs" in the Adaptec BIOS), but it just hangs after the "system information" screen. I doo see the CD-ROM drive light flashing, however. And I see a message saying something to the effect that my CD-ROM drive is now known as the A: drive. I've tried everything I could think of, including removing all SCSI devices except the CD-ROM, removing all of my expansion cards except for video and the Adaptec, disabling the on-board floppy controller and/or my A: drive, etc. but I get the same results. My SCSI bus is properly terminated, BTW. Can anyone tell me what (if anything) I am doing wrong here? Please e-mail me if possible. Thanks in advance! Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. From owner-freebsd-scsi Sun Aug 10 06:08:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA20146 for freebsd-scsi-outgoing; Sun, 10 Aug 1997 06:08:13 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA20128; Sun, 10 Aug 1997 06:08:03 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA08338; Sun, 10 Aug 1997 15:07:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id OAA02961; Sun, 10 Aug 1997 14:31:23 +0200 (MET DST) Message-ID: <19970810143123.ZM33434@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 14:31:23 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: dburr@POBoxes.com (Donald Burr) Cc: freebsd-questions@FreeBSD.ORG (FreeBSD Questions), freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI) Subject: Re: "El Torrito" (bootable CD-ROM), how to use it? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Donald Burr on Aug 10, 1997 03:42:13 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Donald Burr wrote: > Can anyone tell me what (if anything) I am doing wrong here? Please > e-mail me if possible. Thanks in advance! Complain at Adaptec. That's still in their area if it hangs that early. Btw., i've found BIOS rev 1.23 to be the last stable revision regarding El Torito (even though a number of El Torito features are missing that have supposed to be fixed in 1.25 or higher). So it wouldn't surprise me to see that they've broken more than the extended BIOS int 0x13 support. El Torito is already a large pile of sh*t, but the BIOS vendor imple- mentations of it seem to be even crappier. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun Aug 10 08:37:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26195 for freebsd-scsi-outgoing; Sun, 10 Aug 1997 08:37:39 -0700 (PDT) Received: from thor.i-connect.net (qmailr@thor.i-Connect.Net [206.190.143.254]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA26178 for ; Sun, 10 Aug 1997 08:37:35 -0700 (PDT) Received: (qmail 26720 invoked by uid 4028); 10 Aug 1997 15:37:36 -0000 Message-ID: X-Mailer: XFMail 0.5-alpha [p0] on Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19970810143123.ZM33434@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 08:25:53 -0700 (PDT) From: ron@cts.com To: (Joerg Wunsch) Subject: Re: "El Torrito" (bootable CD-ROM), how to use it? Cc: (J Wunsch) , (Donald Burr) , (FreeBSD Questions) , (FreeBSD SCSI) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Works fine for me. Scared me the 1st time it happened. I was doing an install, had just reset the computer and waiting for the install diskette to be read. Suddenly, I am getting messages about a: being reassigned to cdrom and floppy A: being reassigned to b:,; all too fast to be properly read. Then, to add to my confusion, I found myself in the install program. I took the floppy out and tried again. Worked perfectly. I have an: ahc0 rev 0 int a irq 11 on pci0:13 on an Intel Tuscon board. Sorry I can't complain... Ron McDaniels On 10-Aug-97 j@uriah.heep.sax.de wrote: >>As Donald Burr wrote: > >> Can anyone tell me what (if anything) I am doing wrong here? Please >> e-mail me if possible. Thanks in advance! > >Complain at Adaptec. That's still in their area if it hangs that >early. > >Btw., i've found BIOS rev 1.23 to be the last stable revision >regarding El Torito (even though a number of El Torito features are >missing that have supposed to be fixed in 1.25 or higher). So it >wouldn't surprise me to see that they've broken more than the extended >BIOS int 0x13 support. > >El Torito is already a large pile of sh*t, but the BIOS vendor imple- >mentations of it seem to be even crappier. > >-- >cheers, J"org > >joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE >Never trust an operating system you don't have sources for. ;-) ---------------------------------- E-Mail: ron@cts.com Date: 08/10/97 Time: 08:26:04 This message was sent by XF-Mail ---------------------------------- From owner-freebsd-scsi Sun Aug 10 10:51:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02686 for freebsd-scsi-outgoing; Sun, 10 Aug 1997 10:51:05 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA02681 for ; Sun, 10 Aug 1997 10:50:59 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA11926; Sun, 10 Aug 1997 19:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id TAA04425; Sun, 10 Aug 1997 19:28:48 +0200 (MET DST) Message-ID: <19970810192848.BY05190@uriah.heep.sax.de> Date: Sun, 10 Aug 1997 19:28:48 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: dburr@POBoxes.com (Donald Burr) Subject: Re: "El Torrito" (bootable CD-ROM), how to use it? References: <19970810143123.ZM33434@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from ron@cts.com on Aug 10, 1997 08:25:53 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As ron@cts.com wrote: > tried again. Worked perfectly. I have an: > > ahc0 rev 0 int a irq 11 on pci0:13 That's largely irrelevant. The Adaptec BIOS revision is what matters. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sun Aug 10 19:36:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA02794 for freebsd-scsi-outgoing; Sun, 10 Aug 1997 19:36:46 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA02786 for ; Sun, 10 Aug 1997 19:36:43 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxkJx-0001fv-00; Sun, 10 Aug 1997 19:35:01 -0700 Date: Sun, 10 Aug 1997 19:34:59 -0700 (PDT) From: Tom Samplonius To: scsi@freebsd.org cc: shimon@i-connect.net Subject: DPT problem with new boot.flp Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm having a problem with the new boot.flp from sendero-ppp.i-connect:/crash/. Basically, sysinstall hangs during newfs'ing rsd0s1e. I turned debugging on, and the last line displayed was: DEBUG: Executing command `newfs -b 8192 -f 1024 /mnt/dev/rsd0s1e' I can still switch consoles, so it isn't completely hung, but ^C and CTRL-ALT-DEL do nothing. I used "auto" during the label step, to setup a stock filesystem layout. I'm using this with a PM334UW on PPro 200 motherboard with 5 4GB drives setup as RAID-5 array. Tom From owner-freebsd-scsi Mon Aug 11 01:17:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20764 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 01:17:00 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA20751 for ; Mon, 11 Aug 1997 01:16:56 -0700 (PDT) Received: (qmail 9822 invoked by uid 1000); 11 Aug 1997 08:17:12 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Aug 1997 01:17:12 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: RE: DPT problem with new boot.flp Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Aug-97 you wrote: > > I'm having a problem with the new boot.flp from > sendero-ppp.i-connect:/crash/. Basically, sysinstall hangs during > newfs'ing rsd0s1e. I turned debugging on, and the last line displayed > was: > > DEBUG: Executing command `newfs -b 8192 -f 1024 /mnt/dev/rsd0s1e' > > > I can still switch consoles, so it isn't completely hung, but ^C and > CTRL-ALT-DEL do nothing. > > I used "auto" during the label step, to setup a stock filesystem > layout. > > I'm using this with a PM334UW on PPro 200 motherboard with 5 4GB drives > setup as RAID-5 array. > > Tom Which P6 motherboard? What version of the driver is on that floppy? i have not updated a boot floppy in a long time... Simon From owner-freebsd-scsi Mon Aug 11 08:25:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA09669 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 08:25:04 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA09658 for ; Mon, 11 Aug 1997 08:24:59 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxwJU-00020V-00; Mon, 11 Aug 1997 08:23:20 -0700 Date: Mon, 11 Aug 1997 08:23:19 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: scsi@freebsd.org Subject: RE: DPT problem with new boot.flp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Simon Shapiro wrote: > Hi Tom Samplonius; On 11-Aug-97 you wrote: > > > > I'm having a problem with the new boot.flp from > > sendero-ppp.i-connect:/crash/. Basically, sysinstall hangs during > > newfs'ing rsd0s1e. I turned debugging on, and the last line displayed > > was: > > > > DEBUG: Executing command `newfs -b 8192 -f 1024 /mnt/dev/rsd0s1e' > > > > > > I can still switch consoles, so it isn't completely hung, but ^C and > > CTRL-ALT-DEL do nothing. > > > > I used "auto" during the label step, to setup a stock filesystem > > layout. > > > > I'm using this with a PM334UW on PPro 200 motherboard with 5 4GB drives > > setup as RAID-5 array. > > Which P6 motherboard? What version of the driver is on that floppy? > i have not updated a boot floppy in a long time... It is ASUS P6 motherboard. I don't recall the model, but it one that uses a CPU daughtercard. The DPT driver on the floppy claims to be 1.1.2 Another point, that I'm not sure was clear from my original message, is this sysinstall newfs's partitions backwards, so it completly newsfs'ed rsd0s1f (a 16GB /usr filesystem), then hangs on newfs'ing rsd0s1e (a 30MB /var filesystem). > Simon > > Tom From owner-freebsd-scsi Mon Aug 11 10:06:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16422 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:06:07 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA16408 for ; Mon, 11 Aug 1997 10:05:57 -0700 (PDT) Received: (qmail 15662 invoked by uid 1000); 11 Aug 1997 17:06:12 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Aug 1997 10:06:12 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: RE: DPT problem with new boot.flp Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Aug-97 you wrote: > > On Mon, 11 Aug 1997, Simon Shapiro wrote: > > > Hi Tom Samplonius; On 11-Aug-97 you wrote: > > > > > > I'm having a problem with the new boot.flp from > > > sendero-ppp.i-connect:/crash/. Basically, sysinstall hangs during > > > newfs'ing rsd0s1e. I turned debugging on, and the last line > displayed > > > was: > > > > > > DEBUG: Executing command `newfs -b 8192 -f 1024 /mnt/dev/rsd0s1e' > > > > > > > > > I can still switch consoles, so it isn't completely hung, but ^C > and > > > CTRL-ALT-DEL do nothing. > > > > > > I used "auto" during the label step, to setup a stock filesystem > > > layout. > > > > > > I'm using this with a PM334UW on PPro 200 motherboard with 5 4GB > drives > > > setup as RAID-5 array. > > > > Which P6 motherboard? What version of the driver is on that floppy? > > i have not updated a boot floppy in a long time... > > It is ASUS P6 motherboard. I don't recall the model, but it one that > uses a CPU daughtercard. Try to find out for me. > The DPT driver on the floppy claims to be 1.1.2 Ancient. Get a new boot floppy from sendero-ppp. Should support driver 1.1.10. > > Another point, that I'm not sure was clear from my original message, is > this sysinstall newfs's partitions backwards, so it completly newsfs'ed > rsd0s1f (a 16GB /usr filesystem), then hangs on newfs'ing rsd0s1e (a > 30MB /var filesystem). Older versions of the driver were very sensitive to timing problems on the PCI bus. Newer ones are better and we are still working with DPT to isolate the problem. Anyway, version 1.1.10, wit hthe proper options will handle most motherboards just fine. Simon From owner-freebsd-scsi Mon Aug 11 10:07:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA16546 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:07:40 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA16531 for ; Mon, 11 Aug 1997 10:07:29 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxxud-00024R-00; Mon, 11 Aug 1997 10:05:47 -0700 Date: Mon, 11 Aug 1997 10:05:47 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: scsi@freebsd.org Subject: RE: DPT problem with new boot.flp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Tom Samplonius wrote: > On Mon, 11 Aug 1997, Simon Shapiro wrote: > > > Hi Tom Samplonius; On 11-Aug-97 you wrote: > > > > > > I'm having a problem with the new boot.flp from > > > sendero-ppp.i-connect:/crash/. Basically, sysinstall hangs during > > > newfs'ing rsd0s1e. I turned debugging on, and the last line displayed > > > was: > > > > > > DEBUG: Executing command `newfs -b 8192 -f 1024 /mnt/dev/rsd0s1e' > > > > > > > > > I can still switch consoles, so it isn't completely hung, but ^C and > > > CTRL-ALT-DEL do nothing. > > > > > > I used "auto" during the label step, to setup a stock filesystem > > > layout. > > > > > > I'm using this with a PM334UW on PPro 200 motherboard with 5 4GB drives > > > setup as RAID-5 array. > > > > Which P6 motherboard? What version of the driver is on that floppy? > > i have not updated a boot floppy in a long time... > > It is ASUS P6 motherboard. I don't recall the model, but it one that > uses a CPU daughtercard. > > The DPT driver on the floppy claims to be 1.1.2 > > Another point, that I'm not sure was clear from my original message, is > this sysinstall newfs's partitions backwards, so it completly newsfs'ed > rsd0s1f (a 16GB /usr filesystem), then hangs on newfs'ing rsd0s1e (a > 30MB /var filesystem). > > > Simon > > > > > > Tom It seems that the problem is within sysinstall. I specified a 200MB /usr and left the rest of the array unallocated, and sysinstall newfs'ed it fine. Perhaps sysinstall is generating a bogus label when you specify large filesystems. Are people actually using sysinstall from the boot floppy to set up a system with a DPT? Tom From owner-freebsd-scsi Mon Aug 11 10:41:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA18580 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:41:59 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA18574 for ; Mon, 11 Aug 1997 10:41:56 -0700 (PDT) Received: (qmail 16219 invoked by uid 1000); 11 Aug 1997 17:42:12 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Aug 1997 10:42:12 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: RE: DPT problem with new boot.flp Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Aug-97 you wrote: ... > It seems that the problem is within sysinstall. I specified a 200MB > /usr and left the rest of the array unallocated, and sysinstall newfs'ed > it fine. With which DPT version? > Perhaps sysinstall is generating a bogus label when you specify large > filesystems. Larger than 4GB, I run into problems, at times, regardless of SCSI interface. > Are people actually using sysinstall from the boot floppy to set up > a system with a DPT? I do. Routinely :-) There are two possibilities for the problem: a. Sysinstall does not understand well enough things which are too big. b. Newfs issues a very dense burst of disk WRITE operations to the raw device. This can cause, on certain motherboards, invalid PCI bus transfers. If you use the sys/conf/i386/DPT config file as template to build a kernel, this kernel will either resist, or report, or cope with this problem, or all of the above. The cost is in performance. Not terrible, but some cost. Simon From owner-freebsd-scsi Mon Aug 11 10:50:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA19063 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:50:08 -0700 (PDT) Received: from ecsl.cs.sunysb.edu (sequoia.cs.sunysb.edu [130.245.14.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA19053 for ; Mon, 11 Aug 1997 10:50:03 -0700 (PDT) Received: (from lclam@localhost) by ecsl.cs.sunysb.edu (8.6.12/8.6.9) id NAA22893 for freebsd-scsi@freebsd.org; Mon, 11 Aug 1997 13:47:16 -0400 From: Lap Chung Lam Message-Id: <199708111747.NAA22893@ecsl.cs.sunysb.edu> Subject: Ultra SCSI (SCSI-3) To: freebsd-scsi@freebsd.org Date: Mon, 11 Aug 1997 13:47:16 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Everybody Is any Ultra-SCSI (SCSI-3) controller supported by freeBSD? If so, where can I obtain the supported driver for the controller? Thanks... Lap From owner-freebsd-scsi Mon Aug 11 10:51:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA19147 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:51:02 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA19139 for ; Mon, 11 Aug 1997 10:50:58 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0wxyan-000269-00; Mon, 11 Aug 1997 10:49:21 -0700 Date: Mon, 11 Aug 1997 10:49:21 -0700 (PDT) From: Tom Samplonius To: Simon Shapiro cc: scsi@freebsd.org Subject: RE: DPT problem with new boot.flp In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 11 Aug 1997, Simon Shapiro wrote: > > > Which P6 motherboard? What version of the driver is on that floppy? > > > i have not updated a boot floppy in a long time... > > > > It is ASUS P6 motherboard. I don't recall the model, but it one that > > uses a CPU daughtercard. > > Try to find out for me. It is ASUS P/I-P65UP5 (motherboard) + C-P6ND (CPU daughtercard). Tom From owner-freebsd-scsi Mon Aug 11 11:10:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA20166 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 11:10:46 -0700 (PDT) Received: from ns.feral.com (root@feral.mauswerks.net [204.152.96.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA20159 for ; Mon, 11 Aug 1997 11:10:44 -0700 (PDT) Received: from feral.feral.com.feral.COM (feral [192.67.166.5]) by ns.feral.com (8.8.6/8.8.6) with SMTP id LAA04221; Mon, 11 Aug 1997 11:05:52 -0700 Date: Mon, 11 Aug 1997 11:05:52 -0700 From: Matthew Jacob Message-Id: <199708111805.LAA04221@ns.feral.com> To: freebsd-scsi@FreeBSD.ORG, lclam@ecsl.cs.sunysb.edu Subject: Re: Ultra SCSI (SCSI-3) reply-to: mjacob@feral.com Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The adaptec controllers do Ultra SCSI. They're supported. From owner-freebsd-scsi Mon Aug 11 11:56:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA23013 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 11:56:58 -0700 (PDT) Received: from mail.ican.net ([204.92.55.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23008 for ; Mon, 11 Aug 1997 11:56:56 -0700 (PDT) Received: from oddjob.ican.net (oddjob.ican.net [204.92.55.7]) by mail.ican.net (8.8.6/8.8.6) with ESMTP id OAA05486; Mon, 11 Aug 1997 14:56:46 -0400 (EDT) Received: (from josh@localhost) by oddjob.ican.net (8.8.6/8.8.6) id OAA25692; Mon, 11 Aug 1997 14:56:49 -0400 (EDT) Message-ID: <19970811145649.12131@ican.net> Date: Mon, 11 Aug 1997 14:56:49 -0400 From: Josh Tiefenbach To: Simon Shapiro Cc: scsi@freebsd.org Subject: Re: `problem' with dpt driver v1.2.0 References: <19970808215105.63789@ican.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Simon Shapiro on Sat, Aug 09, 1997 at 02:43:51AM -0700 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Version 1.2 is not published. See the copyright message. Actually, > version 1.2 does not exist yet. Whups. Sorry. That's what you get when you try installing a box at 3 in the morning :) > bzero(dpt, sizeof(dpt_softc_t); Added, and it appears to be working beautifully. Thanks josh -- Josh Tiefenbach - Systems Engineer - ACC TelEnterprises - josh@ican.net From owner-freebsd-scsi Mon Aug 11 14:02:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA29649 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 14:02:22 -0700 (PDT) Received: from duncan.nac.net (qmailr@duncan.nac.net [207.99.2.9]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA29644 for ; Mon, 11 Aug 1997 14:02:15 -0700 (PDT) Received: (qmail 17555 invoked from network); 11 Aug 1997 21:11:02 -0000 Received: from unknown (HELO who) (unknown) by unknown with SMTP; 11 Aug 1997 21:11:02 -0000 Message-Id: <3.0.32.19970811165511.00e53d00@207.99.43.1> X-Sender: alex@207.99.43.1 X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 11 Aug 1997 17:00:01 -0400 To: Lap Chung Lam , freebsd-scsi@FreeBSD.ORG From: Alex Rubenstein Subject: Re: Ultra SCSI (SCSI-3) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Ultra Scsi != SCSI 3. Ultra is usually ultra-wide-scsi-ii. And, yes, adaptec 2940 UW, Bustec... At 01:47 PM 8/11/97 -0400, Lap Chung Lam wrote: >Hi, Everybody > > Is any Ultra-SCSI (SCSI-3) controller supported by freeBSD? If so, >where can I obtain the supported driver for the controller? > > Thanks... > > >Lap > --- "Don't go with a spineless ISP; we have more backbone." Alex Rubenstein -- alex@nac.net -- KC2BUO -- www.nac.net net @ccess corporation, 201-983-0725 -- 201-983-0725 From owner-freebsd-scsi Mon Aug 11 19:21:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA17626 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 19:21:09 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA17615 for ; Mon, 11 Aug 1997 19:20:51 -0700 (PDT) Received: from gurney.reilly.home (d30.syd2.zeta.org.au [203.26.11.30]) by godzilla.zeta.org.au (8.8.5/8.6.9) with ESMTP id MAA06237 for ; Tue, 12 Aug 1997 12:20:21 +1000 Received: (from andrew@localhost) by gurney.reilly.home (8.8.5/8.8.5) id MAA00314; Tue, 12 Aug 1997 12:19:44 +1000 (EST) Date: Tue, 12 Aug 1997 12:19:44 +1000 (EST) From: Andrew Reilly Message-Id: <199708120219.MAA00314@gurney.reilly.home> To: scsi@freebsd.org Subject: Newfs on Fujitsu R640 (2k sector media) Cc: andrew@gurney.reilly.home Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I have a Fujitsu M2513A magneto optical disk drive, and I've been using it quite happily with R230 media (230M, 512-byte sectors) for a while, because I was not confident that my pre-release 2.2 FreeBSD would support non-512-byte sectors. I have since upgraded to 2.2.2, and bought myself some R640 disks (640M, 2048-byte sectors), and lo: it doesn't work. Here's the skinny: This is what the boot probe says: Aug 8 09:09:21 gurney /kernel: (ahc0:6:0): "FUJITSU M2513A 1300" type 7 removab le SCSI 2 Aug 8 09:09:22 gurney /kernel: od0(ahc0:6:0): Optical 606MB (310352 2048 byte s ectors) Aug 8 09:09:22 gurney /kernel: od0(ahc0:6:0): with approximate 151 cyls, 64 hea For reference, here's what an earlier boot with an R230 disk in the drive looks like: Aug 7 10:25:48 gurney /kernel.vm86: (ahc0:6:0): "FUJITSU M2513A 1300" type 7 re movable SCSI 2 Aug 7 10:25:48 gurney /kernel.vm86: od0(ahc0:6:0): Optical 217MB (446325 512 by te sectors) Aug 7 10:25:48 gurney /kernel.vm86: od0(ahc0:6:0): with approximate 217 cyls, 6 4 heads, and 32 sectors/track On a side issue (I hope), I tried a few different things after the upgrade, including enabling the "Spindle automatic stop mode" on the drive, and setting the "Device type mode for INQUIRY command" to MO, and using the od driver, instead of the sd driver. I don't know what the difference is (I was hoping for an eject on unmount...) but now I get these messages occasionally: This one every time I mount one of the R230 disks I had formatted under the pre-release 2.2 FreeBSD: Aug 7 14:29:43 gurney /kernel: od0: invalid primary partition table: no magic This looks like a spin-down thing. Note at the end that I re-tried the mount, and it just worked: Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , retries:2 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , retries:1 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , FAILURE Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , retries:2 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , retries:1 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): NOT READY asc:4,0 Aug 8 13:24:00 gurney /kernel: od0(ahc0:6:0): Logical unit not ready, cause no t reportable Aug 8 13:24:00 gurney /kernel: , FAILURE Aug 8 13:24:17 gurney /kernel: od0: invalid primary partition table: no magic This one caused a hang that I had to press the reset button to get out of: Aug 7 14:30:14 gurney /kernel: od0(ahc0:6:0): SCB 0x0 - timed out while idle, L ASTPHASE == 0x1, SCSISIGI == 0x0 Aug 7 14:30:14 gurney /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 7 14:30:14 gurney /kernel: od0(ahc0:6:0): Queueing an Abort SCB Aug 7 14:30:14 gurney /kernel: od0(ahc0:6:0): Abort Message Sent Aug 7 14:30:14 gurney /kernel: od0(ahc0:6:0): SCB 0 - Abort Completed. Aug 7 14:30:14 gurney /kernel: od0(ahc0:6:0): no longer in timeout Aug 7 14:30:22 gurney /kernel: ahc0:A:6: no active SCB for reconnecting target - issuing BUS DEVICE RESET Aug 7 14:30:22 gurney /kernel: SAVED_TCL == 0x60 ARG_1 == 0x0 SEQADDR == 0x10d Aug 7 14:30:22 gurney /kernel: ahc0: Bus Device Reset delivered. 1 SCBs aborted Aug 7 14:30:22 gurney /kernel: ahc0: Bus Device Reset delivered. 1 SCBs aborted OK, those are unpleasant, but I figure I can get rid of them if I care to by preventing the drive from spinning down. What's bugging me at the moment is that I don't seem to be able to disklabel or newfs one of the R640 disks. I'm using this disktab entry, which I built out of the numbers reported at boot time, but it's essentially the same as the one that you get with disklabel -w -r auto: fuj640|R640|Fujitsu R640 media Meg 3.5inch Magneto-Optical:\ :ty=removeable:dt=SCSI:rm#3600:\ :se#2048:nt#64:ns#32:nc#151:sc#2048:su#310352:\ :pa#310352:oa#0:ba#16384:fa#2048:ta=4.2BSD:\ :pc#310352:oc#0: (Auto leavs ba and fa 0, which I guess causes newfs to pick sensible defaults?) # disklabel -e od0 disklabel: ioctl DIOCGDINFO: Invalid argument Here's a question: where do I find a description of DIOCGDINFO to figure out what this means? # disklabel -r -w od0 R640 # disklabel od0 disklabel: ioctl DIOCGDINFO: Invalid argument # disklabel -r od0 # /dev/rod0c: type: SCSI disk: fuj640 label: flags: bytes/sector: 2048 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 151 sectors/unit: 310352 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize bps/cpg] a: 310352 0 4.2BSD 2048 16384 0 # (Cyl. 0 - 151*) c: 310352 0 unused 0 0 # (Cyl. 0 - 151*) OK, that looks like it worked, but then: # newfs od0a newfs: /dev/rod0a: Invalid argument # newfs od0c newfs: ioctl (GDINFO): Invalid argument newfs: /dev/rod0c: can't read disk label; disk type must be specified # newfs -T R640 od0c write error: 310351. Tried 2048, wrote -1. wtfs: Invalid argument So, obviously there's something wrong with reading the disklabel. You can see that I've doctored the error printf() in the wtfs function in mkfs.c, in /usr/src/sbin/newfs, to see what was going on, and it was obviously trying to write a valid block size. Anyone care to offer suggestions? I'm happy to try patches or new things: I want this to work... Thanks in advance, -- Andrew "The steady state of disks is full." -- Ken Thompson From owner-freebsd-scsi Fri Aug 15 11:13:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10322 for freebsd-scsi-outgoing; Fri, 15 Aug 1997 11:13:15 -0700 (PDT) Received: from elvis.mu.org (paul@elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10308 for ; Fri, 15 Aug 1997 11:13:06 -0700 (PDT) Received: (from paul@localhost) by elvis.mu.org (4.1/4.1) id NAA02838 for freebsd-scsi@freebsd.org; Fri, 15 Aug 1997 13:12:17 -0500 (CDT) From: Paul Saab Message-Id: <199708151812.NAA02838@elvis.mu.org> Subject: what does this mean? To: freebsd-scsi@freebsd.org Date: Fri, 15 Aug 1997 13:12:17 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got this today from a machine which I have never seen this problem before. Could someone please tell me what this means. Thanks. Paul Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Fri Aug 15 00:35:04 CDT 1997 root@elvis.mu.org:/usr/src/sys/compile/ELVIS CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 62590976 (61124K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 10 on pci0:11 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "Quantum XP32150W L912" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2151MB (4406960 512 byte sectors) (ahc0:1:0): "HP C3725S 6039" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2047MB (4194058 512 byte sectors) vga0 rev 1 int a irq 11 on pci0:15 vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 9 on pci0:19 mii[*mii*] address 00:60:97:9f:9a:4f Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in ep0 not found at 0x300 npx0 flags 0x1 on motherboard npx0: INT 16 interface rfork() call disabled sd0(ahc0:0:0): Target Busy sd0(ahc0:0:0): SCB 0x1 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 sd0(ahc0:0:0): abort message in message buffer sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Clearing bus reset Clearing 'in-reset' flag sd0(ahc0:0:0): no longer in timeout sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 , retries:2 sd0(ahc0:0:0): Target Busy sd0(ahc0:0:0): SCB 0x1 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 sd0(ahc0:0:0): abort message in message buffer sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Clearing bus reset Clearing 'in-reset' flag sd0(ahc0:0:0): no longer in timeout sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 , retries:2 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:2 sd0(ahc0:0:0): Target Busy sd0(ahc0:0:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 sd0(ahc0:0:0): abort message in message buffer sd0(ahc0:0:0): SCB 0x2 - timed out in datain phase, SCSISIGI == 0x54 SEQADDR = 0x49 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Clearing bus reset Clearing 'in-reset' flag sd0(ahc0:0:0): no longer in timeout sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 , retries:3 sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:4 From owner-freebsd-scsi Fri Aug 15 11:16:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10516 for freebsd-scsi-outgoing; Fri, 15 Aug 1997 11:16:27 -0700 (PDT) Received: from elvis.mu.org (paul@elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA10506 for ; Fri, 15 Aug 1997 11:16:18 -0700 (PDT) Received: (from paul@localhost) by elvis.mu.org (4.1/4.1) id NAA02888 for freebsd-scsi@freebsd.org; Fri, 15 Aug 1997 13:16:11 -0500 (CDT) From: Paul Saab Message-Id: <199708151816.NAA02888@elvis.mu.org> Subject: another thing... To: freebsd-scsi@freebsd.org Date: Fri, 15 Aug 1997 13:16:11 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I forgot to mention that the problems occured when amanda ran last night. Paul From owner-freebsd-scsi Fri Aug 15 12:23:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA14082 for freebsd-scsi-outgoing; Fri, 15 Aug 1997 12:23:04 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA14063 for ; Fri, 15 Aug 1997 12:22:51 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id NAA24002; Fri, 15 Aug 1997 13:22:43 -0600 (MDT) Message-Id: <199708151922.NAA24002@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Paul Saab cc: freebsd-scsi@FreeBSD.ORG Subject: Re: what does this mean? In-reply-to: Your message of "Fri, 15 Aug 1997 13:12:17 CDT." <199708151812.NAA02838@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 15 Aug 1997 13:22:45 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I got this today from a machine which I have never seen this problem >before. Could someone please tell me what this means. Thanks. > >Paul It means that you need to upgrade the firmware on your Atlas I to L915. You should be able to get both the firmware and utility to perform the upgrade from ftp.quantum.com. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri Aug 15 15:06:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21706 for freebsd-scsi-outgoing; Fri, 15 Aug 1997 15:06:38 -0700 (PDT) Received: from elvis.mu.org (paul@elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21701 for ; Fri, 15 Aug 1997 15:06:31 -0700 (PDT) Received: (from paul@localhost) by elvis.mu.org (4.1/4.1) id RAA00875 for freebsd-scsi@freebsd.org; Fri, 15 Aug 1997 17:06:15 -0500 (CDT) From: Paul Saab Message-Id: <199708152206.RAA00875@elvis.mu.org> Subject: Re: what does this mean? To: freebsd-scsi@freebsd.org Date: Fri, 15 Aug 1997 17:06:15 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Justin T. Gibbs wrote: > >I got this today from a machine which I have never seen this problem > >before. Could someone please tell me what this means. Thanks. > > > >Paul > > It means that you need to upgrade the firmware on your Atlas I to L915. > You should be able to get both the firmware and utility to perform the > upgrade from ftp.quantum.com. I called Quantum and they said that this update was only for NT. I updated anyway but.... What did those messages mean? Do you think I should swap out the Controller or something else? Paul From owner-freebsd-scsi Fri Aug 15 23:23:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10074 for freebsd-scsi-outgoing; Fri, 15 Aug 1997 23:23:44 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA10069 for ; Fri, 15 Aug 1997 23:23:41 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id QAA25149; Sat, 16 Aug 1997 16:23:07 +1000 From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id PAA05488; Sat, 16 Aug 1997 15:53:05 +0930 (CST) Message-Id: <199708160623.PAA05488@freebie.lemis.com> Subject: Re: another thing... In-Reply-To: <199708151816.NAA02888@elvis.mu.org> from Paul Saab at "Aug 15, 97 01:16:11 pm" To: paul@mu.org (Paul Saab) Date: Sat, 16 Aug 1997 15:53:05 +0930 (CST) Cc: freebsd-scsi@FreeBSD.ORG Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Paul Saab writes: > I forgot to mention that the problems occured when amanda ran last night. You also forgot to mention the subject. I have no idea to which of the 300 messages I received since yesterday this one may relate. Greg From owner-freebsd-scsi Sat Aug 16 18:30:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA22952 for freebsd-scsi-outgoing; Sat, 16 Aug 1997 18:30:25 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA22945 for ; Sat, 16 Aug 1997 18:30:18 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id LAA14147 for ; Sun, 17 Aug 1997 11:29:45 +1000 From: Greg Lehey Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id KAA03776 for freebsd-scsi@freebsd.org; Sun, 17 Aug 1997 10:59:44 +0930 (CST) Message-Id: <199708170129.KAA03776@freebie.lemis.com> Subject: Bus resets. Grrrr. To: freebsd-scsi@freebsd.org (FreeBSD SCSI Mailing List) Date: Sun, 17 Aug 1997 10:59:43 +0930 (CST) Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is the third time in a row that I haven't been able to complete a backup because of "recoverable" SCSI errors. Here's a pretty typical scenario: Aug 17 10:27:19 freebie /kernel: sd0: SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 What does this mean? What can time out when nothing's happening? Or is this a timeout accepting a new command when it shouldn't have to? Is this a device or a driver logic error? Aug 17 10:27:31 freebie /kernel: SEQADDR = 0x9 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Aug 17 10:27:31 freebie /kernel: sd0: Queueing an Abort SCB Aug 17 10:27:31 freebie /kernel: sd0: Abort Message Sent Aug 17 10:27:31 freebie /kernel: sd0: SCB 0x4 - timed out in message out phase, SCSISIGI == 0xa4 Aug 17 10:27:31 freebie /kernel: SEQADDR = 0x9a SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x2 If I understand this correctly, this means that the abort SCB wasn't received either, so the driver does a bus reset: Aug 17 10:27:31 freebie /kernel: ahc0: Issued Channel A Bus Reset. 3 SCBs aborted Aug 17 10:27:32 freebie /kernel: Clearing bus reset Aug 17 10:27:32 freebie /kernel: Clearing 'in-reset' flag Aug 17 10:27:32 freebie /kernel: sd0: no longer in timeout ... which works. Aug 17 10:27:32 freebie /kernel: sd0: SCB 0x4 - timed out in command phase, SCSISIGI == 0x84 So why do we get another timeout? Or is this overlapping? Aug 17 10:27:32 freebie /kernel: SEQADDR = 0x42 SCSISEQ = 0x12 SSTAT0 = 0x7 SSTAT1 = 0x2 Aug 17 10:27:32 freebie /kernel: sd0: abort message in message buffer Aug 17 10:27:32 freebie /kernel: sd1: SCB 0x3 timedout while recovery in progress Aug 17 10:27:32 freebie /kernel: sd0: SCB 1 - Abort Completed. Aug 17 10:27:32 freebie /kernel: sd0: no longer in timeout Aug 17 10:27:32 freebie /kernel: sd1: UNIT ATTENTION asc:29,0 Aug 17 10:27:32 freebie /kernel: sd1: Power on, reset, or bus device reset occurred Aug 17 10:27:32 freebie /kernel: , retries:3 So sd3 complains, but carries on with no harm done, Aug 17 10:27:32 freebie /kernel: st0: UNIT ATTENTION asc:29,0 Aug 17 10:27:32 freebie /kernel: st0: Power on, reset, or bus device reset occurred Aug 17 10:27:32 freebie /kernel: st0: Target Busy but the tape dies. Is there a good reason for this? I would have thought that it would make sense for a power on or reset, but not for a bus reset. Does a tape unit lose its position or data when it receives a bus reset? Is anybody doing anything about this? Greg From owner-freebsd-scsi Sat Aug 16 22:51:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA08142 for freebsd-scsi-outgoing; Sat, 16 Aug 1997 22:51:32 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA08128 for ; Sat, 16 Aug 1997 22:51:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id HAA12848; Sun, 17 Aug 1997 07:51:23 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id HAA18923; Sun, 17 Aug 1997 07:50:01 +0200 (MET DST) Message-ID: <19970817075001.XE28042@uriah.heep.sax.de> Date: Sun, 17 Aug 1997 07:50:01 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI Mailing List) Cc: grog@lemis.com (Greg Lehey) Subject: Re: Bus resets. Grrrr. References: <199708170129.KAA03776@freebie.lemis.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199708170129.KAA03776@freebie.lemis.com>; from Greg Lehey on Aug 17, 1997 10:59:43 +0930 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > This is the third time in a row that I haven't been able to complete > a backup because of "recoverable" SCSI errors. What makes you think these are `recoverable'? Be reminded that this is the typical failure picture one can see from a bad SCSI chain. I'm also seeing it occasionally on our new Seagate/Conner DAT drive at work, where even the older ahc driver used to work with the previous HP DAT (that is dead now). I'm not fully sure yet, but i tend to blame the Conner drive there. > If I understand this correctly, this means that the abort SCB wasn't > received either, so the driver does a bus reset: Which is typical for a SCSI chain where ``Nichts geht mehr''. > Aug 17 10:27:32 freebie /kernel: sd1: UNIT ATTENTION asc:29,0 > Aug 17 10:27:32 freebie /kernel: sd1: Power on, reset, or bus device reset occurred That's the consequence from the bus reset. As you wrote, no harm done for the disks. The unit attention is typically caught by the first (out of 4) retries. > Is anybody doing anything about this? You, checking your termination and term power first? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Aug 16 23:01:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08979 for freebsd-scsi-outgoing; Sat, 16 Aug 1997 23:01:55 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA08971 for ; Sat, 16 Aug 1997 23:01:49 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id QAA06501; Sun, 17 Aug 1997 16:01:16 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id PAA06503; Sun, 17 Aug 1997 15:31:15 +0930 (CST) Message-ID: <19970817153114.20533@lemis.com> Date: Sun, 17 Aug 1997 15:31:14 +0930 From: Greg Lehey To: Joerg Wunsch Cc: FreeBSD SCSI Mailing List Subject: Re: Bus resets. Grrrr. References: <199708170129.KAA03776@freebie.lemis.com> <19970817075001.XE28042@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <19970817075001.XE28042@uriah.heep.sax.de>; from J Wunsch on Sun, Aug 17, 1997 at 07:50:01AM +0200 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Aug 17, 1997 at 07:50:01AM +0200, J Wunsch wrote: > As Greg Lehey wrote: > >> This is the third time in a row that I haven't been able to complete >> a backup because of "recoverable" SCSI errors. > > What makes you think these are `recoverable'? The disks recover. > Be reminded that this is the typical failure picture one can see from > a bad SCSI chain. Yup. But that's not the only thing. > I'm also seeing it occasionally on our new Seagate/Conner DAT drive at > work, where even the older ahc driver used to work with the previous > HP DAT (that is dead now). I'm not fully sure yet, but i tend to > blame the Conner drive there. Interesting. The tape in question is a Conner^H^H^H^H^H^HArchive^H^H^H^H^H^H^HSeagate changer--see the dmesg output below for more info. But that doesn't seem to be the problem: it's always the Micropolis disk which has the timeout. >> If I understand this correctly, this means that the abort SCB wasn't >> received either, so the driver does a bus reset: > > Which is typical for a SCSI chain where ``Nichts geht mehr''. But which can happen as well at other times. >> Aug 17 10:27:32 freebie /kernel: sd1: UNIT ATTENTION asc:29,0 >> Aug 17 10:27:32 freebie /kernel: sd1: Power on, reset, or bus device reset occurred > > That's the consequence from the bus reset. As you wrote, no harm done > for the disks. The unit attention is typically caught by the first > (out of 4) retries. My question (which you omitted): does this have to be fatal for the tape? Is there indeterminate data loss (i.e. can we not be sure whether a block has been written or not?) >> Is anybody doing anything about this? > > You, checking your termination and term power first? No, been there, done that. Do you think I'd ask a question like that without doing my homework first? Also, this config has been running smoothly for weeks. In that connection, however, I suspect problems with the IBM DORS-32160 drives I have connected to that host adapter. They just plain Would Not Work on any host adapter together with my Conner CFP4207S. The BIOS wouldn't even get through the scan. Here are some relevant parts of the config: ahc0: rev 0x03 int a irq 12 on pci0.18.0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 scbus0 target 0 lun 0: type 0 fixed SCSI 2 sd0 at scbus0 target 0 lun 0 sd0: Direct-Access 1001MB (2051615 512 byte sectors) sd0: with 1760 cyls, 15 heads, and an average 77 sectors/track scbus0 target 3 lun 0: type 0 fixed SCSI 2 sd1 at scbus0 target 3 lun 0 sd1: Direct-Access 2063MB (4226725 512 byte sectors) sd1: with 6703 cyls, 5 heads, and an average 126 sectors/track scbus0 target 4 lun 0: type 1 removable SCSI 2 st0 at scbus0 target 4 lun 0 st0: Sequential-Access density code 0x24, 512-byte blocks, write-enabled scbus0 target 4 lun 1: type 8 removable SCSI 2 uk0 at scbus0 target 4 lun 1 uk0: Unknown scbus0 target 5 lun 0: type 1 removable SCSI 1 st1 at scbus0 target 5 lun 0 st1: Sequential-Access density code 0x0, drive empty scbus1 at aha0 bus 0 scbus1 target 2 lun 0: type 0 fixed SCSI 2 sd2 at scbus1 target 2 lun 0 Any ideas? I was thinking of moving the Micropolis drive to the aha, but that suffers from other problems, over and above the performance loss. Greg From owner-freebsd-scsi Sat Aug 16 23:06:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA09244 for freebsd-scsi-outgoing; Sat, 16 Aug 1997 23:06:05 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09228 for ; Sat, 16 Aug 1997 23:06:01 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id AAA17585; Sun, 17 Aug 1997 00:30:14 -0500 (CDT) Message-Id: <199708170530.AAA17585@iworks.InterWorks.org> Date: Sun, 17 Aug 1997 00:30:14 -0500 (CDT) From: "Daniel M. Eischen" To: freebsd-scsi@FreeBSD.ORG, grog@lemis.com Subject: Re: Bus resets. Grrrr. Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is the third time in a row that I haven't been able to complete a backup > because of "recoverable" SCSI errors. Here's a pretty typical scenario: > > IGI == 0x0 > > What does this mean? What can time out when nothing's happening? Or is this a > timeout accepting a new command when it shouldn't have to? Is this a device or > a driver logic error? I think you're missing a few character. It should probably read SCSISIGI = 0x0, which means the SCSI Control Signal Register was thinks it's in a Data Out phase. [...] > but the tape dies. Is there a good reason for this? I would have thought that > it would make sense for a power on or reset, but not for a bus reset. Does a > tape unit lose its position or data when it receives a bus reset? I get this also when doing backups on my HP C1533 with tapes that are older/bad. The drive seems to retension itself, or something similar, during the middle of accessing it. Using a newer tape doesn't exhibit the same problem. Usually, my system will lock up when this happens. This is under 3.0-current, though I haven't tried since Justin committed the spin-lock fix to the sequencer. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-scsi Sat Aug 16 23:21:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10151 for freebsd-scsi-outgoing; Sat, 16 Aug 1997 23:21:19 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA10143 for ; Sat, 16 Aug 1997 23:21:15 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA13058; Sun, 17 Aug 1997 08:21:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.7/8.8.5) id IAA19114; Sun, 17 Aug 1997 08:12:39 +0200 (MET DST) Message-ID: <19970817081239.KP35653@uriah.heep.sax.de> Date: Sun, 17 Aug 1997 08:12:39 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI Mailing List) Cc: grog@lemis.com (Greg Lehey) Subject: Re: Bus resets. Grrrr. References: <199708170129.KAA03776@freebie.lemis.com> <19970817075001.XE28042@uriah.heep.sax.de> <19970817153114.20533@lemis.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970817153114.20533@lemis.com>; from Greg Lehey on Aug 17, 1997 15:31:14 +0930 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > > What makes you think these are `recoverable'? > > The disks recover. Well, sorta. After a bus reset. That's close to powering them off... > Interesting. The tape in question is a > Conner^H^H^H^H^H^HArchive^H^H^H^H^H^H^HSeagate changer--see the dmesg > output below for more info. But that doesn't seem to be the problem: > it's always the Micropolis disk which has the timeout. Can you move one of them to the other SCSI bus? > My question (which you omitted): does this have to be fatal for the > tape? Sure. The bus didn't accept any command. The bus reset is a (hmm, how does the SCSI standard call this?), at least a hardware thing. You're asserting it as a signal on the entire bus. Naturally, this aborts all operations. I gotta leave more detailed explanations to Justin, it's beyond my point of wisdom then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)