From owner-freebsd-scsi Sun Jun 2 06:48:13 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA19438 for freebsd-scsi-outgoing; Sun, 2 Jun 1996 06:48:13 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA19428 for ; Sun, 2 Jun 1996 06:48:07 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA20775; Sun, 2 Jun 1996 15:47:54 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA28015; Sun, 2 Jun 1996 15:47:54 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id JAA12335; Sun, 2 Jun 1996 09:54:05 +0200 (MET DST) From: J Wunsch Message-Id: <199606020754.JAA12335@uriah.heep.sax.de> Subject: Re: Archive Viper not correctly identified. To: scsi@freebsd.org Date: Sun, 2 Jun 1996 09:54:04 +0200 (MET DST) Cc: jfieber@indiana.edu (John Fieber) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from John Fieber at "May 31, 96 08:25:21 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As John Fieber wrote: > Regardless, a more informative comment at the head of the quirk > list describing the policy, and mentioning the fact that the > manufacturer, model and revision fields are 8, 16 and 4 bytes > respectively would be helpful to future quriklist maintainers. Since you are going to commit a change in this area anyway... do add this comment. :) Btw., this changes is potentially also valid for the -stable branch. Alas, 2.1 didn't use the exact same quirk semantics as we do now, so this one will be quite a bit more work. John, tell us if you are _not_ going to do it (so someone else can do it). -- 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 Jun 2 06:48:50 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA19560 for freebsd-scsi-outgoing; Sun, 2 Jun 1996 06:48:50 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA19528 for ; Sun, 2 Jun 1996 06:48:44 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id PAA20873; Sun, 2 Jun 1996 15:48:31 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id PAA28052; Sun, 2 Jun 1996 15:48:31 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id OAA01065; Sun, 2 Jun 1996 14:56:49 +0200 (MET DST) From: J Wunsch Message-Id: <199606021256.OAA01065@uriah.heep.sax.de> Subject: Re: Parallel to Scsi To: freebsd-scsi@freebsd.org Date: Sun, 2 Jun 1996 14:56:49 +0200 (MET DST) Cc: afurman@sunfire.j51.com (Adam Furman) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from Adam Furman at "Jun 1, 96 00:13:24 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (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 As Adam Furman wrote: > I have a FreeBSD server that has IDE drives in it. I would like to get > the Belkin one because I would like to move around my external dat drive > and would find this conivernt and chaper. I'm sorry to say, but i doubt anybody is going to write a driver for this type of devices anytime soon. Given the crippled design of the standard parallel port, and the fact that the cheapest full-featured SCSI controller (NCR 53C810) is about US$ 80 these days, i doubt any effort in this area would really pay off (unless you're in the business of selling faster CPUs, of course :). -- 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 Jun 2 07:55:38 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA23335 for freebsd-scsi-outgoing; Sun, 2 Jun 1996 07:55:38 -0700 (PDT) Received: from wood.helios.nd.edu (hyan@wood.helios.nd.edu [129.74.217.24]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id HAA23330 for ; Sun, 2 Jun 1996 07:55:36 -0700 (PDT) Received: from localhost (hyan@localhost) by wood.helios.nd.edu (8.6.12/8.6.12) with SMTP id JAA07763 for ; Sun, 2 Jun 1996 09:55:34 -0500 Date: Sun, 2 Jun 1996 09:55:34 -0500 (EST) From: "Hong Yan (Karen)" To: freebsd-scsi@FreeBSD.org Subject: unsubscribe freebsd-scsi Hong Yan hyan@bach.helios.nd.edu In-Reply-To: <199606021256.OAA01065@uriah.heep.sax.de> 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 unsubscribe freebsd-scsi Hong Yan hyan@bach.helios.nd.edu From owner-freebsd-scsi Sun Jun 2 11:50:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA03614 for freebsd-scsi-outgoing; Sun, 2 Jun 1996 11:50:12 -0700 (PDT) Received: from Fieber-John.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA03608 for ; Sun, 2 Jun 1996 11:50:09 -0700 (PDT) Received: from localhost (jfieber@localhost) by Fieber-John.campusview.indiana.edu (8.7.5/8.7.3) with SMTP id NAA00334; Sun, 2 Jun 1996 13:49:53 -0500 (EST) X-Authentication-Warning: Fieber-John.campusview.indiana.edu: jfieber owned process doing -bs Date: Sun, 2 Jun 1996 13:49:52 -0500 (EST) From: John Fieber X-Sender: jfieber@Fieber-John.campusview.indiana.edu To: Joerg Wunsch cc: scsi@freebsd.org Subject: Re: Archive Viper not correctly identified. In-Reply-To: <199606020754.JAA12335@uriah.heep.sax.de> 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 Sun, 2 Jun 1996, J Wunsch wrote: > Btw., this changes is potentially also valid for the -stable branch. > Alas, 2.1 didn't use the exact same quirk semantics as we do now, so A change isn't necessary because the "rogue code" in 2.1 works correctly with the drive in question. ...unless, the -stable branch has moved to the new scsiconf; I have not checked. > this one will be quite a bit more work. John, tell us if you are > _not_ going to do it (so someone else can do it). I'll put in the change, hopefully I can get to it later today. -john == jfieber@indiana.edu =========================================== == http://fallout.campusview.indiana.edu/~jfieber ================ From owner-freebsd-scsi Sun Jun 2 14:45:49 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA12983 for freebsd-scsi-outgoing; Sun, 2 Jun 1996 14:45:49 -0700 (PDT) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA12972 for ; Sun, 2 Jun 1996 14:45:43 -0700 (PDT) Received: by Sisyphos id AA21668 (5.67b/IDA-1.5 for scsi@FreeBSD.ORG); Sun, 2 Jun 1996 23:45:02 +0200 Message-Id: <199606022145.AA21668@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 2 Jun 1996 23:45:01 +0200 In-Reply-To: Tony Kimball "ncr scsi Qs" (May 29, 0:45) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Tony Kimball Subject: Re: ncr scsi Qs Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On May 29, 0:45, Tony Kimball wrote: } Subject: ncr scsi Qs } } Since switching from an Adaptec 1542CF ISA to a CSC NCR PCI scsi } controller, my ancient Micropolis drive has been filling my logs } with this stuff: } } May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): RECOVERED ERROR info:1857e6 asc:3,0 Peripheral device write fault } May 28 23:25:36 compound /kernel: , retries:4 } May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): extraneous data discarded. } May 28 23:25:36 compound /kernel: sd1(ncr0:2:0): COMMAND FAILED (9 0) @f10d3400. } May 28 23:30:09 compound /kernel: sd1(ncr0:2:0): RECOVERED ERROR info:1b6aa5 asc:3,0 Peripheral device write fault } May 28 23:30:09 compound /kernel: , retries:4 Hmm, I'm not sure about the exact definition of the ASC info the drive returns, but it appears to be a problem detected by the firmware which leads to the current command being aborted. This does not seem to be a SCSI bus parity problem, since the message would be different ... } Is this a familiar problem for anyone? I had the adaptec turned down } to 8MB/sec in order to accomodate this drive. Is there any way to } throttle back the scsi bus xfers on the ncr controller? Yes, sure: # ncrcontrol -t 2 -s sync=8 will reduce the sync. transfer speed the driver is willing to negotiate to at most 8MHz. The -t limits the following options to just the target selected (ID 2 in this case). See the "ncrcontrol" man page for details and further options. Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-scsi Wed Jun 5 20:48:12 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA00608 for freebsd-scsi-outgoing; Wed, 5 Jun 1996 20:48:12 -0700 (PDT) Received: from hopf.dnai.com (hopf.dnai.com [140.174.162.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA00591; Wed, 5 Jun 1996 20:48:03 -0700 (PDT) Received: from mars.dnai.com (mars.dnai.com [140.174.162.14]) by hopf.dnai.com (8.6.10/8.6.10) with SMTP id UAA13399; Wed, 5 Jun 1996 20:39:57 -0700 Date: Wed, 5 Jun 1996 20:45:26 -0700 (PDT) From: Dror Matalon Reply-To: Dror Matalon To: freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org Subject: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues 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 Hi Folks, We're using an NCR 53c825 wide scsi controller with 3 Quantum XP34300W 4.3 Fast Wide SCSI drives on a pentium 133 as our news machine. We started getting the messages: sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error , retries:4 sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error , retries:3 ... These messages always complain about 2 addresses 7476a9 and 747d9d. We suspect that these are on the swap area of the first disk. 1. Is there a way to take care of this problem other than swaping out the disk? Could we somehow mark these areas as bad? 2. My number 1 frustration with FreeBsd/Unix on a PC is related to the number of SCSI errors that we're running into. We might be at fault for not running the computer room cool enough, and the PC type of SCSI connectors/cables might also be the problem -- we only recently started using Granite's custom made SCSI cables. Still we've had close to 20% mortality rate on our SCSI disks. Are other people also experiencing these kind or problems? Dror Matalon Voice: 510 649-6110 Direct Network Access Fax: 510 649-7130 2039 Shattuck Avenue Modem: 510 649-6116 Berkeley, CA 94704 Email: dror@dnai.com From owner-freebsd-scsi Wed Jun 5 22:55:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA05362 for freebsd-scsi-outgoing; Wed, 5 Jun 1996 22:55:14 -0700 (PDT) Received: from okjunc.junction.net (root@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA05345; Wed, 5 Jun 1996 22:55:10 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id WAA28368; Wed, 5 Jun 1996 22:10:56 -0700 Date: Wed, 5 Jun 1996 22:54:18 -0700 (PDT) From: Michael Dillon To: Dror Matalon cc: freebsd-scsi@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues In-Reply-To: Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 5 Jun 1996, Dror Matalon wrote: > Quantum XP34300W 4.3 Fast Wide SCSI drives on a pentium 133 > as our news machine. News servers eat drives. No matter what type of drive, they just wear out and die. > 2. My number 1 frustration with FreeBsd/Unix on a PC is related to > the number of SCSI errors that we're running into. We might be at > fault for not running the computer room cool enough, Computer room??? How about the case where the drives are? Most clone cases have NO (that's zero) airflow engineering done. The only way to be sure that the drives are running cool enough (especially 7200 RPM drives) is to mount them with space in between (an inch or so) and mount extra fans that blow air across the top of the drive. When you open the case and remove the bad drive, stick your finger on top. If it burns so badly that it blisters, you need more cooling. Even if it's only hot, add more airflow anyway. > recently started using Granite's custom made SCSI cables. Still > we've had close to 20% mortality rate on our SCSI disks. Are other > people also experiencing these kind or problems? Almost everybody who runs news servers. Go into your machine room any time day or night and you hear drives rattling constantly. Go put your ear against the news server, that's the one that NEVER stops rattling. The others actually go in fits and starts. It helps to really cool things down a lot, i.e. air conditioned machine room that you need to put on a sweater when you go in. It also helps to use RAID (http://www.mylex.com DAC960SI) because it lessens the physical activity on any one drive to some extent. And the special fans to blow air across the top of each individual drive. The nice thing about a DAC960 is that with a proper hot-swap chassis and RAID 5, replacing a drive doesn't shut anything down. Michael Dillon ISP & Internet Consulting Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com From owner-freebsd-scsi Thu Jun 6 04:11:41 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA18787 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 04:11:41 -0700 (PDT) Received: from guardian.fortress.org (fortress.org [199.84.158.128]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA18781; Thu, 6 Jun 1996 04:11:36 -0700 (PDT) Received: (from andrew@localhost) by guardian.fortress.org (8.6.12/8.6.12) id HAA04720; Thu, 6 Jun 1996 07:10:26 -0400 Date: Thu, 6 Jun 1996 07:10:25 -0400 (EDT) From: Andrew Webster Reply-To: andrew@pubnix.net To: Dror Matalon cc: freebsd-scsi@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI , issues 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 Wed, 5 Jun 1996, Dror Matalon wrote: > Hi Folks, > > We're using an NCR 53c825 wide scsi controller with 3 > Quantum XP34300W 4.3 Fast Wide SCSI drives on a pentium 133 > as our news machine. > > We started getting the messages: > sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error > , retries:4 > sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error > , retries:3 > ... > > These messages always complain about 2 addresses 7476a9 and 747d9d. > We suspect that these are on the swap area of the first disk. Very interesting, I had a bad experience almost a year ago where a system ate two of these Quantum XP34300 drives in two months, and it wasn't a news server! This was a P133 with AHA-2940 with FreeBSD 2.0.5. What I'd noticed in both cases was that when lots of seek activity occurs, occasionally, the drive would stop seeking and a loud "ringing" sound would be heard from the drive for a couple of seconds, and then it would continue seeking. I've seen this in a couple of other vendor's drives as well. I suspect that the head/arm mechanism may start resonating due to the speed at which the seeks are being done, and this may lead to head crashes. In the case of the Quantum drives, both drives, when they failed, had bad spots all over the disks! I don't think the problem was related to heat, as the drive was in an external enclosure with its own fan. After two disks suffering the same fate, I switched the disk for a Seagate and all the problems went away! Bleeding edge technology? Maybe! Andrew Webster - andrew@pubnix.net - http://www.pubnix.net PubNIX Montreal - Connected to the world - Branche au monde 514-990-5911 - P.O. Box 147, Cote St-Luc, Quebec, H4V 2Y3 From owner-freebsd-scsi Thu Jun 6 04:42:45 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA20229 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 04:42:45 -0700 (PDT) Received: from hda (ip86-max1-fitch.zipnet.net [199.232.245.86]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA20208; Thu, 6 Jun 1996 04:42:39 -0700 (PDT) Received: (from dufault@localhost) by hda (8.6.11/8.6.9) id HAA17307; Thu, 6 Jun 1996 07:46:38 -0400 From: Peter Dufault Message-Id: <199606061146.HAA17307@hda> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues To: dror@hopf.dnai.com Date: Thu, 6 Jun 1996 07:46:36 -0400 (EDT) Cc: freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: from "Dror Matalon" at Jun 5, 96 08:45:26 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Hi Folks, > > We're using an NCR 53c825 wide scsi controller with 3 > Quantum XP34300W 4.3 Fast Wide SCSI drives on a pentium 133 > as our news machine. > > We started getting the messages: > sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error > , retries:4 > sd0(ncr0:0:0): MEDIUM ERROR info:7476a9 asc:11,0 Unrecovered read error > , retries:3 > ... > This indicates that the drive can't read those blocks. Even if you have automatic read and write reallocation enabled the drive won't reallocate on a read failure. You should: 1. Check that you do have AWRE and ARRE on in mode page 1 - see how to use the mode page editor in scsi(8) to check and change this; 2. Once these are on, you can map out the block by writing anything to that block. You will change the data on the disk. Alternatively, this UNTESTED script should map it out (sorry, I don't have any disks with bad blocks on line): ++Start of scsiremap: #!/bin/sh PATH="/sbin:/usr/sbin:/bin:/usr/bin"; export PATH RAW= usage() { echo "Usage: scsiremap raw-device-name block" 1>&2 exit 2 } shift $(($OPTIND - 1)) if [ $# -ne 2 ] ; then usage fi RAW=$1 BLOCK=$2 if [ "x$RAW" = "x" ] ; then usage fi if expr "$RAW" : 'sd[0-9][0-9]*$' > /dev/null ; then # generic disk name given, convert to control device name RAW="/dev/r${RAW}.ctl" fi scsi -f $RAW -c "7 0 0 0 0 0" -o 8 "0 0 4:i2 v:i4" $BLOCK --End scsiremap. (block can be either decimal or hex if preceded by 0x) This isn't a general utility because I don't know that this is the right thing to do. What does the drive do for that data it can't read? It doesn't say what in the SCSI spec. Is it better to turn off ECC, read as much as you can from the block, then write it back forcing the slip? Do you want to restore from backups? Etc. > These messages always complain about 2 addresses 7476a9 and 747d9d. > We suspect that these are on the swap area of the first disk. > > 1. Is there a way to take care of this problem other than swaping > out the disk? Could we somehow mark these areas as bad? > > 2. My number 1 frustration with FreeBsd/Unix on a PC is related to > the number of SCSI errors that we're running into. We might be at > fault for not running the computer room cool enough, and the PC > type of SCSI connectors/cables might also be the problem -- we only > recently started using Granite's custom made SCSI cables. Still > we've had close to 20% mortality rate on our SCSI disks. Are other > people also experiencing these kind or problems? If you are swapping out disks because you are developing read errors then: You have to figure out why you are developing these read errors. An OS needs a well thought out policy for handling developed read errors to hide this from the user. -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Thu Jun 6 06:31:09 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27850 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 06:31:09 -0700 (PDT) Received: from hda (ip86-max1-fitch.zipnet.net [199.232.245.86]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA27818; Thu, 6 Jun 1996 06:31:03 -0700 (PDT) Received: (from dufault@localhost) by hda (8.6.11/8.6.9) id JAA17446; Thu, 6 Jun 1996 09:34:59 -0400 From: Peter Dufault Message-Id: <199606061334.JAA17446@hda> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI , issues To: andrew@pubnix.net Date: Thu, 6 Jun 1996 09:34:58 -0400 (EDT) Cc: dror@hopf.dnai.com, freebsd-scsi@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG In-Reply-To: from "Andrew Webster" at Jun 6, 96 07:10:25 am Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > ate two of these Quantum XP34300 drives in two months, and it wasn't a news > server! > > This was a P133 with AHA-2940 with FreeBSD 2.0.5. What I'd noticed in > both cases was that when lots of seek activity occurs, occasionally, the > drive would stop seeking and a loud "ringing" sound would be heard from > the drive for a couple of seconds, and then it would continue seeking. > I've seen this in a couple of other vendor's drives as well... This may be a thermal recalibration of the servo mechanism. The old CDC drive I have makes a "KA-PROING" noise when it does it and it takes a few seconds to complete. -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Thu Jun 6 06:39:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA28347 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 06:39:04 -0700 (PDT) Received: from hda (ip86-max1-fitch.zipnet.net [199.232.245.86]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA28328; Thu, 6 Jun 1996 06:38:59 -0700 (PDT) Received: (from dufault@localhost) by hda (8.6.11/8.6.9) id JAA17463; Thu, 6 Jun 1996 09:43:05 -0400 From: Peter Dufault Message-Id: <199606061343.JAA17463@hda> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues To: dror@hopf.dnai.com Date: Thu, 6 Jun 1996 09:43:05 -0400 (EDT) Cc: freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: from "Dror Matalon" at Jun 5, 96 08:45:26 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > We suspect that these are on the swap area of the first disk. (oops, just noticed that part) . If this is really on the swap area of the disk (verify that by looking at the partition info and seeing where that block is) then this is easy to fix: 1. Verify that AWRE is enabled in mode page 1; 2. Disable swap on that partition; 3. dd from /dev/zero to that partition. The write will force the sector to remap; 4. Tell -hackers that swap is being read before written (that doesn't make much sense). -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Thu Jun 6 07:12:11 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA02185 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 07:12:11 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA02106; Thu, 6 Jun 1996 07:12:00 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id JAA02596; Thu, 6 Jun 1996 09:11:13 -0500 (EST) From: "John S. Dyson" Message-Id: <199606061411.JAA02596@dyson.iquest.net> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues To: hdalog@zipnet.net Date: Thu, 6 Jun 1996 09:11:13 -0500 (EST) Cc: dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: <199606061343.JAA17463@hda> from "Peter Dufault" at Jun 6, 96 09:43:05 am X-Mailer: ELM [version 2.4 PL24 ME8] 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 > > 4. Tell -hackers that swap is being read before written (that doesn't make much > sense). > EEEK!!! I'll look into it, but also we would use a problem report. John dyson@freebsd.org From owner-freebsd-scsi Thu Jun 6 07:24:38 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA04478 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 07:24:38 -0700 (PDT) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA04456; Thu, 6 Jun 1996 07:24:30 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id HAA07038; Thu, 6 Jun 1996 07:22:11 -0700 (PDT) Message-Id: <199606061422.HAA07038@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol To: andrew@pubnix.net cc: Dror Matalon , freebsd-scsi@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI , issues In-reply-to: Your message of "Thu, 06 Jun 1996 07:10:25 EDT." From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 06 Jun 1996 07:22:11 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Very interesting, I had a bad experience almost a year ago where a system >ate two of these Quantum XP34300 drives in two months, and it wasn't a news >server! Are you sure that they weren't XP34301 drives? I've never had a problem with the Atlas (XP34300), but I've had a 70% failure rate on Grand Prixs (XP34301). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-scsi Thu Jun 6 09:37:07 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA13812 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 09:37:07 -0700 (PDT) Received: from okjunc.junction.net (root@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA13792; Thu, 6 Jun 1996 09:37:03 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id IAA03748; Thu, 6 Jun 1996 08:52:19 -0700 Date: Thu, 6 Jun 1996 09:35:41 -0700 (PDT) From: Michael Dillon To: hdalog@zipnet.net cc: dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues In-Reply-To: <199606061343.JAA17463@hda> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 6 Jun 1996, Peter Dufault wrote: > 3. dd from /dev/zero to that partition. The write will force the sector > to remap; If you are talking about the internal SCSI remapping, then when the internally allocated table is full, no more remapping will take place resulting in error reports by the OS. Generally a drive with that many errors can be replaced under warranty. I remember the older 1 gig Quantum drives that would not work in *ANY* UNIX system. I had one drive in BSDI system reporting lots of errors. Ran diagnostics and it was clean. Put it into a Linux machine, still lots of errors, diagnostics report was clean. Different host adapter. Same problem. Put in a Windows workstation and it works like a charm. A month later while setting up a SCO UNIX box, we got wierd, wierd read errors. They weren't reported in the system log, but a database program was definitely getting the wrong data off the drive. It was the same Quantum 1 gig drive so we sent it back, grabbed two 500 meg IDE's off the shelf and everything works now. Maybe Quantum's engineering does something wierd internally and doesn't test their drives on a real world activity mix that includes UNIX. Michael Dillon ISP & Internet Consulting Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com From owner-freebsd-scsi Thu Jun 6 15:40:47 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA15947 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 15:40:47 -0700 (PDT) Received: from guardian.fortress.org (fortress.org [199.84.158.128]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA15930; Thu, 6 Jun 1996 15:40:43 -0700 (PDT) Received: (from andrew@localhost) by guardian.fortress.org (8.6.12/8.6.12) id SAA05787; Thu, 6 Jun 1996 18:39:25 -0400 Date: Thu, 6 Jun 1996 18:39:24 -0400 (EDT) From: Andrew Webster Reply-To: andrew@pubnix.net To: David Greenman cc: Dror Matalon , freebsd-scsi@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI , issues In-Reply-To: <199606061422.HAA07038@Root.COM> 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 Thu, 6 Jun 1996, David Greenman wrote: > >Very interesting, I had a bad experience almost a year ago where a system > >ate two of these Quantum XP34300 drives in two months, and it wasn't a news > >server! > > Are you sure that they weren't XP34301 drives? I've never had a problem > with the Atlas (XP34300), but I've had a 70% failure rate on Grand Prixs > (XP34301). > Your are absolutely right, they were indeed GP drives! Andrew Webster - andrew@pubnix.net - http://www.pubnix.net PubNIX Montreal - Connected to the world - Branche au monde 514-990-5911 - P.O. Box 147, Cote St-Luc, Quebec, H4V 2Y3 From owner-freebsd-scsi Thu Jun 6 23:53:39 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA22330 for freebsd-scsi-outgoing; Thu, 6 Jun 1996 23:53:39 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA22308; Thu, 6 Jun 1996 23:53:29 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id XAA08211; Thu, 6 Jun 1996 23:53:01 -0700 (PDT) Message-Id: <199606070653.XAA08211@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Dillon cc: hdalog@zipnet.net, dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues In-reply-to: Your message of Thu, 06 Jun 96 09:35:41 -0700. Date: Thu, 06 Jun 1996 23:52:53 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Maybe Quantum's engineering does something wierd internally and doesn't >test their drives on a real world activity mix that includes UNIX. That would be hard to believe, considering that Quantum drives ship in some HP Workstations, among others... ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-scsi Fri Jun 7 05:48:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA12221 for freebsd-scsi-outgoing; Fri, 7 Jun 1996 05:48:31 -0700 (PDT) Received: from unicorn.uk1.vbc.net (unicorn.uk1.vbc.net [204.137.194.11]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA12215 for ; Fri, 7 Jun 1996 05:48:28 -0700 (PDT) Received: (from gordon@localhost) by unicorn.uk1.vbc.net (8.7.3/8.7.3) id NAA00417; Fri, 7 Jun 1996 13:46:05 +0100 Date: Fri, 7 Jun 1996 13:46:05 +0100 (BST) From: Gordon Henderson X-Sender: gordon@unicorn To: freebsd-scsi@freebsd.org Subject: Anyone using Adaptec 2940 & ASUS '486 boards? 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 It's probably not a specific FreeBSD question - but I'm trying to get FreeBSD going on this combination. ASUS 486 mainboard (PVI-486SP3) AMD 486DX4/100 processor 64MB RAM Adaptec 2940 PCI SCSI card Cirrus 5436 PCI graphics card 3com590 ethernet card and 3 SCSI disks. (No IDE's) It doesn't work. The problems I see are the scsi disks not being recognised by the firmware on the SCSI card or, the machine hanging during the newfs part of an installation. It doesn't make any difference if the ethernet card in in or not so I don't think thats causing the problem. If I replace the PCI SCSI card with an old Adaptec ISA SCSI card then it works fine, I can complete the install without a hitch. If I take the 3 cards & memory and plug them into an ASUS P120 board then it also works fine. I have tried 2 different ASUS PVI-486SP3 mainboards and 2 different Adaptec 2490 PCI SCSI carsd with no luck. I've double checked the board jumpers & BIOS settings, altered them, reset them back to defaults but with no luck. Anyone seen any similar problems with ASUS 486 mainboards or the Adaptec PCI SCSI cards? Gordon From owner-freebsd-scsi Fri Jun 7 07:37:07 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA19114 for freebsd-scsi-outgoing; Fri, 7 Jun 1996 07:37:07 -0700 (PDT) Received: from isgate.is (isgate.is [193.4.58.51]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA19108 for ; Fri, 7 Jun 1996 07:37:04 -0700 (PDT) Received: from hummer.islandia.is by isgate.is (8.7.5-M/ISnet/14-10-91); Fri, 7 Jun 1996 14:36:58 GMT Received: from hummer.islandia.is by hummer.islandia.is (8.6.12/ISnet/12-09-94); Fri, 7 Jun 1996 14:36:52 GMT Date: Fri, 7 Jun 1996 14:36:51 +0000 (GMT) From: "Gestur A. Grjetarsson" To: Gordon Henderson cc: freebsd-scsi@freebsd.org Subject: Re: Anyone using Adaptec 2940 & ASUS '486 boards? 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 Fri, 7 Jun 1996, Gordon Henderson wrote: > Date: Fri, 7 Jun 1996 13:46:05 +0100 (BST) > From: Gordon Henderson > To: freebsd-scsi@freebsd.org > Subject: Anyone using Adaptec 2940 & ASUS '486 boards? > > > It's probably not a specific FreeBSD question - but I'm trying to get > FreeBSD going on this combination. > > ASUS 486 mainboard (PVI-486SP3) > AMD 486DX4/100 processor > 64MB RAM > Adaptec 2940 PCI SCSI card > Cirrus 5436 PCI graphics card > 3com590 ethernet card > and 3 SCSI disks. (No IDE's) > > It doesn't work. The problems I see are the scsi disks not being > recognised by the firmware on the SCSI card or, the machine hanging during > the newfs part of an installation. It doesn't make any difference if the > ethernet card in in or not so I don't think thats causing the problem. > check if the bios on this board is conflicting with the SCSI card's bios. > I've double checked the board jumpers & BIOS settings, altered them, > reset them back to defaults but with no luck. > check if this motherboard has an ide controller onboard, if so, check if the interupts req are same as the scsi card. > Anyone seen any similar problems with ASUS 486 mainboards or the Adaptec > PCI SCSI cards? > we at islandia.is are using Adaptec 2940w SCSI2 with three diffrent systems, all of them are working great. One system is running the Adaptec with and onboard ide controller, it identifies with all of the SCSI dev's along with the ide disk. Med kvedju Sincerely -------------------------------------------------- Gestur A. Grjetarsson gestur@islandia.is kerfisstjori islandia.is sysadmin islandia.is http://www.islandia.is/~gestur http://www.islandia.is/misc/skvopn There are only three kind of people in the world ! Those who know how to count, and those who don't ! From owner-freebsd-scsi Fri Jun 7 12:31:00 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA13881 for freebsd-scsi-outgoing; Fri, 7 Jun 1996 12:31:00 -0700 (PDT) Received: from hopf.dnai.com (hopf.dnai.com [140.174.162.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA13876; Fri, 7 Jun 1996 12:30:57 -0700 (PDT) Received: from mars.dnai.com (mars.dnai.com [140.174.162.14]) by hopf.dnai.com (8.6.10/8.6.10) with SMTP id MAA14562; Fri, 7 Jun 1996 12:23:03 -0700 Date: Fri, 7 Jun 1996 12:28:22 -0700 (PDT) From: Dror Matalon Reply-To: Dror Matalon To: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read ...other SCSI issues 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 Michael Dillon says: >News servers eat drives. No matter what type of drive, they just wear out >and die. Yes, I guess I knew that, although our web server is doing plenty of disk io too. >Computer room??? How about the case where the drives are? Most clone cases >have NO (that's zero) airflow engineering done. The only way to be sure >that the drives are running cool enough (especially 7200 RPM drives) is to >mount them with space in between (an inch or so) and mount extra fans that >blow air across the top of the drive. When you open the case and remove >the bad drive, stick your finger on top. If it burns so badly that it >blisters, you need more cooling. Even if it's only hot, add more airflow >anyway. I'll look at that, although I think I'll try some other testing methodology. > >room that you need to put on a sweater when you go in. It also helps to >use RAID (http://www.mylex.com DAC960SI) because it lessens the physical >activity on any one drive to some extent. And the special fans to blow air >across the top of each individual drive. The nice thing about a DAC960 is >that with a proper hot-swap chassis and RAID 5, replacing a drive doesn't >shut anything down. I'd love using some kind of RAID solution. So far I haven't found anything that I really like, and that has been tested. Are you using the mylex RAID? I looked at it a while ago and it sounded like an interesting solution, but I first wanted to hear about other people using it. I also understand that there are some problems with the freebsd utilities handling large (20 Gig and more) disks, they report negative sizes etc (32 bit problem?). I actually think that someone could make nice bucks, by putting together a FreeBsd box with redundant Power supplies, fans, Scsi controllers etc and make it a, relatively, cheap NFS appliance. As for the disk with the SCSI errors, we're just replacing it with a new one. Thanks for all the replies and help, Dror Dror Matalon Voice: 510 649-6110 Direct Network Access Fax: 510 649-7130 2039 Shattuck Avenue Modem: 510 649-6116 Berkeley, CA 94704 Email: dror@dnai.com From owner-freebsd-scsi Fri Jun 7 14:10:19 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA21629 for freebsd-scsi-outgoing; Fri, 7 Jun 1996 14:10:19 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA21621; Fri, 7 Jun 1996 14:10:14 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id OAA11907; Fri, 7 Jun 1996 14:10:01 -0700 From: "Rodney W. Grimes" Message-Id: <199606072110.OAA11907@GndRsh.aac.dev.com> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read ...other SCSI issues To: dror@hopf.dnai.com Date: Fri, 7 Jun 1996 14:10:01 -0700 (PDT) Cc: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: from Dror Matalon at "Jun 7, 96 12:28:22 pm" X-Mailer: ELM [version 2.4ME+ PL11 (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'd love using some kind of RAID solution. So far I haven't found anything > that I really like, and that has been tested. Are you using the mylex > RAID? I looked at it a while ago and it sounded like an interesting solution, > but I first wanted to hear about other people using it. I also understand > that there are some problems with the freebsd utilities handling > large (20 Gig and more) disks, they report negative sizes etc > (32 bit problem?). > I actually think that someone could make nice bucks, by putting together > a FreeBsd box with redundant Power supplies, fans, Scsi controllers etc > and make it a, relatively, cheap NFS appliance. Check out http://www.geli.com, Russ is doing that kind of stuff, though he is aimed more at the compute cluster market. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-scsi Fri Jun 7 20:28:42 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA28196 for freebsd-scsi-outgoing; Fri, 7 Jun 1996 20:28:42 -0700 (PDT) Received: from okjunc.junction.net (root@okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA28183; Fri, 7 Jun 1996 20:28:37 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id TAA09057; Fri, 7 Jun 1996 19:44:17 -0700 Date: Fri, 7 Jun 1996 20:27:42 -0700 (PDT) From: Michael Dillon To: Dror Matalon cc: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read ...other SCSI issues In-Reply-To: Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 7 Jun 1996, Dror Matalon wrote: > >room that you need to put on a sweater when you go in. It also helps to > >use RAID (http://www.mylex.com DAC960SI) because it lessens the physical > >activity on any one drive to some extent. And the special fans to blow air > >across the top of each individual drive. The nice thing about a DAC960 is > >that with a proper hot-swap chassis and RAID 5, replacing a drive doesn't > >shut anything down. > > I'd love using some kind of RAID solution. So far I haven't found anything > that I really like, and that has been tested. Are you using the mylex > RAID? I've used the DAC960E under SCO UNIX with RAID 5 on IBM servers and AST Manhattan servers. It works great, especially when you have a hot swap chassis. > I looked at it a while ago and it sounded like an interesting solution, > but I first wanted to hear about other people using it. I have read at least one account of somebody using the SI version with FreeBSD but it was a while ago and I forget the details. > I actually think that someone could make nice bucks, by putting together > a FreeBsd box with redundant Power supplies, fans, Scsi controllers etc > and make it a, relatively, cheap NFS appliance. Tell your favourite dealer this. SOme I have run across that might be interested are http://www.promox.com http://www.apache.com http://www.justcomp.com http://www.varesearch.com Michael Dillon ISP & Internet Consulting Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com From owner-freebsd-scsi Sat Jun 8 04:15:29 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA25356 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 04:15:29 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [206.117.70.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA25346; Sat, 8 Jun 1996 04:15:26 -0700 (PDT) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id EAA08772; Sat, 8 Jun 1996 04:15:25 -0700 (PDT) Message-Id: <199606081115.EAA08772@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Using two NCR 53C825 controllers blows up? Date: Sat, 08 Jun 1996 04:15:24 -0700 From: Dave Hayes Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In a Pent-133 I am trying to install with two of these NCR controllers in it, there are two disks per controller. When I boot off the floppy, the disks are numbered one way (sd0 thru sd3). Install proceeds happily. Wben I boot off the installed operating system, the controller cards suddenly switch roles, causing sd0 to become sd2, and causing a panic("cannot mount root");. Now I know this is something stupid. It's either me, or the driver. What am I doing wrong? What is it doing wrong? ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet The king arrived at the resturant where Nasrudin had been left in charge. The king ordered an omelette. After his meal, when he saw the check he raised his eyebrows. "Eggs must be very costly here. Are they as scarce as that?" "It is not the eggs, your majesty...it is the visits of kings." From owner-freebsd-scsi Sat Jun 8 07:39:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA21427 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 07:39:54 -0700 (PDT) Received: from zit1.zit.th-darmstadt.de (root@zit1.zit.th-darmstadt.de [130.83.63.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA21411 for ; Sat, 8 Jun 1996 07:39:49 -0700 (PDT) Received: (from petzi@localhost) by zit1.zit.th-darmstadt.de (8.7.5/8.6.9) id QAA00424; Sat, 8 Jun 1996 16:39:17 +0200 (MET DST) Date: Sat, 8 Jun 1996 16:39:17 +0200 (MET DST) From: Michael Beckmann To: scsi@freebsd.org Subject: Fast SCSI-2 = 6 MB/sec ? 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 have just installed a Plextor SCSI CD ROM drive in my machine. I had to find out that it supports only 6 MB/sec. Here is the output from dmesg: ncr0 rev 2 int a irq 10 on pci0:8 ncr0 waiting for scsi devices to settle (ncr0:0:0): 200ns (5 Mb/sec) offset 8. (ncr0:0:0): "IBM OEM DFHSS4F 4141" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 4303MB (8813870 512 byte sectors) (ncr0:2:0): 200ns (5 Mb/sec) offset 8. (ncr0:2:0): "IBM OEM 0662S12 2 23" type 0 fixed SCSI 2 sd1(ncr0:2:0): Direct-Access sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1003MB (2055035 512 byte sectors) (ncr0:3:0): "PLEXTOR CD-ROM PX-4XCE 1.01" type 5 removable SCSI 2 cd0(ncr0:3:0): CD-ROM cd0(ncr0:3:0): FAST SCSI-2 175ns (6 Mb/sec) offset 8. ^^^^^^^^^^ cd0(ncr0:3:0): NOT READY asc:3a,0 Medium not present can't get the size (ncr0:5:0): "HP C1533A 9503" type 1 removable SCSI 2 st0(ncr0:5:0): Sequential-Access st0(ncr0:5:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. density code 0x13, variable blocks, write-enabled I know that the CD ROM drive can never deliver a throughput of 6 MB/sec, (actually, it should deliver around 680 kByte/sec.) but I wonder if the CD ROM drive decreases the performance of the entire bus, thus limiting the bus throughput to 6 MB/sec. Am I right ? Should I be concerned about this and replace the CD drive ? I wonder if my bus is running at 10 MByte/sec at all, because the hard drives report both 5 MB/sec and 10 MB/sec. Michael From owner-freebsd-scsi Sat Jun 8 09:04:18 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA07726 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 09:04:18 -0700 (PDT) Received: from linux4nn.gn.iaf.nl (root@linux4nn.gn.iaf.nl [193.67.144.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA07688; Sat, 8 Jun 1996 09:04:11 -0700 (PDT) Received: from uni4nn.iaf.nl (root@uni4nn.iaf.nl [193.67.144.33]) by linux4nn.gn.iaf.nl (8.6.9/8.6.9) with SMTP id SAA20134; Sat, 8 Jun 1996 18:04:20 +0200 Received: by uni4nn.iaf.nl with UUCP id AA06795 (5.67b/IDA-1.5); Sat, 8 Jun 1996 18:03:55 +0200 Received: by iafnl.es.iaf.nl with UUCP id AA29721 (5.67b/IDA-1.5); Sat, 8 Jun 1996 16:38:25 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.6.12/8.6.6) id QAA04029; Sat, 8 Jun 1996 16:27:02 +0200 From: Wilko Bulte Message-Id: <199606081427.QAA04029@yedi.iaf.nl> X-Organisation: Private FreeBSD site - Arnhem - The Netherlands Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues To: michaelv@HeadCandy.com (Michael L. VanLoon -- HeadCandy.com) Date: Sat, 8 Jun 1996 16:27:02 +0200 (MET DST) Cc: michael@memra.com, hdalog@zipnet.net, dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: <199606070653.XAA08211@MindBender.HeadCandy.com> from "Michael L. VanLoon -- HeadCandy.com" at Jun 6, 96 11:52:53 pm X-Mailer: ELM [version 2.4 PL23] 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 As Michael L. VanLoon -- HeadCandy.com wrote... > > >Maybe Quantum's engineering does something wierd internally and doesn't > >test their drives on a real world activity mix that includes UNIX. > > That would be hard to believe, considering that Quantum drives ship in > some HP Workstations, among others... And in lots of Digital Equipment machines... In general: I have yet to hear of a manufacturer that never has 'junk' drive types every now and then. Wilko _ __________________________________________________________________________ | / o / / _ Wilko Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Private FreeBSD site - Arnhem - The Netherlands -------------------------------------------------------------------------------- From owner-freebsd-scsi Sat Jun 8 11:00:35 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA22025 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 11:00:35 -0700 (PDT) Received: from hda (ip86-max1-fitch.zipnet.net [199.232.245.86]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA22014 for ; Sat, 8 Jun 1996 11:00:31 -0700 (PDT) Received: (from dufault@localhost) by hda (8.6.11/8.6.9) id OAA22866; Sat, 8 Jun 1996 14:05:31 -0400 From: Peter Dufault Message-Id: <199606081805.OAA22866@hda> Subject: Re: Fast SCSI-2 = 6 MB/sec ? To: petzi@zit.th-darmstadt.de (Michael Beckmann) Date: Sat, 8 Jun 1996 14:05:30 -0400 (EDT) Cc: scsi@freebsd.org In-Reply-To: from "Michael Beckmann" at Jun 8, 96 04:39:17 pm Reply-to: hdalog@zipnet.net X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I have just installed a Plextor SCSI CD ROM drive in my machine. I had to > find out that it supports only 6 MB/sec. Here is the output from dmesg: ... > I know that the CD ROM drive can never deliver a throughput of 6 MB/sec, > (actually, it should deliver around 680 kByte/sec.) but I wonder > if the CD ROM drive decreases the performance of the entire bus, thus > limiting the bus throughput to 6 MB/sec. Am I right ? Should I be > concerned about this and replace the CD drive ? No - each device will negotiate its own synchronous rate. The peak burst data rate for that CD will be 6MB, and you have to assume it will will properly disconnect and reconnect to permit effective bus utilization. -- Peter Dufault Real-Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Sat Jun 8 11:15:10 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24593 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 11:15:10 -0700 (PDT) Received: from liliput.tmp.com.br (liliput.tmp.com.br [200.255.204.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA24548; Sat, 8 Jun 1996 11:15:00 -0700 (PDT) Received: (from durval@localhost) by liliput.tmp.com.br (8.7.1/8.6.9) id PAA27548; Sat, 8 Jun 1996 15:08:26 -0300 From: Durval Menezes Message-Id: <199606081808.PAA27548@liliput.tmp.com.br> Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sat, 8 Jun 1996 15:08:25 -0300 (EST) Cc: michaelv@HeadCandy.com, michael@memra.com, hdalog@zipnet.net, dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: <199606081427.QAA04029@yedi.iaf.nl> from "Wilko Bulte" at Jun 8, 96 04:27:02 pm X-Mailer: ELM [version 2.4 PL24] 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 Hello, > > >Maybe Quantum's engineering does something wierd internally and doesn't > > >test their drives on a real world activity mix that includes UNIX. > > > > That would be hard to believe, considering that Quantum drives ship in > > some HP Workstations, among others... > > And in lots of Digital Equipment machines... > > In general: I have yet to hear of a manufacturer that never has 'junk' > drive types every now and then. In the last 6 months, 4 of the sites I do consulting for had disk failures. All of them were using Quantum 2GB Empire drives... Also, I recall that about 1 1/2 years ago Seagate had a disastrous run of the Barracuda drives around (those with firmware revision level less than 12) that locked solid under heavy disk I/O. Best regards, -- Durval Menezes (durval@tmp.com.br, http://www.tmp.com.br/~durval) From owner-freebsd-scsi Sat Jun 8 12:32:01 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA05379 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 12:32:01 -0700 (PDT) Received: from mole.mole.org (marmot.mole.org [204.216.57.191]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA05336; Sat, 8 Jun 1996 12:31:56 -0700 (PDT) Received: (from mail@localhost) by mole.mole.org (8.6.12/8.6.12) id TAA05347; Sat, 8 Jun 1996 19:31:09 GMT Received: from meerkat.mole.org(206.197.192.110) by mole.mole.org via smap (V1.3) id sma005345; Sat Jun 8 19:30:53 1996 Received: (from mrm@localhost) by meerkat.mole.org (8.6.11/8.6.9) id MAA18867; Sat, 8 Jun 1996 12:30:53 -0700 Date: Sat, 8 Jun 1996 12:30:53 -0700 From: "M.R.Murphy" Message-Id: <199606081930.MAA18867@meerkat.mole.org> To: durval@liliput.tmp.com.br, wilko@yedi.iaf.nl Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues Cc: dror@hopf.dnai.com, freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org, hdalog@zipnet.net, michael@memra.com, michaelv@HeadCandy.com Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > In the last 6 months, 4 of the sites I do consulting for had disk failures. > All of them were using Quantum 2GB Empire drives... > I had one of the bad ones. It'd work for a day or so and then hang tight. Quantum replaced it with a good one, no hassle. -- Mike Murphy mrm@Mole.ORG +1 619 598 5874 Better is the enemy of Good From owner-freebsd-scsi Sat Jun 8 13:41:56 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA15772 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 13:41:56 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA15751; Sat, 8 Jun 1996 13:41:50 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id NAA19365; Sat, 8 Jun 1996 13:37:35 -0700 (PDT) Message-Id: <199606082037.NAA19365@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Dave Hayes cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Using two NCR 53C825 controllers blows up? In-reply-to: Your message of Sat, 08 Jun 96 04:15:24 -0700. <199606081115.EAA08772@kachina.jetcafe.org> Date: Sat, 08 Jun 1996 13:37:18 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >In a Pent-133 I am trying to install with two of these NCR >controllers in it, there are two disks per controller. > >When I boot off the floppy, the disks are numbered one way >(sd0 thru sd3). Install proceeds happily. > >Wben I boot off the installed operating system, the controller >cards suddenly switch roles, causing sd0 to become sd2, and >causing a panic("cannot mount root");. What kind of machine is this? I know that Dell, for example, really screwed this up. You could get similar bad behavior under Windows NT (add a new disk on the external controller, which DOS recognizes as D:; reboot into Windows NT and all of a sudden the new disk is C:, and your old C: drive is now D:). The problem there was that the second controller piggy-backed onto the first, and the Dell BIOS artificially made the second controller drives probe after the first controller's. However, the "second" card was actually installed with a lower address or IRQ or something. The only thing that made it come "after" the first was because it was hacked into the BIOS that way. After bootstrapping, NT doesn't use the BIOS anymore, and so would make the "second" controller into the first controller under NT, and the "first" controller would become the second. The drives on the controllers, of course, would then follow the new order. Very very annoying. You might be seeing something similar. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-scsi Sat Jun 8 14:01:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA18193 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 14:01:55 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@[199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA18147; Sat, 8 Jun 1996 14:01:38 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.6.9) with SMTP id NAA19410; Sat, 8 Jun 1996 13:53:35 -0700 (PDT) Message-Id: <199606082053.NAA19410@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Wilko Bulte cc: michael@memra.com, hdalog@zipnet.net, dror@hopf.dnai.com, freebsd-scsi@freebsd.org, freebsd-isp@freebsd.org Subject: Re: ERROR info:747d9d asc:11,0 Unrecovered read error, other SCSI issues In-reply-to: Your message of Sat, 08 Jun 96 16:27:02 +0200. <199606081427.QAA04029@yedi.iaf.nl> Date: Sat, 08 Jun 1996 13:52:04 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >Maybe Quantum's engineering does something wierd internally and doesn't >> >test their drives on a real world activity mix that includes UNIX. >As Michael L. VanLoon -- HeadCandy.com wrote... >> That would be hard to believe, considering that Quantum drives ship in >> some HP Workstations, among others... >And in lots of Digital Equipment machines... >In general: I have yet to hear of a manufacturer that never has 'junk' >drive types every now and then. That has been my experience also, following these lists and Usenet. I think I have heard of bad runs of drives from every major manufacturer. Especially the ones that try to push the limits, like newer 7200rpm drives. The only difference, I think, is that I have heard of Seagate drives failing more than the rest. Personally, I have owned several Quantums. I like them -- they do the job for a good price, and the performance is good. I have had two Quantums fail. One (a ProDrive 425S) was old and had put in several years of good service and hard life running Unix. It didn't surprise me a bit when it finally went. The other was newer (LPS 540S), but was a few months out of warranty. I called them up and they replaced it for free anyway. I have other Quantum drives (a couple TrailBlazer 850S's) that haven't shown any problems. I also have a couple Western Digital IDE drives (a 1.6GB and a 540MB; all my other drives are SCSI) which work very well, and actually seem to run less hot than the other bigger drives. I have two HP drives (both 1GB) which run hot, but which have been quite reliable and quick so far. I also have an old Seagate (500MB) with an Apple decal on it, that probes as a SCSI-1 drive, but still performs pretty well for an older drive, and hasn't shown a single problem so far. So, in Quantum's case, specifically, I wouldn't say that all their drives way more reliable, but I wouldn't say they are way less, either. And, it doesn't bring your data back, but they were very helpful and courteous when I did need to get a drive replaced. Anyone who says "Don't buy X's drives -- they all suck!", I pretty much tune out right away. If a manufacturer truly made only drives that always failed a few months after you bought them, they quite simply wouldn't stay in business. People who can give specific examples and models I take more seriously. Is this thread beat to death, yet? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. ----------------------------------------------------------------------------- From owner-freebsd-scsi Sat Jun 8 16:27:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA05723 for freebsd-scsi-outgoing; Sat, 8 Jun 1996 16:27:25 -0700 (PDT) Received: from kachina.jetcafe.org (kachina.jetcafe.org [206.117.70.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA05714; Sat, 8 Jun 1996 16:27:22 -0700 (PDT) Received: from [127.0.0.1] ([127.0.0.1]) by kachina.jetcafe.org (8.7.5/8.7.3) with SMTP id QAA15662; Sat, 8 Jun 1996 16:27:06 -0700 (PDT) Message-Id: <199606082327.QAA15662@kachina.jetcafe.org> X-Authentication-Warning: kachina.jetcafe.org: Host [127.0.0.1] didn't use HELO protocol To: "Michael L. VanLoon -- HeadCandy.com" Cc: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Using two NCR 53C825 controllers blows up? Date: Sat, 08 Jun 1996 16:27:01 -0700 From: Dave Hayes Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "Michael L. VanLoon -- HeadCandy.com" writes: >What kind of machine is this? Oops, sorry. It's not a name brand per se. It is an "Intel Advanced ZP" motherboard. AMI Bios, and I don't have the revision handy. >However, the "second" card was actually installed with a lower address >or IRQ or something. The only thing that made it come "after" the >first was because it was hacked into the BIOS that way. After >bootstrapping, NT doesn't use the BIOS anymore, and so would make the >"second" controller into the first controller under NT, and the >"first" controller would become the second. The drives on the >controllers, of course, would then follow the new order. Very very >annoying. That's real swell, now how do I find out whether it's doing that? These NCR cards have jumpers to switch between INT A/B/C/D, but I don't think PCI interrupts are as simple as ISA ones. Do I hafta play with the jumpers? ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet Sometimes what a person escapes to is worse than what they escapes from.