From owner-freebsd-scsi Sun Jul 25 11:17:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 4366D14BF2 for ; Sun, 25 Jul 1999 11:17:35 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA21479; Sun, 25 Jul 1999 20:05:35 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id NAA65145; Sun, 25 Jul 1999 13:06:22 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907251106.NAA65145@yedi.iaf.nl> Subject: Re: MAKEDEV In-Reply-To: from Pedro Leitao at "Jul 24, 1999 3:13:14 pm" To: pete@jeeves.poopie.net (Pedro Leitao) Date: Sun, 25 Jul 1999 13:06:22 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Pedro Leitao wrote ... You are looking for the wrong device entry: crw-rw---- 2 root operator 14, 0 May 23 20:28 /dev/rsa0 crw-rw---- 2 root operator 14, 0 May 23 20:28 /dev/rsa0.0 crw-rw---- 1 root operator 14, 4 May 4 22:11 /dev/rsa0.1 crw-rw---- 1 root operator 14, 8 May 4 22:11 /dev/rsa0.2 crw-rw---- 1 root operator 14, 12 May 4 22:11 /dev/rsa0.3 crw-rw---- 1 root wheel 14, 0x20000000 May 4 22:11 /dev/rsa0.ctl > I just added a new scsi backup tape drive on my server. > I compiled the kernel, and the scsi card and tape drive now show > up on startup as ahc0(card) and sa0(drive). > > I want to use that drive, but the device sa0 doesn't show in /dev. > I am trying to make it with ./MAKEDEV sa0, but that just doesn't work. > When I run ./MAKEDEV sa0 , it looks like it runs, but the sa0 device > doesn't show in /dev/ > > How do I make the backup tape drive device so that I can use it? > > thanx in advance for any help.. > _P_ -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 26 18:38: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8833E14BE3 for ; Mon, 26 Jul 1999 18:38:03 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id SAA20001; Mon, 26 Jul 1999 18:36:22 -0700 Date: Mon, 26 Jul 1999 18:36:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" , "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: delay in debugging problems with Qlogic cards caused by... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Part of the problem I've had in debugging this 'hang' condition has turned out to be a failing drive- I finally caught in a situation of: First Error: (da1:isp0:0:1:0): READ(10). CDB: 28 0 0 47 57 aa 0 0 6 0 (da1:isp0:0:1:0): ABORTED COMMAND asc:48,0 (da1:isp0:0:1:0): Initiator detected error message received field replaceable unit: 2 Then the next command fails to do Auto Request Sense: isp0: Auto Request Sense failed for target 1 lun 0 Then there's an infinite (and quiet until I put a debug line in) sequence of: isp0: fdevq 1.0 20c 8, i.e., freeze of Device Queue because the device is always sending back a busy status. This goes on until you reset the machine. It strikes me that an upper bound of busy time would be a good thing to have- it took me several days of hangs in the middle of the night until I finally caught this. You can say that this is "flaky" h/w (and you'd be right), but seems like a good case for defensive programming. Whew. I'm sore fatigued... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 26 23:22: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id C392E14F83 for ; Mon, 26 Jul 1999 23:21:57 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: (qmail 87940 invoked from network); 27 Jul 1999 06:21:44 -0000 Received: from yusufg.portal2.com (qmailr@203.85.226.249) by ns1.portal2.com with SMTP; 27 Jul 1999 06:21:44 -0000 Received: (qmail 14238 invoked by uid 500); 27 Jul 1999 06:21:55 -0000 Date: 27 Jul 1999 06:21:54 -0000 Message-ID: <19990727062154.14237.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-scsi@freebsd.org Subject: Anybody used the Viper II SCSI-SCSI Raid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I was pointed to the Viper II SCSI-SCSI Raid products by a colleague. Has anybody on this list used and what were your experiences Thanks, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 8: 8:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 0FBB314BFF for ; Tue, 27 Jul 1999 08:08:30 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id JAA22101; Tue, 27 Jul 1999 09:08:18 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199907271508.JAA22101@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com Cc: "Justin T. Gibbs" , "Kenneth D. Merry" , scsi@freebsd.org Subject: Re: delay in debugging problems with Qlogic cards caused by... In-reply-to: Your message of "Mon, 26 Jul 1999 18:36:15 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jul 1999 09:08:18 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >It strikes me that an upper bound of busy time would be a good thing to >have- it took me several days of hangs in the middle of the night until I >finally caught this. You can say that this is "flaky" h/w (and you'd be >right), but seems like a good case for defensive programming. Whew. I'm >sore fatigued... What is a good upper bound on the length of time a device should be allowed to report busy? I hate these kinds of questions because you never seem to be able to satisfy everyone. Perhaps 5 minutes is good. One thing I don't understand yet is why this hung up the whole machine. It should have only stuffed up that one device, not all devices in the system. Have you looked at the code path to see where this other bug may be? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 8:14:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 29B4015023 for ; Tue, 27 Jul 1999 08:14:19 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id IAA22253; Tue, 27 Jul 1999 08:14:18 -0700 Date: Tue, 27 Jul 1999 08:14:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: "Kenneth D. Merry" , scsi@freebsd.org Subject: Re: delay in debugging problems with Qlogic cards caused by... In-Reply-To: <199907271508.JAA22101@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >It strikes me that an upper bound of busy time would be a good thing to > >have- it took me several days of hangs in the middle of the night until I > >finally caught this. You can say that this is "flaky" h/w (and you'd be > >right), but seems like a good case for defensive programming. Whew. I'm > >sore fatigued... > > What is a good upper bound on the length of time a device should be allowed > to report busy? > > I hate these kinds of questions because you never seem to be able to > satisfy everyone. Perhaps 5 minutes is good. 5 minutes is probably too short, but I most emphatically agree that it's not an easy question to answer- it's the same level as "How long should a command take" for devices like tapes. It probably should be a per-device property and quirked to override it- mostly so that the da driver can finally do a BDR or *something* to try and get the thing back alive- or at least complain about it... > One thing I don't understand yet is why this hung up the whole machine. > It should have only stuffed up that one device, not all devices in the > system. Have you looked at the code path to see where this other bug > may be? I'm sorry- I was a little inaccurate here- the machine would ping, but because it had the root/swap on it, nothing else could happen. -matt > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 12:38:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dialup124.zpr.uni-koeln.de (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by hub.freebsd.org (Postfix) with ESMTP id 6295C14CC8; Tue, 27 Jul 1999 12:37:55 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: by dialup124.zpr.uni-koeln.de (Postfix, from userid 200) id 38EB5D36; Tue, 27 Jul 1999 20:17:08 +0200 (CEST) Date: Tue, 27 Jul 1999 20:17:07 +0200 From: Stefan Esser To: Thierry.Besancon@lps.ens.fr Cc: scsi@FreeBSD.ORG, Stefan Esser Subject: Re: tagged openings Message-ID: <19990727201707.A371@dialup124.zpr.uni-koeln.de> Reply-To: se@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Thierry.Besancon@lps.ens.fr on Thu, Jul 22, 1999 at 07:06:31PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-07-22 19:06 +0200, Thierry.Besancon@lps.ens.fr wrote: > I'm running FreeBSD 3.1 and whenever my workstation reboots I get the > message : > > (da0:ncr0:0:0:0): tagged openings now 15 > > What does it mean ? There were more tagged commands issued to the drive than it is able to queue. This is not really a problem, the driver will resend the command that has not been accepted and will reduce the number of commands in progress on that drive to one less than the number that caused the failure ... There are quite a number of Quantum drives that had to be entered into the "quirks" table in /sys/cam/cam_xpt.c. You may want to add an entry for your drive, that limits "mintags" to 8 and "maxtags" to 15. See the other Quantum entries for reference. > I must say that I encounter scsi problems with this host but I can't > find where they're coming from. > Generally the machine freezes with messages saying ncr1 is on timeout. > > For example : > > ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). This message indicates a SCSI bus problem. SIST code 0x91 has the following error bits set: 0x80 = phase mismatch 0x10 = reselected by another device 0x01 = parity error This happened during a read (DATA IN phase) after quite some data had already been transfered. While it is bit OK that the driver does not recover from this situation, you may want to check your SCSI cables and terminators to prevent the parity error, which most often is the result of too long a SCSI bus or a bad cable. > Another one : > > ncr1:4:ERROR (81:0) (f-aa-0) (0/3) @ (script 3f0: 48000000) This one is different, but may well also be caused by spurious SCSI bus pulses. The NCR chip reports an illegal instruction error, which most often is caused by too optimistic PCI performance options choosen in the BIOS setup. Some chip-sets could not really support as many active bus-masters as claimed (often only a single bus-master was allowed, and the ISA legacy DMA counted as one). Intel chip-sets should be OK, but I'm not sure whether Ali or VIA Super-7 chip-sets are as reliable. > The precise configuration is 2 Tekram 390F cards + 2 towers of disks > (4 disks each, IBM 9.1 Go), one DLT and one QUANTUM for the system : > > ncr0: rev 0x26 int a irq 9 on pci0.9.0 > ncr1: rev 0x26 int a irq 12 on pci0.10.0 Do you know about save cable length limits for ULTRA-SCSI ? Most of your devices are operating at 20MHz synch. SCSI rate, which means the maximum specified SCSI bus length is *at most* 3m. This value does of course include the internal ribbon cable in your drive boxes, which often is already 90cm in a 2 drive enclosing. If you are not sure that your SCSI bus cable is specified for 20MHz transfer rates, you better consider 1.5m to be the maximum total bus length, or you will see sporadic transfer failures (with a certain probability of undetected data corruption, since parity only detects single bit errors (or rather odd numbers of flipped bits)). > The DLT is daisy chained with one UW tower and I don't use the narrow > connector on the tekram 390F. If I do so, the workstation just freezes > during the boot with an error like : > > ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). This is again the same parity error as in the first message and it points to the real source of your trouble: SCSI bus data corruption. > I must say too that I had the same problems with the same PC in > another configuration : the DLT was the same, the system disk was the > same, all other disks were different and not UW, the scsi cards were > NCR 810. Since the 810 only supported 10MHz rates, you could have a 6m SCSI bus, but only if termination at both sides was OK. There have been a few cheap 810 based SCSI cards with only passive terminators (single in-line resistor packs), though the original NCR and all Symbios cards (as well as Tekram and other high quality cards) always used active terminators, AFAIK. Again: If your cable quality is not up to the spec, you better stay below half the maximum specified for perfect cables and terminators. > The scsi bus goinf timeout is always the one with the DLT. > Might it be faulty ? No, I just think that you violate the Fast-20 specs by daisy chaining the DLT with the UW tower, which may already be at its limits because of the sum of external and internal cables between the SCSI card and the last disk drive in the chain. (External cables are often in the order of 1.5m and I guess that the internal cable will be at least 0.9m long ...) Isn't the DLT4000 a non-wide SCSI device ? If you connect an 8bit SCSI cable to the end of the 16bit SCSI bus, you need quite some extra safety margin (i.e. restrict the total cable length even further). If you really need to connect that number of drives, you may be better off with an Ultra-2 (Fast-40) card with the bus operating in LVD mode. Your IBM DDRS drives may already be U2W, I can't tell from the probe message, at least over here they are the same price in either UW or U2W versions. LVD supports a SCSI bus length of 12.5m, which should satisfy your requirements ;-) But if you have another free PCI slot, you may instead just install another 8bit SCSI card (Sym8100 or 8600) for the DLT (and the boot disk). Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 13: 5: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from excalibur.lps.ens.fr (excalibur.lps.ens.fr [129.199.120.3]) by hub.freebsd.org (Postfix) with ESMTP id 413E314E2C; Tue, 27 Jul 1999 13:04:13 -0700 (PDT) (envelope-from Thierry.Besancon@lps.ens.fr) Received: from (besancon@localhost) by excalibur.lps.ens.fr (8.9.3/jtpda-5.3.1) id WAA25936 ; Tue, 27 Jul 1999 22:01:49 +0200 (MET DST) To: se@FreeBSD.ORG Cc: Thierry.Besancon@lps.ens.fr, scsi@FreeBSD.ORG Subject: Re: tagged openings References: <19990727201707.A371@dialup124.zpr.uni-koeln.de> From: Thierry.Besancon@lps.ens.fr Date: 27 Jul 1999 22:01:48 +0200 In-Reply-To: Stefan Esser's message of Tue, 27 Jul 1999 20:17:07 +0200 Message-ID: Lines: 166 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello A big thanks for your explanation. I was going desperate not to have any answer... Given this host is the fileserver for my all lab, I had to find a solution. So I went quite the way you told. I swapped the old host -- a Pentium 90 based PC with only 4 PCI slots (ethernet, video and 2 scsi cards consumed all the slots) -- for a new one (K6-II 333 MHz) with more PCI slots (5 slots + AGP video). I still couldn't get a NCR810 working with the two tekram. They complain about EEPROM checksum error when the NCR810 is in. There are some notes about that in the notice but their way-out gave nothing. Sh*t. So I went to an old adaptec 2940. I changed the system disk too. I went for a spare UW 2 Go I had for my DEC systems and dropped my old narrow seagate 1 Go ;-) Since this operation -- and long hours at night testing/switching hardware -- everything is ok. My fileserver now runs FreeBSD 3.2, with two tekrams UW and one adaptec 2940. There are just UW disks on the tekrams, all UW disks are in the UW closets, cable length is restricted to the minimum I could go, the DLT is alone on the narrow 2940. The NFS fileserver has been up since 3 days with no freeze and no scsi error. Best regards from Paris at night. Thierry Dixit Stefan Esser (le Tue, 27 Jul 1999 20:17:07 +0200) : >> >> On 1999-07-22 19:06 +0200, Thierry.Besancon@lps.ens.fr wrote: >> > I'm running FreeBSD 3.1 and whenever my workstation reboots I get the >> > message : >> > >> > (da0:ncr0:0:0:0): tagged openings now 15 >> > >> > What does it mean ? >> >> There were more tagged commands issued to the drive than it is able >> to queue. This is not really a problem, the driver will resend the >> command that has not been accepted and will reduce the number of >> commands in progress on that drive to one less than the number that >> caused the failure ... >> >> There are quite a number of Quantum drives that had to be entered into >> the "quirks" table in /sys/cam/cam_xpt.c. You may want to add an entry >> for your drive, that limits "mintags" to 8 and "maxtags" to 15. See the >> other Quantum entries for reference. >> >> > I must say that I encounter scsi problems with this host but I can't >> > find where they're coming from. >> > Generally the machine freezes with messages saying ncr1 is on timeout. >> > >> > For example : >> > >> > ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). >> >> This message indicates a SCSI bus problem. SIST code 0x91 has the >> following error bits set: >> >> 0x80 = phase mismatch >> 0x10 = reselected by another device >> 0x01 = parity error >> >> This happened during a read (DATA IN phase) after quite some data had >> already been transfered. While it is bit OK that the driver does not >> recover from this situation, you may want to check your SCSI cables >> and terminators to prevent the parity error, which most often is the >> result of too long a SCSI bus or a bad cable. >> >> > Another one : >> > >> > ncr1:4:ERROR (81:0) (f-aa-0) (0/3) @ (script 3f0: 48000000) >> >> This one is different, but may well also be caused by spurious SCSI >> bus pulses. The NCR chip reports an illegal instruction error, which >> most often is caused by too optimistic PCI performance options choosen >> in the BIOS setup. Some chip-sets could not really support as many >> active bus-masters as claimed (often only a single bus-master was >> allowed, and the ISA legacy DMA counted as one). Intel chip-sets >> should be OK, but I'm not sure whether Ali or VIA Super-7 chip-sets >> are as reliable. >> >> > The precise configuration is 2 Tekram 390F cards + 2 towers of disks >> > (4 disks each, IBM 9.1 Go), one DLT and one QUANTUM for the system : >> > >> > ncr0: rev 0x26 int a irq 9 on pci0.9.0 >> > ncr1: rev 0x26 int a irq 12 on pci0.10.0 >> >> Do you know about save cable length limits for ULTRA-SCSI ? >> Most of your devices are operating at 20MHz synch. SCSI rate, which >> means the maximum specified SCSI bus length is *at most* 3m. >> This value does of course include the internal ribbon cable in your >> drive boxes, which often is already 90cm in a 2 drive enclosing. >> >> If you are not sure that your SCSI bus cable is specified for 20MHz >> transfer rates, you better consider 1.5m to be the maximum total bus >> length, or you will see sporadic transfer failures (with a certain >> probability of undetected data corruption, since parity only detects >> single bit errors (or rather odd numbers of flipped bits)). >> >> > The DLT is daisy chained with one UW tower and I don't use the narrow >> > connector on the tekram 390F. If I do so, the workstation just freezes >> > during the boot with an error like : >> > >> > ncr1:5: ERROR (0:91) (9-ae-800) (8/13) @ (script 6dc:190001cb). >> >> This is again the same parity error as in the first message and it >> points to the real source of your trouble: SCSI bus data corruption. >> >> > I must say too that I had the same problems with the same PC in >> > another configuration : the DLT was the same, the system disk was the >> > same, all other disks were different and not UW, the scsi cards were >> > NCR 810. >> >> Since the 810 only supported 10MHz rates, you could have a 6m SCSI bus, >> but only if termination at both sides was OK. There have been a few >> cheap 810 based SCSI cards with only passive terminators (single in-line >> resistor packs), though the original NCR and all Symbios cards (as well >> as Tekram and other high quality cards) always used active terminators, >> AFAIK. >> >> Again: If your cable quality is not up to the spec, you better stay below >> half the maximum specified for perfect cables and terminators. >> >> > The scsi bus goinf timeout is always the one with the DLT. >> > Might it be faulty ? >> >> No, I just think that you violate the Fast-20 specs by daisy chaining >> the DLT with the UW tower, which may already be at its limits because >> of the sum of external and internal cables between the SCSI card and >> the last disk drive in the chain. (External cables are often in the >> order of 1.5m and I guess that the internal cable will be at least 0.9m >> long ...) >> >> Isn't the DLT4000 a non-wide SCSI device ? >> >> If you connect an 8bit SCSI cable to the end of the 16bit SCSI bus, >> you need quite some extra safety margin (i.e. restrict the total cable >> length even further). >> >> >> If you really need to connect that number of drives, you may be >> better off with an Ultra-2 (Fast-40) card with the bus operating in >> LVD mode. Your IBM DDRS drives may already be U2W, I can't tell from >> the probe message, at least over here they are the same price in either >> UW or U2W versions. LVD supports a SCSI bus length of 12.5m, which should >> satisfy your requirements ;-) >> >> But if you have another free PCI slot, you may instead just install >> another 8bit SCSI card (Sym8100 or 8600) for the DLT (and the boot disk). >> >> Regards, STefan >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 17:28:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from paert.tse-online.de (paert.tse-online.de [194.97.69.172]) by hub.freebsd.org (Postfix) with SMTP id 7180114BF3 for ; Tue, 27 Jul 1999 17:28:15 -0700 (PDT) (envelope-from ab@paert.tse-online.de) Received: (qmail 57002 invoked by uid 1000); 28 Jul 1999 00:34:09 -0000 Date: Wed, 28 Jul 1999 02:34:08 +0200 From: Andreas Braukmann To: freebsd-scsi@FreeBSD.ORG Subject: Re: Anybody used the Viper II SCSI-SCSI Raid Message-ID: <19990728023408.A56308@paert.tse-online.de> References: <19990727062154.14237.qmail@yusufg.portal2.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <19990727062154.14237.qmail@yusufg.portal2.com>; from Yusuf Goolamabbas on Tue, Jul 27, 1999 at 06:21:54AM -0000 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Tue, Jul 27, 1999 at 06:21:54AM -0000, Yusuf Goolamabbas wrote: > Hi, I was pointed to the Viper II SCSI-SCSI Raid products > by a colleague. Has anybody on this list used and > what were your experiences we use the CMD 5440 (configured for 2 host and 2 disk channels, SCSI UW) and are rather satisfied. But despite of that, ... I would buy a Mylex SCSI2SCSI RAID the next time. The CMDs are (IMHO!) ok in environments with relatively low disk traffic (like in our 'small business' 8 to 10 people doing web-design etc.). But under really high load the Mylex units might perform much better. The bottleneck with the CMDs is, that they only support up to 32 tagged commands. -Andreas -- : TSE GmbH Neue Medien : Gsf: Arne Reuter : : : Hovestrasse 14 : Andreas Braukmann : We do it with : : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP : :--------------------------------------------------------------------: : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 20:38:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tz005.tsuzuki.ne.jp (TZ005.tsuzuki.ne.jp [210.138.98.5]) by hub.freebsd.org (Postfix) with SMTP id 7C777153C9 for ; Tue, 27 Jul 1999 20:38:41 -0700 (PDT) (envelope-from tetsuhiro@tsuzuki.ne.jp) Received: from TZ200.tsuzuki.ne.jp (TZ200.tsuzuki.ne.jp [210.138.98.200]) by tz005.tsuzuki.ne.jp (NTMail 3.02.13) with ESMTP id la004873 for ; Wed, 28 Jul 1999 12:39:16 +0900 Message-ID: <379E7B51.5B982F00@tsuzuki.ne.jp> Date: Wed, 28 Jul 1999 12:38:57 +0900 From: tetsuhiro X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: SYNCHRONIZE CACHE with a vinum volume Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I made a mirrored vinum volue on FreeBSD 3.2R. The volume has a /usr partition and /var links to /usr/var. Ofcause I changed vext.h and move history_log file to a root partition. When I do shutdown the machine, I get following messages: syncing disks... done (da0:ahc0:0:1:0): SYNCHRONIZE CACHE. CDB:35 0 0 0 0 0 0 0 0 0 (da0:ahc0:0:1:0): error code xx at block no. 0 (decimal) where xx differs time by time. it was 59, 66, 5, 85, 1. da0 is: da0: da0: 10.000MB/s transfers (10.000MHz, offset 15) Tagged Queueing Enabled da0: 2048MB (4194304 512 byte sectors: 64H 21S/T 2048C) Should I disable tagged queueing on this old drive? I appreciate your help. Tetsuhiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 20:41:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 99F7915493 for ; Tue, 27 Jul 1999 20:41:31 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA25963; Wed, 28 Jul 1999 13:11:11 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA68085; Wed, 28 Jul 1999 13:11:10 +0930 (CST) Date: Wed, 28 Jul 1999 13:11:10 +0930 From: Greg Lehey To: tetsuhiro Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYNCHRONIZE CACHE with a vinum volume Message-ID: <19990728131110.P66861@freebie.lemis.com> References: <379E7B51.5B982F00@tsuzuki.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <379E7B51.5B982F00@tsuzuki.ne.jp>; from tetsuhiro on Wed, Jul 28, 1999 at 12:38:57PM +0900 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 28 July 1999 at 12:38:57 +0900, tetsuhiro wrote: > I made a mirrored vinum volue on FreeBSD 3.2R. > The volume has a /usr partition and /var links to /usr/var. > Ofcause I changed vext.h and move history_log file to a root > partition. The fact that you're using Vinum doesn't have anything to do with this problem. > When I do shutdown the machine, I get following messages: > > syncing disks... done > (da0:ahc0:0:1:0): SYNCHRONIZE CACHE. CDB:35 0 0 0 0 0 0 0 0 0 > (da0:ahc0:0:1:0): error code xx at block no. 0 (decimal) > > where xx differs time by time. it was 59, 66, 5, 85, 1. > da0 is: > da0: > da0: 10.000MB/s transfers (10.000MHz, offset 15) Tagged Queueing > Enabled > da0: 2048MB (4194304 512 byte sectors: 64H 21S/T 2048C) > > Should I disable tagged queueing on this old drive? I don't think that this will help. I have similar problems here with old drives. Is this a problem for you? Otherwise I'd just ignore it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 27 22:18: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tz005.tsuzuki.ne.jp (TZ005.tsuzuki.ne.jp [210.138.98.5]) by hub.freebsd.org (Postfix) with SMTP id 3C12914C8B for ; Tue, 27 Jul 1999 22:17:57 -0700 (PDT) (envelope-from tetsuhiro@tsuzuki.ne.jp) Received: from TZ200.tsuzuki.ne.jp (TZ200.tsuzuki.ne.jp [210.138.98.200]) by tz005.tsuzuki.ne.jp (NTMail 3.02.13) with ESMTP id na004875 for ; Wed, 28 Jul 1999 14:19:17 +0900 Message-ID: <379E92BF.DC46DC03@tsuzuki.ne.jp> Date: Wed, 28 Jul 1999 14:18:55 +0900 From: tetsuhiro X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: Greg Lehey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SYNCHRONIZE CACHE with a vinum volume References: <379E7B51.5B982F00@tsuzuki.ne.jp> <19990728131110.P66861@freebie.lemis.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks Greg, Greg Lehey wrote: > > On Wednesday, 28 July 1999 at 12:38:57 +0900, tetsuhiro wrote: > > I made a mirrored vinum volue on FreeBSD 3.2R. > > The volume has a /usr partition and /var links to /usr/var. > > Ofcause I changed vext.h and move history_log file to a root > > partition. > > The fact that you're using Vinum doesn't have anything to do with this > problem. > Following procedure suppress error messages. # shutdown now # umount /usr # vinum stop # shutdown -h now This is why I stupitly thought vinum do somthing to do with it. > > When I do shutdown the machine, I get following messages: > > > > syncing disks... done > > (da0:ahc0:0:1:0): SYNCHRONIZE CACHE. CDB:35 0 0 0 0 0 0 0 0 0 > > (da0:ahc0:0:1:0): error code xx at block no. 0 (decimal) > > > > where xx differs time by time. it was 59, 66, 5, 85, 1. > > da0 is: > > da0: > > da0: 10.000MB/s transfers (10.000MHz, offset 15) Tagged Queueing > > Enabled > > da0: 2048MB (4194304 512 byte sectors: 64H 21S/T 2048C) > > > > Should I disable tagged queueing on this old drive? > > I don't think that this will help. I have similar problems here with > old drives. Is this a problem for you? Otherwise I'd just ignore it. > I dont know this will be a problem or not. Isn't it harmless? I appreciate your help. Tetsuhiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 28 12: 2:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 0EB6215279 for ; Wed, 28 Jul 1999 12:02:30 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA25895; Wed, 28 Jul 1999 20:53:33 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA00983; Wed, 28 Jul 1999 20:38:45 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199907281838.UAA00983@yedi.iaf.nl> Subject: Re: SYNCHRONIZE CACHE with a vinum volume In-Reply-To: <19990728131110.P66861@freebie.lemis.com> from Greg Lehey at "Jul 28, 1999 1:11:10 pm" To: grog@lemis.com (Greg Lehey) Date: Wed, 28 Jul 1999 20:38:45 +0200 (CEST) Cc: tetsuhiro@tsuzuki.ne.jp, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Greg Lehey wrote ... > On Wednesday, 28 July 1999 at 12:38:57 +0900, tetsuhiro wrote: > > I made a mirrored vinum volue on FreeBSD 3.2R. > > The volume has a /usr partition and /var links to /usr/var. > > Ofcause I changed vext.h and move history_log file to a root > > partition. > > The fact that you're using Vinum doesn't have anything to do with this > problem. > > > When I do shutdown the machine, I get following messages: > > > > syncing disks... done > > (da0:ahc0:0:1:0): SYNCHRONIZE CACHE. CDB:35 0 0 0 0 0 0 0 0 0 > > (da0:ahc0:0:1:0): error code xx at block no. 0 (decimal) > > > > where xx differs time by time. it was 59, 66, 5, 85, 1. > > da0 is: > > da0: > > da0: 10.000MB/s transfers (10.000MHz, offset 15) Tagged Queueing > > Enabled > > da0: 2048MB (4194304 512 byte sectors: 64H 21S/T 2048C) > > > > Should I disable tagged queueing on this old drive? > > I don't think that this will help. I have similar problems here with > old drives. Is this a problem for you? Otherwise I'd just ignore it. The reason is probably pretty simple: the drive does not know about / support the SYNC CACHE SCSI cmd. -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 28 22: 8: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vulcan.addy.com (vulcan.addy.com [207.239.68.7]) by hub.freebsd.org (Postfix) with ESMTP id 7562514ED2 for ; Wed, 28 Jul 1999 22:08:03 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from your-name (freyes.static.inch.com [207.240.212.43]) by vulcan.addy.com (8.8.5/8.6.12) with SMTP id BAA00880 for ; Thu, 29 Jul 1999 01:05:56 -0400 (EDT) Message-Id: <199907290505.BAA00880@vulcan.addy.com> From: "Francisco Reyes" To: "freebsd-scsi@freebsd.org" Date: Thu, 29 Jul 1999 01:06:14 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Which SCSI controller with non destructive verify? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On a second computer I am putting together I am using a Bus Logic SCSI controller that I picked up on an auction. I was very happy with it until I went to do a verify on a scsi disk and got a warning that this would erase my data. An Adaptec 2940 I have in another compute does verify without formating the media. I am interested on what other SCSI controllers that work on FreeBSD are good choices. The only reason I am looking for alternatives other than Adaptec is purely price. Anyone using Advansys? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 29 5:26:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vulcan.addy.com (vulcan.addy.com [207.239.68.7]) by hub.freebsd.org (Postfix) with ESMTP id 7ABE115142 for ; Thu, 29 Jul 1999 05:26:12 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from your-name (freyes.static.inch.com [207.240.212.43]) by vulcan.addy.com (8.8.5/8.6.12) with SMTP id IAA01939 for ; Thu, 29 Jul 1999 08:25:38 -0400 (EDT) Message-Id: <199907291225.IAA01939@vulcan.addy.com> From: "Francisco Reyes" To: "freebsd-scsi@freebsd.org" Date: Thu, 29 Jul 1999 08:25:17 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: da0:bt timeout Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One of my computers had some SCSI timeouts Jul 28 16:21:16 sanson /kernel: (da0:bt0:0:0:0): CCB 0xc295fb40 - timed out Jul 28 16:21:30 sanson /kernel: bt0: btdone - Attempt to free non-active BCCB 0xc295f3c0 Jul 28 16:21:30 sanson /kernel: (da0:bt0:0:0:0): CCB 0xc295fb40 - timed out Jul 28 16:21:30 sanson /kernel: bt0: No longer in timeout After looking at the archives found different comments on this, but not much of a solution. The controller is a bus logic and the HD an old IBM 5Mb/sec drive (SCSI 1?) I started to have these yesterday. The computer has been up for about a week and most of that time I did not have the error, however I had the controller set to 5Mb/Synchronous for the drive. Changed to async while trying to debug why softupdates where not been installed (I was not building the kernel properly). Will this old drive have less problems as 5Mb/synchronous? Will this be a problem with softupdates? The computer/controller/drive are a combination of a gift from a brother and items picked up from Ebay. Worst case I could replace the HD which I suspect is just plain old, but it would be nice if I could get this to work at least for a few more months before I buy a new drive. Most of the time the timeouts correct themselves with "No longer in timeout" but once it brought down the whole machine. When I first got the drive I did a verify and a format and it did not report any errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 29 19:58:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 2CD9614BF1 for ; Thu, 29 Jul 1999 19:58:31 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-117.dialup.HiWAAY.net [216.180.14.117]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA07138; Thu, 29 Jul 1999 21:58:19 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA73047; Thu, 29 Jul 1999 21:31:07 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199907300231.VAA73047@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Francisco Reyes" , freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Which SCSI controller with non destructive verify? In-reply-to: Message from "Francisco Reyes" of "Thu, 29 Jul 1999 01:06:14 EDT." <199907290505.BAA00880@vulcan.addy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Jul 1999 21:31:07 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Francisco Reyes" writes: > On a second computer I am putting together I am using a Bus > Logic SCSI controller that I picked up on an auction. I was very > happy with it until I went to do a verify on a scsi disk and got > a warning that this would erase my data. What about: # dd if=/dev/sd0 bs=64k of=/dev/null (maybe /dev/sd0c would be a better choice? This is one area I keep getting crossed up when jumping between Solaris, Irix, and FreeBSD.) -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 29 21:18:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vulcan.addy.com (vulcan.addy.com [207.239.68.7]) by hub.freebsd.org (Postfix) with ESMTP id 64B3914D5A for ; Thu, 29 Jul 1999 21:18:47 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from your-name (freyes.static.inch.com [207.240.212.43]) by vulcan.addy.com (8.8.5/8.6.12) with SMTP id AAA20863; Fri, 30 Jul 1999 00:17:58 -0400 (EDT) Message-Id: <199907300417.AAA20863@vulcan.addy.com> From: "Francisco Reyes" To: "David Kelly" , "freebsd-scsi@FreeBSD.ORG" Date: Fri, 30 Jul 1999 00:18:38 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: Which SCSI controller with non destructive verify? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 29 Jul 1999 21:31:07 -0500, David Kelly wrote: >> Bus Logic SCSI controller ... verify ... >> a warning that this would erase my data. > >What about: ># dd if=/dev/sd0 bs=64k of=/dev/null Would this be equivalent to what a "verify" from a controller does? Doesn't the verify function in a controller tries to write? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 30 4: 0:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 6DE1F150A6 for ; Fri, 30 Jul 1999 04:00:31 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from synge.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 30 Jul 1999 12:00:13 +0100 (BST) To: freebsd-scsi@freebsd.org Subject: Bad Quantum Atlas? X-Request-Do: Date: Fri, 30 Jul 1999 12:00:12 +0100 From: David Malone Message-ID: <199907301200.aa14950@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We've just been sent a replacement for a 4GB atlas which died a few weeks ago. The replacement seems flakey too, and seems to go south after a few mminutes of use. Powercycling the drive seems to wake it up. I wonder if the drive is actually bad, or just the firmware. It shows: (ahc0:0:0): "Quantum XP34300 L912" type 0 fixed SCSI 2 on bootup. We have a similar, but working atlas with version L915. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 30 9: 7:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 51B7014C58 for ; Fri, 30 Jul 1999 09:07:50 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA37400; Fri, 30 Jul 1999 10:05:30 -0600 (MDT) (envelope-from ken) Message-Id: <199907301605.KAA37400@panzer.kdm.org> Subject: Re: Bad Quantum Atlas? In-Reply-To: <199907301200.aa14950@salmon.maths.tcd.ie> from David Malone at "Jul 30, 1999 12:00:12 pm" To: dwmalone@maths.tcd.ie (David Malone) Date: Fri, 30 Jul 1999 10:05:30 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David Malone wrote... > We've just been sent a replacement for a 4GB atlas which died a few weeks > ago. The replacement seems flakey too, and seems to go south after a few > mminutes of use. Powercycling the drive seems to wake it up. > > I wonder if the drive is actually bad, or just the firmware. It shows: > > (ahc0:0:0): "Quantum XP34300 L912" type 0 fixed SCSI 2 > > on bootup. We have a similar, but working atlas with version L915. From the snippet above, I assume you're using the old SCSI layer. The new (CAM) SCSI layer can generally handle the sorts of problems you're seeing, although it will be painful at times. (mainly because it takes a minute for things to timeout before we hit the drive with a BDR) Older firmware revisions of the Atlas I and II are known to be bogus. I would suggest you upgrade that disk to the L915 firmware. If the firmware is your problem, the problem should go away after an upgrade to L915. If the problem doesn't go away, there's likely some other problem with the drive. Quantum has firmware images and a loader on their ftp site. You will need a bootable DOS floppy with ASPI drivers for your SCSI controller. I would recommend backing up your disk before you do the upgrade. (I've upgraded a number of Atlas II's, though, and have never lost data.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 30 19: 9:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6F7C315252 for ; Fri, 30 Jul 1999 19:09:55 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-82.dialup.HiWAAY.net [216.180.15.82]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA27680; Fri, 30 Jul 1999 21:08:30 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA77182; Fri, 30 Jul 1999 20:30:41 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199907310130.UAA77182@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Francisco Reyes" Cc: "freebsd-scsi@FreeBSD.ORG" From: David Kelly Subject: Re: Which SCSI controller with non destructive verify? In-reply-to: Message from "Francisco Reyes" of "Fri, 30 Jul 1999 00:18:38 EDT." <199907300417.AAA20863@vulcan.addy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jul 1999 20:30:41 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Francisco Reyes" writes: > On Thu, 29 Jul 1999 21:31:07 -0500, David Kelly wrote: > > >> Bus Logic SCSI controller ... verify ... > >> a warning that this would erase my data. > > > >What about: > ># dd if=/dev/sd0 bs=64k of=/dev/null > > Would this be equivalent to what a "verify" from a controller > does? > Doesn't the verify function in a controller tries to write? If the nondestructive verify function writes then it would scare me. I have seen 3rd party Macintosh utilities that were able to read-write-read verify, or a modified version that wrote something else in the middle, then wrote the original data, and read it again just to be sure. Think FWB's Hard Drive Toolkit does this. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 31 8: 2:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vulcan.addy.com (vulcan.addy.com [207.239.68.7]) by hub.freebsd.org (Postfix) with ESMTP id 92AC915113 for ; Sat, 31 Jul 1999 08:02:17 -0700 (PDT) (envelope-from francisco@natserv.com) Received: from your-name (freyes.static.inch.com [207.240.212.43]) by vulcan.addy.com (8.8.5/8.6.12) with SMTP id LAA19986 for ; Sat, 31 Jul 1999 11:02:16 -0400 (EDT) Message-Id: <199907311502.LAA19986@vulcan.addy.com> From: "Francisco Reyes" To: "FreeBSD SCSI List" Date: Sat, 31 Jul 1999 11:02:08 -0400 Reply-To: "Francisco Reyes" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Controller timeout Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My Buslogic controller keeps timing out with an old 5Mb/sec IBM drive. When I got the drive recently I did a verify and a format. Both reported no problems. All was well until a few days ago when the controller started to time out/recover. Most of the time the system recovers, but it has crashed the machine twice. Re-verified the surface and re-formated. No errors. Is there are setting to increase the timeout wait time for the SCSI drive? Could it be the the drive is not fast enough to keep up with FreeBSD? What setting would be most helpful on trying to reduce this timeout issue Async or Sync 5Mb? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message