From owner-freebsd-scsi Sun Jun 18 7:22:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from southern-software.com (rosetta.thundercat.com [203.37.173.7]) by hub.freebsd.org (Postfix) with SMTP id AC38237BBC5; Sun, 18 Jun 2000 07:22:19 -0700 (PDT) (envelope-from info@southern-software.com) Received: from southern-software.com [198.142.196.124] by southern-software.com (SMTPD32-4.06) id A8BAC73A0392; Sun, 18 Jun 2000 00:22:34 PDT From: info@southern-software.com Reply-To: info@southern-software.com To: info@southern-software.com Subject: Can you please assist ? Date: Sun, 18 Jun 2000 00:23:37 PDT Message-Id: <20000618142219.AC38237BBC5@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ___________________________________________________________ We are a software development company that specializes in security software. For some time now we have been working on developing a Client email program that contains security features never before available. In order for us to make this program the best that it can possibly be, we ask your assistance by taking a few minutes to answer these important questions for us. Which of the following functions do you consider to be important or essential for an email program? For questions 1-7, please rate 1-5. (1 being the least important and 5 being most important). A client email program should have: Question 1: The ability to prevent certain attachments that may possibly be carrying a virus. (This allows you to accept only safe attachments) Importance Rating______ Question 2: Automatic searching for file attachments that have been renamed or tampered with. (Virus senders can rename vbs files to txt files hoping you will open them) Importance Rating______ Question 3: The ability to limit the size of incoming email and attachments. (Reduce time wasted downloading large files, graphics, audio files, jokes, etc.) Importance Rating______ Question 4: The ability to select the size of outgoing emails and attachments. (Saves bandwidth as large files are roughly doubled when transferred by email). Importance Rating______ Question 5: An encrypted Address Book. (This will stop worm viruses sending copies of itself to your clients and/or friends). Importance Rating______ Question 6: The ability to restrict the number of attachments and size of attachments sent or received. And the ability to the restrict types of attachments received. (Gives control to employers and eliminate privacy issues arising). Importance Rating______ Question 7: A viewable log file containing information such as; email deleted without being opened, when email was downloaded, when email was read (opened), if email was forwarded or replied to etc. (Mail management and accountability at a glance) Importance Rating______ Question 8: Has your company been the victim of a computer virus attack? Yes/No ________ Question 9: If yes to question 8, approximately how many hours did it take to fix the problem? Hours ________ Question 10: If an email program was developed with the above security features, would you be interested in trialing a free demonstration version? Yes/No ________ Question 11: What percentage of email traffic is personal email? __________% We sincerely thank you for your time in answering these important questions for us. Sincere thanks, Graeme A. Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 0:34: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from main.tellink.net (main.tellink.net [208.3.160.2]) by hub.freebsd.org (Postfix) with ESMTP id B472B37BB2D for ; Mon, 19 Jun 2000 00:34:02 -0700 (PDT) (envelope-from dwstclair@tellink.net) Received: from [208.3.161.38] (pm-2-22.tellink.net [208.3.161.38]) by main.tellink.net (8.9.0/8.9.0) with ESMTP id DAA16280 for ; Mon, 19 Jun 2000 03:14:38 -0400 (EDT) Mime-Version: 1.0 Message-Id: Date: Mon, 19 Jun 2000 03:14:41 -0400 To: freebsd-scsi@FreeBSD.ORG From: "Douglas W. St.Clair" Subject: SCSI problems installing on HP NetServer LH Pro Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I seem to have a catch 22 situation. I read that the SCSI not found error message I get after trying to install from the most recent Walnut Creek (V4-March 2000) CD-ROM is due to a known problem with the NetServers. What I read was "... the ESIA occupies slot 11 ... [which] collides with PCI address space." Now the recommended solution was to increase the EISA_SLOTS value to 12. and to do this by with the boot -c option in UserConfig. But I'll be darned if I can find the EISA_SLOT option in UserConfig. Nor anyway to adjust it. Please send detailed instructions for accomplishing this feat. Thanks in advance -- END *************** *************** *************** ********** Douglas W. St.Clair Tir na nOg 400 Burton Highway Wilton, NH 03086-5022 USA PH: 603-654-9321 FAX: 603-654-5440 CELL: 617-233-3387 or 617-beef-fur *************** *************** *************** ********** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 12:50:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 4F1A037B641 for ; Mon, 19 Jun 2000 12:50:13 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (lucifer.is.an.elder.of.the.ninth-circle.org [195.38.216.226]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id e5JJo7e47658 for ; Mon, 19 Jun 2000 21:50:07 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA34754 for freebsd-scsi@freebsd.org; Mon, 19 Jun 2000 21:50:06 +0200 (CEST) (envelope-from asmodai) Date: Mon, 19 Jun 2000 21:50:05 +0200 From: Jeroen Ruigrok/Asmodai To: freebsd-scsi@freebsd.org Subject: VCD support Message-ID: <20000619214950.N3659@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there anyone working on this for CAM/SCSI? I found some old patches for ATA VCD support, but I need this for SCSI devices. Any hints/tips/specs I want to look at? Btw, I wasn't sure if I needed -scsi or -multimedia. I guessed that it being a fs support issue with CAM that -scsi was more appropriate. Thanks 'n cheers, -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Necessity relieves us of the ordeal of choice... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 21:37:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ux.accesscom.net (ux.accesscom.net [204.181.176.2]) by hub.freebsd.org (Postfix) with SMTP id E7E8B37B531; Mon, 19 Jun 2000 21:37:37 -0700 (PDT) (envelope-from mlistbsd@icorp.net) Received: from p501.accesscom.net (icorp.net [206.160.4.1]) by ux(smtpd 2.1.3) with SMTP id smtp001463 for ; Tue, 20 Jun 00 04:37:28 GMT (envelope-from ) Message-ID: <394EF4EF.FDBD3928@icorp.net> Date: Mon, 19 Jun 2000 23:37:04 -0500 From: James X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en Mime-Version: 1.0 To: troy@picus.com Cc: freebsd-isp@FreeBSD.ORG Subject: Re: Compaq SmartRAID compatibility issues? X-Priority: 1 (Highest) References: Content-Length: 2807 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Snapshot doesn't work. I booted and installed from 4.0-20000619-STABLE and still NO GO. It went through the entire installation and then reported that no kernel was found. Can ANYONE verify that they have managed to get the Compaq SmartRAID controller running under FreeBSD 4.0? I know that earlier versions were hacked (i.e. 3.4 with wd0 controllers) to work, but I think the ida driver bundled with 4.0 does not support the SmartRaid controllers - it's a shame because it seems to be a minor error - the array is recognized; the filesystem is created successfully but something is messed up during setting up of the kernel - this is driving me crazy - any info anyone can provide would be *greatly* appreciated - and it save someone from getting hit by a flying Compaq (proprietary piece of sh*t) raid controller. Troy Settle wrote: > James, > > I've been flipping through messages pretty quickly the last few days, but I > could swear that someone responded to this same question not too long ago, > suggesting that you (or whomever) use a 4.0 snapshot, rather than the > release. > > Try it, it just might do the trick for you. > > g'luck, > > -Troy > > ** -----Original Message----- > ** From: owner-freebsd-isp@FreeBSD.ORG > ** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of James > ** Sent: Monday, June 19, 2000 12:46 PM > ** To: void@humankind.com > ** Subject: Compaq SmartRAID compatibility issues? > ** > ** > ** > ** I'm still having problems getting this Proliant 3000R with the Compaq > ** 2DH controller to work properly - I've seen some historical messages > ** indicating people have gotten 3.3 to work incorporating a non-bundled > ** IDA driver; I've also heard that this driver is now integrated in with > ** FreeBSD in the later versions. I'm still running into the following > ** issues: > ** > ** * Booting/installing FreeBSD <4.0 does not recognize the drive array > ** * FBSD 4.0 does recognize the array but either: > ** a) crashes with a "makedev returns non-zero" during install > ** b) won't reboot - saying kernel not found > ** c) crashes during post-install config with all forks causing core > ** dumps > ** > ** I can pull out the raid array and reconfigure the disks on Compaq's > ** on-board scsi and it installs and runs perfectly, so I know it's an > ** issue with the raid card. > ** > ** I'm trying to install the os straight to the raid5 array - I really do > ** not want to have to dedicate a non-raid drive just to work around a bug > ** in the OS. Does anyone have any ideas? > ** > ** > ** > ** > ** > ** To Unsubscribe: send mail to majordomo@FreeBSD.org > ** with "unsubscribe freebsd-isp" in the body of the message > ** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 22:49:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ux.accesscom.net (ux.accesscom.net [204.181.176.2]) by hub.freebsd.org (Postfix) with SMTP id 62DF737BAF4; Mon, 19 Jun 2000 22:49:45 -0700 (PDT) (envelope-from mlistbsd@icorp.net) Received: from p501.accesscom.net (icorp.net [206.160.4.1]) by ux(smtpd 2.1.3) with SMTP id smtp014364 for ; Tue, 20 Jun 00 05:48:34 GMT (envelope-from ) Message-ID: <394F0599.2D4EA6C8@icorp.net> Date: Tue, 20 Jun 2000 00:48:10 -0500 From: James X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en Mime-Version: 1.0 To: freebsd-isp@FreeBSD.ORG, freebsd-scsi@freebsd.org Subject: Re: Compaq SmartRAID compatibility issues? Alternatives?? References: <394EFA59.3B59080F@icorp.net> Content-Length: 2577 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anyone recommend a suitable alternative RAID controller that will work in a Compaq Proliant 3000R? I'm having some problems finding compatibility with the hot-swap drive cage's 68-pin open connectors and 40MB/s transfer rate. What is the best non-compaq controller (AMI, DPT, Mylex? What model??) that will work without the nightmares I've had - I'll pay whatever as long as I don't spend long-ass nights trying to hack this proprietary Compaq machine any further than necessary? As a side note, what hardware is ftp.freebsd.org running on? They claim to be running hardware RAID 5 - what controller? I just want something that will work - my brain is sooo fried. On the topic of trying to get the Compaq SmartRAID running on FreeBSD 4.0, I think I'm basically giving up. I am assuming at this time 4.0 does not seem to support the Compaq Smart raid controllers - even though there does seem to be a device driver for this controller, it must not be functioning. I'm open to any ideas on this issue. Here's my situation: Compaq Proliant 3000R with Smart 2HD 2-channel raid scsi The system works fine with the on-board scsi but I cannot install ANY version of FreeBSD from the ide cdrom. I've heard that the Compaq (proprietary piece of crap) raid controller takes over resources reserved for the ide interface and creates compatibility problems - I've also heard there is a "hack" for 3.4 to use the controller at the expense of making all atapi devices inoperable. I've tried everything short of the 3.4 hack - I will reluctantly go back to an older version because it may have more support - ironic when there does seem to be a driver that recognizes the controll but doesn't function properly. I've tried to install 3.3-4.0 via ftp and it fails to produce a kernel on the system. I've tried to install the current 4.0 snapshot - it fails with a message saying "trying to link the kernel but not found - you'll have a very hard time getting the hard drive to boot without a kernel". I can't try any manual copying becuase the holographic shell doesn't have any commands that I can find to mount devices or even copy files - that's probably my ignorance of how to hack the post-install environment - any ideas? In any case, I'll gladly trash this Compaq controller in favor of something which will perform better, handle the Compaq's hot swap drive cage and do at least the 40M/s transfer rate of the scsi plane - money is not an issue as long as it works. Productive suggestions will be rewarded with a very large array of good kharma - guaranteed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 22:58:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 1429837B5D2; Mon, 19 Jun 2000 22:58:54 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA20248; Mon, 19 Jun 2000 22:49:08 -0700 (PDT) Message-Id: <200006200549.WAA20248@implode.root.com> To: James Cc: freebsd-isp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Compaq SmartRAID compatibility issues? Alternatives?? In-reply-to: Your message of "Tue, 20 Jun 2000 00:48:10 CDT." <394F0599.2D4EA6C8@icorp.net> From: David Greenman Reply-To: dg@root.com Date: Mon, 19 Jun 2000 22:49:08 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Can anyone recommend a suitable alternative RAID controller that will work in a Compaq >Proliant 3000R? I'm having some problems finding compatibility with the hot-swap drive >cage's 68-pin open connectors and 40MB/s transfer rate. What is the best non-compaq >controller (AMI, DPT, Mylex? What model??) that will work without the nightmares I've >had - I'll pay whatever as long as I don't spend long-ass nights trying to hack this >proprietary Compaq machine any further than necessary? > >As a side note, what hardware is ftp.freebsd.org running on? They claim to be running >hardware RAID 5 - what controller? I just want something that will work - my brain is >sooo fried. ftp.freebsd.org (actually ftp.freesoftware.com) is using TeraSolutions TSR-2200 RAID storage systems, which have at their heart TeraSolutions TRC-22 RAID controllers. I'd be happy to discuss this with you privately and provide you with a price quote, however I'm headed to the Usenix conference now and won't be back until next week. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 19 23:24:43 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.2]) by hub.freebsd.org (Postfix) with ESMTP id 3444E37BBC8 for ; Mon, 19 Jun 2000 23:24:39 -0700 (PDT) (envelope-from graichen@innominate.de) Received: from mate.bln.innominate.de (cerberus.innominate.de [212.84.234.251]) by hermes.mixx.net (Postfix) with ESMTP id BDB9BF807; Tue, 20 Jun 2000 08:24:28 +0200 (CEST) Received: from h2o.bln.innominate.de (h2o.bln.innominate.de [10.0.0.69]) by mate.bln.innominate.de (Postfix) with ESMTP id 1F0802CA78; Tue, 20 Jun 2000 08:24:28 +0200 (CEST) Received: from localhost (graichen@localhost) by h2o.bln.innominate.de (8.9.3/8.9.3) with ESMTP id IAA04278; Tue, 20 Jun 2000 08:24:50 +0200 X-Authentication-Warning: h2o.bln.innominate.de: graichen owned process doing -bs Date: Tue, 20 Jun 2000 08:24:49 +0200 (CEST) From: Thomas Graichen X-Sender: graichen@h2o.bln.innominate.de Reply-To: thomas.graichen@innominate.de To: Takefumi SAYO Cc: scsi@FreeBSD.ORG Subject: Re: Initio INIC-941 PCI SCSI driver for FreeBSD 4.0-RELEASE In-Reply-To: <20000617174358N.stake@po.shiojiri.ne.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Jun 2000, Takefumi SAYO wrote: > Further investigation is beyond my skill, so I send what I changed from > 'iha-991210.tar.gz' with this mail for SCSI hackers who can fix this > problem correctly and newbusify driver. (Please see attached diff and > Graichen's web page http://www.innominate.org/~tgr/ for iha-991210.tar.gz) > Ofcourse I can test the driver with Initio INIC-941 PCI SCSI adapter > and Matsushita CD-R CW-7502. i have put this diff also to the page and updated the bsd driver database entry accordingly - so the old tarball and the new diff can both be found at http://www.innominate.org/~tgr/projects/FreeBSD/iha/ if anyone is interested t -- thomas.graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 0:28:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 3AD4A37BC41; Tue, 20 Jun 2000 00:28:13 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5K7SBg84931; Tue, 20 Jun 2000 17:28:11 +1000 (EST) Date: Tue, 20 Jun 2000 17:28:10 +1000 From: Nick Slager To: scsi@freebsd.org, questions@freebsd.org Subject: Invalidating pack messages Message-ID: <20000620172810.A84355@albury.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an issue here that is just about to make me start chewing carpet or gnawing furniture in frustration. We build our own BSD servers - always have. Pretty much always with the same hardware. The latest system I've built sporadically spews forth these messages on the console with reckless abandon: (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack Occasionally, I get interspersed with this things like: (da0:ahc0:0:0:0): SCB 0x29 - timed out while idle, SEQADDR == 0x9 (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): no longer in timeout, status = 35b The system is custom built as follows: Asus P3B-F motherboard (both BIOS revisions 1004 and 1005) Adaptec 2940UW-Pro SCSI controller 1 Seagate 18Gb Baracuda drive 128Mb RAM Celeron 466MHz CPU (no overclocking!) I have swapped out, individually, one at a time, each component of the SCSI subsystem - controller, cable, drive and terminator. I'm still getting the error message. I pulled off the 4.0-RELEASE install that was on it and went back to 3.4-RELEASE; same problem. After looking through the archives, I thought the 'Invalidating pack' message was a sure indicator of bad hardware/termination etc. Now I'm not so sure. Anyone have some helpful suggestions? Thanks, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 0:57:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 39C8C37BAEA; Tue, 20 Jun 2000 00:57:24 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA05701; Tue, 20 Jun 2000 00:57:16 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id AAA53614; Tue, 20 Jun 2000 00:54:27 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA28201; Tue, 20 Jun 2000 00:54:07 -0700 (PDT) From: Don Lewis Message-Id: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Date: Tue, 20 Jun 2000 00:54:07 -0700 In-Reply-To: <20000620172810.A84355@albury.net.au> References: <20000620172810.A84355@albury.net.au> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Nick Slager , scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Invalidating pack messages Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 20, 5:28pm, Nick Slager wrote: } Subject: Invalidating pack messages } I have an issue here that is just about to make me start chewing carpet or } gnawing furniture in frustration. } } We build our own BSD servers - always have. Pretty much always with the same } hardware. } } The latest system I've built sporadically spews forth these messages on the } console with reckless abandon: } } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } } Occasionally, I get interspersed with this things like: } } (da0:ahc0:0:0:0): SCB 0x29 - timed out while idle, SEQADDR == 0x9 } (da0:ahc0:0:0:0): Queuing a BDR SCB } (da0:ahc0:0:0:0): no longer in timeout, status = 35b } } The system is custom built as follows: } } Asus P3B-F motherboard (both BIOS revisions 1004 and 1005) } Adaptec 2940UW-Pro SCSI controller } 1 Seagate 18Gb Baracuda drive } 128Mb RAM } Celeron 466MHz CPU (no overclocking!) } } I have swapped out, individually, one at a time, each component of the SCSI } subsystem - controller, cable, drive and terminator. I'm still getting the } error message. You left out the power supply and power cable to the drive. } I pulled off the 4.0-RELEASE install that was on it and went back to } 3.4-RELEASE; same problem. } } After looking through the archives, I thought the 'Invalidating pack' message } was a sure indicator of bad hardware/termination etc. Now I'm not so sure. I believe this error means that the drive has gone away (power failure) and come back (and has told FreeBSD that it has freshly powered up) in such a way that FreeBSD has no way to tell if the drive it was talking to before is the same drive that it is talking to now. To avoid severe filesystem damage, FreeBSD prevents further access to the drive. Imagine the havoc you could cause by unplugging a drive that held a mounted filesystem that was being written to and hooking up another drive containing important data in its place if FreeBSD didn't detect this condition. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 1:52:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from zeus.tassie.net.au (zeus.tassie.net.au [203.57.213.21]) by hub.freebsd.org (Postfix) with ESMTP id B6BBD37BDA4; Tue, 20 Jun 2000 01:52:25 -0700 (PDT) (envelope-from Scott.Donovan@tassie.net.au) Received: from scott (xaviar.live.net.au [203.27.117.243]) by zeus.tassie.net.au (8.8.8/8.8.8) with SMTP id SAA26550; Tue, 20 Jun 2000 18:51:57 +1000 (EST) From: "Scott Donovan" To: "Don Lewis" , "Nick Slager" , , Subject: RE: Invalidating pack messages Date: Tue, 20 Jun 2000 18:51:54 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 In-reply-to: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Importance: Normal Disposition-Notification-To: "Scott Donovan" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org } } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } (da0:ahc0:0:0:0): Invalidating pack } 1 Seagate 18Gb Baracuda drive > I believe this error means that the drive has gone away (power failure) > and come back (and has told FreeBSD that it has freshly powered up) in > such a way that FreeBSD has no way to tell if the drive it was talking > to before is the same drive that it is talking to now. To avoid severe > filesystem damage, FreeBSD prevents further access to the drive. We are having exactly the same problem with these drive at the moment. I can assure the drive remains powered. Perhaps this isa manufacturing fault ? However we brought around 8 of these drives only 4 went to freebsd machines these all play up. The ones on the NT 4.0 systems don't show any hickups ??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 2: 0: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 86EC337BDA4 for ; Tue, 20 Jun 2000 02:00:02 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5K8xq286360; Tue, 20 Jun 2000 18:59:52 +1000 (EST) Date: Tue, 20 Jun 2000 18:59:52 +1000 From: Nick Slager To: Don Lewis Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000620185952.A86159@albury.net.au> References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006200754.AAA28201@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Tue, Jun 20, 2000 at 12:54:07AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > On Jun 20, 5:28pm, Nick Slager wrote: > } > } I have swapped out, individually, one at a time, each component of the SCSI > } subsystem - controller, cable, drive and terminator. I'm still getting the > } error message. > > You left out the power supply and power cable to the drive. A good point; I'll swap power supplies tomorrow. Thanks for the suggestion. > I believe this error means that the drive has gone away (power failure) > and come back (and has told FreeBSD that it has freshly powered up) in > such a way that FreeBSD has no way to tell if the drive it was talking > to before is the same drive that it is talking to now. To avoid severe > filesystem damage, FreeBSD prevents further access to the drive. > > Imagine the havoc you could cause by unplugging a drive that held a > mounted filesystem that was being written to and hooking up another > drive containing important data in its place if FreeBSD didn't detect > this condition. Yes, this would certainly be sub-optimal. The sporadic nature of this fault has been particularly frustrating. Often the system will run fine, all the time doing hefty reads/writes to various parts of the filesystem, for a whole day before it dies. One more thing I meant to mention in the original post: when the error occurs the small green LED on the front of the drive flashes in a peculiar pattern. It's hard to record exactly *what* the pattern is, as I have no reference point and the sequence is fairly lengthy. Seagate support insist they have no idea what the pattern represents, and "not even an engineer would know". Needless to say, it's not in the manual for the drive. :-( Has anyone come across a reference to the LED flash patterns on Seagate drives? Regards, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 2: 2:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 676B137BDC1 for ; Tue, 20 Jun 2000 02:02:46 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5K92hb86421; Tue, 20 Jun 2000 19:02:43 +1000 (EST) Date: Tue, 20 Jun 2000 19:02:43 +1000 From: Nick Slager To: Scott Donovan Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000620190243.B86159@albury.net.au> References: <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from Scott.Donovan@tassie.net.au on Tue, Jun 20, 2000 at 06:51:54PM +1000 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Scott Donovan (Scott.Donovan@tassie.net.au): > > I believe this error means that the drive has gone away (power failure) > > and come back (and has told FreeBSD that it has freshly powered up) in > > such a way that FreeBSD has no way to tell if the drive it was talking > > to before is the same drive that it is talking to now. To avoid severe > > filesystem damage, FreeBSD prevents further access to the drive. > > We are having exactly the same problem with these drive at the moment. I can > assure the drive remains powered. Perhaps this isa manufacturing fault ? > However we brought around 8 of these drives only 4 went to freebsd machines > these all play up. The ones on the NT 4.0 systems don't show any hickups ??? Hi Scott, Interesting. When I'm at work tommorow I'll grab exact model and serial numbers for a comparison. Regards, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 7:48:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 55EA237BA12; Tue, 20 Jun 2000 07:48:30 -0700 (PDT) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id 7B7EB62D60; Wed, 21 Jun 2000 00:18:23 +0930 (CST) Date: Wed, 21 Jun 2000 00:18:23 +0930 From: Ian West To: Nick Slager Cc: scsi@freebsd.org, questions@freebsd.org Subject: Re: Invalidating pack messages Message-ID: <20000621001823.A32878@rose.niw.com.au> References: <20000620172810.A84355@albury.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000620172810.A84355@albury.net.au>; from nicks@albury.net.au on Tue, Jun 20, 2000 at 05:28:10PM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 20, 2000 at 05:28:10PM +1000, Nick Slager wrote: > I have an issue here that is just about to make me start chewing carpet or > gnawing furniture in frustration. > > We build our own BSD servers - always have. Pretty much always with the same > hardware. > > The latest system I've built sporadically spews forth these messages on the > console with reckless abandon: > > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > (da0:ahc0:0:0:0): Invalidating pack > > Occasionally, I get interspersed with this things like: > > (da0:ahc0:0:0:0): SCB 0x29 - timed out while idle, SEQADDR == 0x9 > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): no longer in timeout, status = 35b > > The system is custom built as follows: > > Asus P3B-F motherboard (both BIOS revisions 1004 and 1005) > Adaptec 2940UW-Pro SCSI controller > 1 Seagate 18Gb Baracuda drive > 128Mb RAM > Celeron 466MHz CPU (no overclocking!) > > I have swapped out, individually, one at a time, each component of the SCSI > subsystem - controller, cable, drive and terminator. I'm still getting the > error message. > > I pulled off the 4.0-RELEASE install that was on it and went back to > 3.4-RELEASE; same problem. > > After looking through the archives, I thought the 'Invalidating pack' message > was a sure indicator of bad hardware/termination etc. Now I'm not so sure. > > Anyone have some helpful suggestions? > > Thanks, > > > Nick. > > -- > From a Sun Microsystems bug report (#4102680): > "Workaround: don't pound on the mouse like a wild monkey." > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message I think it might be a driver issue with freebsd. I have a very new system with 2 * 18G Seagate Cheetah drives connected to an Adaptec 29160 controller which was showing identical symptoms. I loaded OpenBSD to check if it was hardware or software (grasping at straws) and it has been running flat out for days since. (Looping make build, kind of like make world). Justin Gibbs did mention that he had some ideas, and some code which might be available after usenix, although I think this might be more specific to the 29160 set. There is no sign of any problem at all under OpenBSD, although the throughput seems to be less. (~26Mbytes/sec as opposed to ~34MBytes/Sec) Just an extra data point, it might not be hardware at all. Cheers Ian. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 11: 0:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from staff.nyi.net (staff.nyi.net [204.248.157.16]) by hub.freebsd.org (Postfix) with SMTP id 1D01F37BF13 for ; Tue, 20 Jun 2000 11:00:15 -0700 (PDT) (envelope-from javier@nyi.net) Received: (qmail 72593 invoked by uid 1004); 20 Jun 2000 17:57:48 -0000 Message-ID: <20000620175748.72592.qmail@staff.nyi.net> References: <394EFA59.3B59080F@icorp.net> <394F0599.2D4EA6C8@icorp.net> In-Reply-To: <394F0599.2D4EA6C8@icorp.net> From: "javier" To: James Cc: freebsd-isp@FreeBSD.ORG, freebsd-scsi@freebsd.org Subject: Re: Compaq SmartRAID compatibility issues? Alternatives?? Date: Tue, 20 Jun 2000 17:57:48 GMT 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 Running a 51gig raid 5 arraid here on a compaq proliant 3000 with the smart array controller with no problems.. ( they make really good dev servers) i think you are missing one step after you install, see, the kernel in the boot floppy contains supports for the ida device, but the kernel that's installed during the sys install, doesnot. So what you have to do is this: Install systems as normal with your boot floppy using a snapshot form releng4.freebsd.org after is fully done, DONOT REBOOT hit alt+F4 and goto to a console cd /usr/src/sys/i386/conf and compile yourself a custom kernel with the ida device included. go ahead and reboot now it should work so you believe me: bfm# uname -a FreeBSD bfm.ops.about.com 4.0-20000619-STABLE FreeBSD 4.0-20000619-STABLE #0: Fri Mar 19 11:01:47 GMT 1999 root@bfm.ops.about.com:/usr/src/sys/compile/custom i386 bfm# df -k Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/idad0s1a 1190783 37783 1057738 3% / /dev/idad0s1g 44625658 14 41055592 0% /home /dev/idad0s1e 3175982 752007 2169897 26% /usr /dev/idad0s1f 1488607 7189 1362330 1% /var procfs 4 4 0 100% /proc more info at : http://www.seeberg.dk/freebsd/idaraid/ hope this helps ;) James writes: > > Can anyone recommend a suitable alternative RAID controller that will work in a Compaq > Proliant 3000R? I'm having some problems finding compatibility with the hot-swap drive > cage's 68-pin open connectors and 40MB/s transfer rate. What is the best non-compaq > controller (AMI, DPT, Mylex? What model??) that will work without the nightmares I've > had - I'll pay whatever as long as I don't spend long-ass nights trying to hack this > proprietary Compaq machine any further than necessary? > > As a side note, what hardware is ftp.freebsd.org running on? They claim to be running > hardware RAID 5 - what controller? I just want something that will work - my brain is > sooo fried. > > On the topic of trying to get the Compaq SmartRAID running on FreeBSD 4.0, I think I'm > basically giving up. > > I am assuming at this time 4.0 does not seem to support the Compaq Smart raid controllers > - even though there does seem to be a device driver for this controller, it must not be > functioning. > > I'm open to any ideas on this issue. Here's my situation: > > Compaq Proliant 3000R with Smart 2HD 2-channel raid scsi > > The system works fine with the on-board scsi but I cannot install ANY version of FreeBSD > from the ide cdrom. I've heard that the Compaq (proprietary piece of crap) raid > controller takes over resources reserved for the ide interface and creates compatibility > problems - I've also heard there is a "hack" for 3.4 to use the controller at the expense > of making all atapi devices inoperable. I've tried everything short of the 3.4 hack - I > will reluctantly go back to an older version because it may have more support - ironic > when there does seem to be a driver that recognizes the controll but doesn't function > properly. > > I've tried to install 3.3-4.0 via ftp and it fails to produce a kernel on the system. > I've tried to install the current 4.0 snapshot - it fails with a message saying "trying > to link the kernel but not found - you'll have a very hard time getting the hard drive to > boot without a kernel". I can't try any manual copying becuase the holographic shell > doesn't have any commands that I can find to mount devices or even copy files - that's > probably my ignorance of how to hack the post-install environment - any ideas? > > In any case, I'll gladly trash this Compaq controller in favor of something which will > perform better, handle the Compaq's hot swap drive cage and do at least the 40M/s > transfer rate of the scsi plane - money is not an issue as long as it works. Productive > suggestions will be rewarded with a very large array of good kharma - guaranteed. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 11:33:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from staff.nyi.net (staff.nyi.net [204.248.157.16]) by hub.freebsd.org (Postfix) with SMTP id C592E37BCAE for ; Tue, 20 Jun 2000 11:33:02 -0700 (PDT) (envelope-from javier@nyi.net) Received: (qmail 73404 invoked by uid 1004); 20 Jun 2000 18:30:35 -0000 Message-ID: <20000620183035.73403.qmail@staff.nyi.net> References: <394EFA59.3B59080F@icorp.net> <394F0599.2D4EA6C8@icorp.net> <20000620175748.72592.qmail@staff.nyi.net> In-Reply-To: <20000620175748.72592.qmail@staff.nyi.net> From: "javier" To: James Cc: freebsd-isp@FreeBSD.ORG, freebsd-scsi@freebsd.org Subject: Re: Compaq SmartRAID compatibility issues? Alternatives?? Date: Tue, 20 Jun 2000 18:30:35 GMT 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 Forgot to include.... ida0: port 0x5000-0x50ff mem 0xf0000000-0xf7ffffff,0xfe9fff00-0xfe9fffff irq 11 at devi ce 0.0 on pci1 ida0: drives=1 firm_rev=2.08 idad0: on ida0 idad0: 52063MB (106626720 sectors), blocksize=512 javier writes: > > Running a 51gig raid 5 arraid here on a compaq proliant 3000 with the smart > array controller with no problems.. ( they make really good dev servers) > > > > i think you are missing one step after you install, see, the kernel in the > boot floppy contains supports for the ida device, but the kernel that's > installed during the sys install, doesnot. > > So what you have to do is this: > > Install systems as normal with your boot floppy using a snapshot form > releng4.freebsd.org > after is fully done, > DONOT REBOOT > hit alt+F4 and goto to a console > > cd /usr/src/sys/i386/conf > and compile yourself a custom kernel with the ida device included. > go ahead and reboot > now it should work > > so you believe me: > > bfm# uname -a > FreeBSD bfm.ops.about.com 4.0-20000619-STABLE FreeBSD 4.0-20000619-STABLE > #0: Fri Mar 19 11:01:47 GMT 1999 > root@bfm.ops.about.com:/usr/src/sys/compile/custom i386 > bfm# df -k > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/idad0s1a 1190783 37783 1057738 3% / > /dev/idad0s1g 44625658 14 41055592 0% /home > /dev/idad0s1e 3175982 752007 2169897 26% /usr > /dev/idad0s1f 1488607 7189 1362330 1% /var > procfs 4 4 0 100% /proc > > > more info at : > > http://www.seeberg.dk/freebsd/idaraid/ > > > hope this helps ;) > James writes: > > > > > Can anyone recommend a suitable alternative RAID controller that will work in a Compaq > > Proliant 3000R? I'm having some problems finding compatibility with the hot-swap drive > > cage's 68-pin open connectors and 40MB/s transfer rate. What is the best non-compaq > > controller (AMI, DPT, Mylex? What model??) that will work without the nightmares I've > > had - I'll pay whatever as long as I don't spend long-ass nights trying to hack this > > proprietary Compaq machine any further than necessary? > > > > As a side note, what hardware is ftp.freebsd.org running on? They claim to be running > > hardware RAID 5 - what controller? I just want something that will work - my brain is > > sooo fried. > > > > On the topic of trying to get the Compaq SmartRAID running on FreeBSD 4.0, I think I'm > > basically giving up. > > > > I am assuming at this time 4.0 does not seem to support the Compaq Smart raid controllers > > - even though there does seem to be a device driver for this controller, it must not be > > functioning. > > > > I'm open to any ideas on this issue. Here's my situation: > > > > Compaq Proliant 3000R with Smart 2HD 2-channel raid scsi > > > > The system works fine with the on-board scsi but I cannot install ANY version of FreeBSD > > from the ide cdrom. I've heard that the Compaq (proprietary piece of crap) raid > > controller takes over resources reserved for the ide interface and creates compatibility > > problems - I've also heard there is a "hack" for 3.4 to use the controller at the expense > > of making all atapi devices inoperable. I've tried everything short of the 3.4 hack - I > > will reluctantly go back to an older version because it may have more support - ironic > > when there does seem to be a driver that recognizes the controll but doesn't function > > properly. > > > > I've tried to install 3.3-4.0 via ftp and it fails to produce a kernel on the system. > > I've tried to install the current 4.0 snapshot - it fails with a message saying "trying > > to link the kernel but not found - you'll have a very hard time getting the hard drive to > > boot without a kernel". I can't try any manual copying becuase the holographic shell > > doesn't have any commands that I can find to mount devices or even copy files - that's > > probably my ignorance of how to hack the post-install environment - any ideas? > > > > In any case, I'll gladly trash this Compaq controller in favor of something which will > > perform better, handle the Compaq's hot swap drive cage and do at least the 40M/s > > transfer rate of the scsi plane - money is not an issue as long as it works. Productive > > suggestions will be rewarded with a very large array of good kharma - guaranteed. > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-isp" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message -- MMM \|/ www __^__ (o o) @ @ (O-O) /(o o)\ -ooO-(_)-Ooo---oOO-(_)-OOo---oOO--(_)--OOo---oOO==(_)==OOo Javier A. Frias Sr. System Administrator The New York Internet Company 20 Exchange Place 21st Floor New York, N.Y. 10005 "Error #152 - Windows not found: (C)heer (P)arty (D)ance" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 11:57:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (term29.conference.usenix.org [209.179.127.29]) by hub.freebsd.org (Postfix) with ESMTP id E1F3037BFDD for ; Tue, 20 Jun 2000 11:57:19 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: (from gibbs@localhost) by caspian.plutotech.com (8.9.3/8.9.1) id MAA00629; Tue, 20 Jun 2000 12:57:46 -0600 (MDT) (envelope-from gibbs) Date: Tue, 20 Jun 2000 12:57:46 -0600 (MDT) Message-Id: <200006201857.MAA00629@caspian.plutotech.com> From: "Justin T. Gibbs" To: "NandaKumar P.K." Cc: scsi@FreeBSD.org Subject: Re: Reset device and reset bus is not working X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <20000616050010.7958.qmail@web1903.mail.yahoo.com> User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/5.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000616050010.7958.qmail@web1903.mail.yahoo.com> you wrote: > > Is it necessary to complete these commands in the > request function (_action ) itself ? As Ken already mentioned, there was a bug with device resets. The CAM system does expect a bus reset to be non-blocking. In otherwords, you must complete a bus reset before the call into your action routine returns. Device resets, which require the initiator to actually aquire a nexus to the device and has a large chance of failure is an asynchronous command. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 16:42:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from karenium.kjsl.com (kjsl-home-net.kjsl.com [206.55.236.202]) by hub.freebsd.org (Postfix) with ESMTP id 30B8B37C108 for ; Tue, 20 Jun 2000 16:42:55 -0700 (PDT) (envelope-from javier@karenium.kjsl.com) Received: (from javier@localhost) by karenium.kjsl.com (8.9.3/8.9.3) id QAA00354; Tue, 20 Jun 2000 16:42:53 -0700 (PDT) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14672.380.691352.782821@karenium.kjsl.com> Date: Tue, 20 Jun 2000 16:42:52 -0700 (PDT) To: freebsd-scsi@freebsd.org Subject: Tape drive oddities X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I recently picked up a Digital DLT drive (the exact model number is TH4AA). I tried it with FreeBSD 3.4-STABLE and an Adaptec AHA1510A and it works fine. I then switched to an AHA 1542C and things got funky. No matter what argument I used for -b, writes always failed one byte short of the block size. For example, if I did: tar -c -b 10240 /usr I would get an error message about only 10239 bytes being written. I put the AHA1510A back on, and the thing works fine. Any ideas? -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 16:49: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 99C3737BBC6 for ; Tue, 20 Jun 2000 16:48:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA18603; Tue, 20 Jun 2000 16:48:49 -0700 Date: Tue, 20 Jun 2000 16:48:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Javier Henderson Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities In-Reply-To: <14672.380.691352.782821@karenium.kjsl.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 Not a tape driver problem- sounds like either your termination is wrong on the 1542C (check via bios), or that there's something not quite right with the adaptec 1542 driver. On Tue, 20 Jun 2000, Javier Henderson wrote: > Greetings, > > I recently picked up a Digital DLT drive (the exact > model number is TH4AA). > > I tried it with FreeBSD 3.4-STABLE and an Adaptec AHA1510A and > it works fine. > > I then switched to an AHA 1542C and things got funky. No > matter what argument I used for -b, writes always failed one byte > short of the block size. For example, if I did: > > tar -c -b 10240 /usr > > I would get an error message about only 10239 bytes being > written. > > I put the AHA1510A back on, and the thing works fine. > > Any ideas? > > > -jav > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 16:51:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from karenium.kjsl.com (kjsl-home-net.kjsl.com [206.55.236.202]) by hub.freebsd.org (Postfix) with ESMTP id C578137BD80 for ; Tue, 20 Jun 2000 16:51:49 -0700 (PDT) (envelope-from javier@karenium.kjsl.com) Received: (from javier@localhost) by karenium.kjsl.com (8.9.3/8.9.3) id QAA00483; Tue, 20 Jun 2000 16:51:47 -0700 (PDT) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14672.915.155185.555480@karenium.kjsl.com> Date: Tue, 20 Jun 2000 16:51:47 -0700 (PDT) To: mjacob@feral.com Cc: Javier Henderson , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities In-Reply-To: References: <14672.380.691352.782821@karenium.kjsl.com> X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > Not a tape driver problem- sounds like either your termination is wrong on the > 1542C (check via bios), or that there's something not quite right with the > adaptec 1542 driver. The termination is set right on both the 1510 and the 1542. -jav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 16:56:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id EC68537B5A7 for ; Tue, 20 Jun 2000 16:56:14 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA18633; Tue, 20 Jun 2000 16:53:02 -0700 Date: Tue, 20 Jun 2000 16:52:37 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Javier Henderson Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities In-Reply-To: <14672.915.155185.555480@karenium.kjsl.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 > Matthew Jacob writes: > > > > Not a tape driver problem- sounds like either your termination is wrong on the > > 1542C (check via bios), or that there's something not quite right with the > > adaptec 1542 driver. > > The termination is set right on both the 1510 and the 1542. Well, then.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 20 21:36:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 4DD1337B935 for ; Tue, 20 Jun 2000 21:36:22 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5L4a9L03638; Wed, 21 Jun 2000 14:36:09 +1000 (EST) Date: Wed, 21 Jun 2000 14:36:09 +1000 From: Nick Slager To: Don Lewis Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000621143609.A3012@albury.net.au> References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006200754.AAA28201@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Tue, Jun 20, 2000 at 12:54:07AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > } I have swapped out, individually, one at a time, each component of the SCSI > } subsystem - controller, cable, drive and terminator. I'm still getting the > } error message. > > You left out the power supply and power cable to the drive. I pulled out the power supply this morning, and replaced it with a brand new unit. The system has just crashed again with the 'Invalidating pack' error messages. > } After looking through the archives, I thought the 'Invalidating pack' message > } was a sure indicator of bad hardware/termination etc. Now I'm not so sure. > > I believe this error means that the drive has gone away (power failure) > and come back (and has told FreeBSD that it has freshly powered up) in > such a way that FreeBSD has no way to tell if the drive it was talking > to before is the same drive that it is talking to now. To avoid severe > filesystem damage, FreeBSD prevents further access to the drive. If this is the case (and I'm not doubting what you say), what else could cause this problem? Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 21 4: 5:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from web1902.mail.yahoo.com (web1902.mail.yahoo.com [128.11.23.51]) by hub.freebsd.org (Postfix) with SMTP id BA0C537BD79 for ; Wed, 21 Jun 2000 04:05:50 -0700 (PDT) (envelope-from p_k_nandan@yahoo.com) Received: (qmail 23929 invoked by uid 60001); 21 Jun 2000 11:05:50 -0000 Message-ID: <20000621110550.23928.qmail@web1902.mail.yahoo.com> Received: from [203.197.190.137] by web1902.mail.yahoo.com; Wed, 21 Jun 2000 04:05:50 PDT Date: Wed, 21 Jun 2000 04:05:50 -0700 (PDT) From: "NandaKumar P.K." Subject: Unable to mount root device To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am testing my HBA driver (FreeBSD 3.4) with the DELL server. The DELL server has got an adaptec controller and five SCSI disks and one tape drive. My first disk was seen as da0 but when i added my controller which was having a single disk that was seen as da0 and system says unable to mount root device. The da0 was on scsibus0. I tried the same experiment with the Q-Logic adpter and it also gives the same result. In both cases i tried the following line in the configuration file. controller scbus1 at isp0. But still the drive put on the Q-Logic adapter was taken on scsibus0. How is this clash avoided ? Regards, Nandan __________________________________________________ Do You Yahoo!? Send instant messages with Yahoo! Messenger. http://im.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 21 12: 3:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id 752DB37B9F9 for ; Wed, 21 Jun 2000 12:03:18 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000621060834.BLJK18262.relay02@chello.nl>; Wed, 21 Jun 2000 08:08:34 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id IAA81499; Wed, 21 Jun 2000 08:08:48 +0200 (CEST) (envelope-from wkb) Date: Wed, 21 Jun 2000 08:08:48 +0200 From: Wilko Bulte To: Matthew Jacob Cc: Javier Henderson , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities Message-ID: <20000621080848.A81471@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <14672.380.691352.782821@karenium.kjsl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Tue, Jun 20, 2000 at 04:48:23PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jun 20, 2000 at 04:48:23PM -0700, Matthew Jacob wrote: > Not a tape driver problem- sounds like either your termination is wrong on the > 1542C (check via bios), or that there's something not quite right with the > adaptec 1542 driver. A repeatable off-by-1 error due to termination problems? I doubt it to be honest.. Sounds more like driver problems to me > On Tue, 20 Jun 2000, Javier Henderson wrote: > > > Greetings, > > > > I recently picked up a Digital DLT drive (the exact > > model number is TH4AA). > > > > I tried it with FreeBSD 3.4-STABLE and an Adaptec AHA1510A and > > it works fine. > > > > I then switched to an AHA 1542C and things got funky. No > > matter what argument I used for -b, writes always failed one byte > > short of the block size. For example, if I did: > > > > tar -c -b 10240 /usr > > > > I would get an error message about only 10239 bytes being > > written. > > > > I put the AHA1510A back on, and the thing works fine. -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 21 12: 6: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 86F4037C055; Wed, 21 Jun 2000 12:05:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA20861; Wed, 21 Jun 2000 12:05:53 -0700 Date: Wed, 21 Jun 2000 12:05:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: Javier Henderson , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities In-Reply-To: <20000621080848.A81471@freebie.wbnet> 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 > > Not a tape driver problem- sounds like either your termination is wrong on the > > 1542C (check via bios), or that there's something not quite right with the > > adaptec 1542 driver. > > A repeatable off-by-1 error due to termination problems? I doubt it to be > honest.. Sounds more like driver problems to me > Yes, I'd usually agree. Although in SYNC mode for older hardware, a missing 'last byte' was indeed often a bad cabling problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 21 12: 8:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id D094737C06D; Wed, 21 Jun 2000 12:08:26 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000621190917.KJRC24430.relay01@chello.nl>; Wed, 21 Jun 2000 21:09:17 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id VAA00624; Wed, 21 Jun 2000 21:08:24 +0200 (CEST) (envelope-from wkb) Date: Wed, 21 Jun 2000 21:08:24 +0200 From: Wilko Bulte To: Matthew Jacob Cc: wilko@FreeBSD.ORG, Javier Henderson , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities Message-ID: <20000621210824.F238@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <20000621080848.A81471@freebie.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from mjacob@feral.com on Wed, Jun 21, 2000 at 12:05:24PM -0700 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jun 21, 2000 at 12:05:24PM -0700, Matthew Jacob wrote: > > > Not a tape driver problem- sounds like either your termination is wrong on the > > > 1542C (check via bios), or that there's something not quite right with the > > > adaptec 1542 driver. > > > > A repeatable off-by-1 error due to termination problems? I doubt it to be > > honest.. Sounds more like driver problems to me > > > > Yes, I'd usually agree. Although in SYNC mode for older hardware, a missing > 'last byte' was indeed often a bad cabling problem. Right, and Adaptec (the older ones) had a reputation for being sensitive to cabling (shiver, like the 1740) -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 21 12: 9:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 46CD637C042; Wed, 21 Jun 2000 12:09:13 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA20883; Wed, 21 Jun 2000 12:09:11 -0700 Date: Wed, 21 Jun 2000 12:08:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: Javier Henderson , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape drive oddities In-Reply-To: <20000621210824.F238@freebie.wbnet> 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 > > Right, and Adaptec (the older ones) had a reputation for being sensitive to > cabling (shiver, like the 1740) *uh* [ circular muscle in middle of body twitches ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 0:30:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 0DDC637C21D for ; Thu, 22 Jun 2000 00:30:08 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id AAA10261; Thu, 22 Jun 2000 00:30:00 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id AAA14020; Thu, 22 Jun 2000 00:30:00 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id AAA07327; Thu, 22 Jun 2000 00:29:59 -0700 (PDT) From: Don Lewis Message-Id: <200006220729.AAA07327@salsa.gv.tsc.tdk.com> Date: Thu, 22 Jun 2000 00:29:59 -0700 In-Reply-To: <20000621143609.A3012@albury.net.au> References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> <20000621143609.A3012@albury.net.au> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Nick Slager , Don Lewis Subject: Re: Invalidating pack messages Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 21, 2:36pm, Nick Slager wrote: } Subject: Re: Invalidating pack messages } I pulled out the power supply this morning, and replaced it with a brand new } unit. The system has just crashed again with the 'Invalidating pack' error } messages. [ snip ] } If this is the case (and I'm not doubting what you say), what else could cause } this problem? If your seeing funny blinking lights on the drive, and you are not the only person having problems with this particular drive model, I would be very suspicious that a drive firmware bug is being tickled. The best solution in this case would be to obtain a better version of the firmware from the vendor, but lacking that you might try turning off tagged command queueing or just reducing the number of tagged openings. I've noticed interactions between tagged command queueing and write caching on Seagate drives, so you might try turning off write caching and leaving the number of tagged openings alone. You can do all this with camcontrol. I'm not a fan of write caching since it violates the assumptions behind softupdates, so I turn it off on all my drives. I haven't seen any real performance penalty in doing so, though I think I've heard reports that it makes newfs run slower. You may be seeing this in FreeBSD and not NT because I think the CAM SCSI system can push the drives a lot harder than the SCSI drivers in NT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 2:34: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 7DA5C37C226 for ; Thu, 22 Jun 2000 02:33:58 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id CAA11451; Thu, 22 Jun 2000 02:33:36 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id CAA14627; Thu, 22 Jun 2000 02:33:36 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id CAA07879; Thu, 22 Jun 2000 02:33:35 -0700 (PDT) From: Don Lewis Message-Id: <200006220933.CAA07879@salsa.gv.tsc.tdk.com> Date: Thu, 22 Jun 2000 02:33:35 -0700 In-Reply-To: <200006220927.DAA29116@Ilsa.StevesCafe.com> References: <200006220927.DAA29116@Ilsa.StevesCafe.com> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Steve Passe , Don Lewis Subject: Re: Invalidating pack messages Cc: Nick Slager , scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Jun 22, 3:27am, Steve Passe wrote: } Subject: Re: Invalidating pack messages } Hi, } > On Jun 21, 2:36pm, Nick Slager wrote: } > } Subject: Re: Invalidating pack messages } > } > [ snip ] } > } > } If this is the case (and I'm not doubting what you say), what else could cause } > } this problem? } > } > If your seeing funny blinking lights on the drive, and you are not the only } > person having problems with this particular drive model, I would be very } > suspicious that a drive firmware bug is being tickled. The best solution } > ... } } I've been running old and new cheetahs on sym and 29160 controllers } without a hint of trouble: I think I saw two reports of this problem, both involving 18 GB drives. Yours look like 4 GB and 8 GB drives. } ahc0: port 0x3000-0x30ff mem } 0xfe004000-0xfe004fff irq 19 at device 1.0 on pci1 } ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs } sym1: <896> port 0x3400-0x34ff mem 0xfe000000-0xfe001fff,0xfe005000-0xfe0053ff } irq 10 at device 3.0 on pci1 } sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking } sym2: <896> port 0x3800-0x38ff mem 0xfe002000-0xfe003fff,0xfe005400-0xfe0057ff } irq 2 at device 3.1 on pci1 } sym2: No NVRAM, ID 7, Fast-40, LVD, parity checking } } da0 at sym1 bus 0 target 0 lun 0 } da0: Fixed Direct Access SCSI-2 device } da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing } Enabled } da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) } da1 at sym1 bus 0 target 1 lun 0 } da1: Fixed Direct Access SCSI-2 device } da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing } Enabled } da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) } da3 at ahc0 bus 0 target 8 lun 0 } da3: Fixed Direct Access SCSI-3 device } da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da3: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } da4 at ahc0 bus 0 target 9 lun 0 } da4: Fixed Direct Access SCSI-3 device } da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da4: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } da5 at ahc0 bus 0 target 10 lun 0 } da5: Fixed Direct Access SCSI-3 device } da5: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing } Enabled } da5: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) } } -- } Steve Passe | powered by } smp@csn.net | Symmetric MultiProcessor FreeBSD } } }-- End of excerpt from Steve Passe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 2:42:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id D165637B77A for ; Thu, 22 Jun 2000 02:42:28 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id DAA29233; Thu, 22 Jun 2000 03:41:07 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200006220941.DAA29233@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Don Lewis Cc: Steve Passe , Nick Slager , scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages In-reply-to: Your message of "Thu, 22 Jun 2000 02:33:35 PDT." <200006220933.CAA07879@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jun 2000 03:41:07 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > On Jun 22, 3:27am, Steve Passe wrote: > } Subject: Re: Invalidating pack messages > } Hi, > } > On Jun 21, 2:36pm, Nick Slager wrote: > } > } Subject: Re: Invalidating pack messages > } > > } > [ snip ] > } > > } > } If this is the case (and I'm not doubting what you say), what else could cause > } > } this problem? > } > > } > If your seeing funny blinking lights on the drive, and you are not the only > } > person having problems with this particular drive model, I would be very > } > suspicious that a drive firmware bug is being tickled. The best solution > } > ... > } > } I've been running old and new cheetahs on sym and 29160 controllers > } without a hint of trouble: > > I think I saw two reports of this problem, both involving 18 GB drives. > Yours look like 4 GB and 8 GB drives. True, I also have a pair of 36 GB u160 cheetahs, but havn't had time to install them yet... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 2:58:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id CB94E37B564 for ; Thu, 22 Jun 2000 02:58:23 -0700 (PDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id DAA29116; Thu, 22 Jun 2000 03:27:56 -0600 (MDT) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200006220927.DAA29116@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Don Lewis Cc: Nick Slager , scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages In-reply-to: Your message of "Thu, 22 Jun 2000 00:29:59 PDT." <200006220729.AAA07327@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jun 2000 03:27:56 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > On Jun 21, 2:36pm, Nick Slager wrote: > } Subject: Re: Invalidating pack messages > > [ snip ] > > } If this is the case (and I'm not doubting what you say), what else could cause > } this problem? > > If your seeing funny blinking lights on the drive, and you are not the only > person having problems with this particular drive model, I would be very > suspicious that a drive firmware bug is being tickled. The best solution > ... I've been running old and new cheetahs on sym and 29160 controllers without a hint of trouble: ahc0: port 0x3000-0x30ff mem 0xfe004000-0xfe004fff irq 19 at device 1.0 on pci1 ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs sym1: <896> port 0x3400-0x34ff mem 0xfe000000-0xfe001fff,0xfe005000-0xfe0053ff irq 10 at device 3.0 on pci1 sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking sym2: <896> port 0x3800-0x38ff mem 0xfe002000-0xfe003fff,0xfe005400-0xfe0057ff irq 2 at device 3.1 on pci1 sym2: No NVRAM, ID 7, Fast-40, LVD, parity checking da0 at sym1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da1 at sym1 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da3 at ahc0 bus 0 target 8 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) da4 at ahc0 bus 0 target 9 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) da5 at ahc0 bus 0 target 10 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da5: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 7:31:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id F40DD37BA49 for ; Thu, 22 Jun 2000 07:31:33 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 4413 invoked by alias); 22 Jun 2000 14:31:30 -0000 Received: (qmail 4407 invoked from network); 22 Jun 2000 14:31:30 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 22 Jun 2000 14:31:30 -0000 Received: (qmail 22075 invoked by uid 141); 22 Jun 2000 14:31:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 22 Jun 2000 14:31:29 -0000 Date: Thu, 22 Jun 2000 15:31:29 +0100 (BST) From: Mark Powell To: freebsd-scsi@freebsd.org Subject: Xiotech Magnitude and QLogic experience? 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 Hi, We've been presented with a tender for a large-scale storage system using fibre channel. It's based upon the Xiotech (www.xiotech.com) Magnitude system. http://www.xiotech.com/cgi-bin/magnitude.pl It's to be used for storage with Netware and UNIX using differing areas of the disk. Looks good. However, I've had no experience of FC before. I notice 4.0S supports the QLogic cards. I'd like to know whether Magnitude and a QLogic card under 4.0S would function happily. Is FC as open standard as SCSI? Xiotech do their own FC cards, but of course they aren't supported. Would the QLogic be just as good? Cheers. Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 22 11:36:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 56AD637B64F for ; Thu, 22 Jun 2000 11:36:55 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA23812; Thu, 22 Jun 2000 11:36:49 -0700 Date: Thu, 22 Jun 2000 11:36:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mark Powell Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Xiotech Magnitude and QLogic experience? In-Reply-To: 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 Unfortunately FC isn't as well shaken out as SCSI. It sure is an open standard, but that also means much is left open to interpretration. With respect to this particular device- I have not used it myself. I do know that XIOtech boxes have worked with Qlogic cards. I would recommend that you tell them: "We plan to use Qlogic 2200 cards under FreeBSD" and ask them to allow for demonstration time. I would be delighted to assist resolving any problems that ocur (I am the Qlogic driver writer for FreBSD, NetBSD and OpenBSD). -matt On Thu, 22 Jun 2000, Mark Powell wrote: > Hi, > We've been presented with a tender for a large-scale storage system > using fibre channel. It's based upon the Xiotech (www.xiotech.com) > Magnitude system. > > http://www.xiotech.com/cgi-bin/magnitude.pl > > It's to be used for storage with Netware and UNIX using differing areas of > the disk. Looks good. > However, I've had no experience of FC before. I notice 4.0S supports the > QLogic cards. I'd like to know whether Magnitude and a QLogic card under > 4.0S would function happily. Is FC as open standard as SCSI? Xiotech do > their own FC cards, but of course they aren't supported. Would the QLogic > be just as good? > Cheers. > > Mark Powell - UNIX System Administrator - Clifford Whitworth Building > A.I.S., University of Salford, Salford, Manchester, UK. > Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key > M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 23 0:40: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 0FE5C37B838 for ; Fri, 23 Jun 2000 00:40:00 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e5N7ciS51408; Fri, 23 Jun 2000 17:38:44 +1000 (EST) Date: Fri, 23 Jun 2000 17:38:44 +1000 From: Nick Slager To: Don Lewis Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000623173844.A51332@albury.net.au> References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> <20000621143609.A3012@albury.net.au> <200006220729.AAA07327@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006220729.AAA07327@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Thu, Jun 22, 2000 at 12:29:59AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > If your seeing funny blinking lights on the drive, and you are not the only > person having problems with this particular drive model, I would be very > suspicious that a drive firmware bug is being tickled. The best solution > in this case would be to obtain a better version of the firmware from the > vendor, but lacking that you might try turning off tagged command queueing > or just reducing the number of tagged openings. I've noticed interactions > between tagged command queueing and write caching on Seagate drives, so you > might try turning off write caching and leaving the number of tagged > openings alone. You can do all this with camcontrol. This morning I disabled write back caching in the SCSI BIOS, and the machine has been copying files here and there for ~7 hours now with no problems at all. As you say the performance difference is pretty much negligible. I'm going to leave the machine copying and rm'ing files all weekend to make sure this all is OK, but at this stage it appears disabling write caching has fixed the problem (or at least worked around it). Thanks very much for your help. Regards, Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 23 2:10:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pan.salford.ac.uk (pan.salford.ac.uk [146.87.255.104]) by hub.freebsd.org (Postfix) with SMTP id A7E6237B949 for ; Fri, 23 Jun 2000 02:10:37 -0700 (PDT) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 7125 invoked by alias); 23 Jun 2000 09:10:36 -0000 Received: (qmail 7119 invoked from network); 23 Jun 2000 09:10:36 -0000 Received: from unknown (HELO plato.salford.ac.uk) (146.87.255.76) by pan.salford.ac.uk with SMTP; 23 Jun 2000 09:10:36 -0000 Received: (qmail 23592 invoked by uid 141); 23 Jun 2000 09:10:36 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 23 Jun 2000 09:10:36 -0000 Date: Fri, 23 Jun 2000 10:10:36 +0100 (BST) From: Mark Powell To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Xiotech Magnitude and QLogic experience? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 22 Jun 2000, Matthew Jacob wrote: > I would be delighted to assist resolving any problems that ocur (I am the > Qlogic driver writer for FreBSD, NetBSD and OpenBSD). Many thanks for that offer, Matt. It gives me a damn sight more confidence in reaching a working solution :) Mark Powell - UNIX System Administrator - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 23 10:10:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with SMTP id 19CD537C37E; Fri, 23 Jun 2000 10:10:40 -0700 (PDT) (envelope-from magus+@hurlame.pdl.cs.cmu.edu) To: scsi@freebsd.org, hackers@freebsd.org Subject: SCSI HBA device detection? From: Nat Lanza Date: 23 Jun 2000 13:10:26 -0400 Message-ID: Lines: 17 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm writing a SCSI HBA driver that simulates a bus with some ramdisk-backed disks attached to it. I've read through the HBA tutorial in Daemon News, but I'm still unsure how to tell the system about my pretend disk devices. I suspect part of the problem is that I don't actually have real devices or a real IO bus. Anyone feel like explaining this? Thanks. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 23 10:13:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay02.chello.nl (relay02.chello.nl [212.83.68.146]) by hub.freebsd.org (Postfix) with ESMTP id D956A37B529 for ; Fri, 23 Jun 2000 10:13:02 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay02.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000623171243.TDXP26299.relay02@chello.nl>; Fri, 23 Jun 2000 19:12:43 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA02942; Fri, 23 Jun 2000 19:12:55 +0200 (CEST) (envelope-from wkb) Date: Fri, 23 Jun 2000 19:12:55 +0200 From: Wilko Bulte To: Nick Slager Cc: Don Lewis , scsi@FreeBSD.ORG Subject: Re: Invalidating pack messages Message-ID: <20000623191255.B2887@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <20000620172810.A84355@albury.net.au> <200006200754.AAA28201@salsa.gv.tsc.tdk.com> <20000621143609.A3012@albury.net.au> <200006220729.AAA07327@salsa.gv.tsc.tdk.com> <20000623173844.A51332@albury.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000623173844.A51332@albury.net.au>; from nicks@albury.net.au on Fri, Jun 23, 2000 at 05:38:44PM +1000 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jun 23, 2000 at 05:38:44PM +1000, Nick Slager wrote: > Thus spake Don Lewis (Don.Lewis@tsc.tdk.com): > > > If your seeing funny blinking lights on the drive, and you are not the only > > person having problems with this particular drive model, I would be very > > suspicious that a drive firmware bug is being tickled. The best solution > > in this case would be to obtain a better version of the firmware from the > > vendor, but lacking that you might try turning off tagged command queueing > > or just reducing the number of tagged openings. I've noticed interactions > > between tagged command queueing and write caching on Seagate drives, so you > > might try turning off write caching and leaving the number of tagged > > openings alone. You can do all this with camcontrol. > > This morning I disabled write back caching in the SCSI BIOS, and the machine > has been copying files here and there for ~7 hours now with no problems at > all. As you say the performance difference is pretty much negligible. > > I'm going to leave the machine copying and rm'ing files all weekend to make > sure this all is OK, but at this stage it appears disabling write caching has > fixed the problem (or at least worked around it). > > Thanks very much for your help. If this continues to work this drive/firmware combo deserves a quirk entry. -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jun 23 22:29:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from vicosa.dpi.ufv.br (vicosa.dpi.ufv.br [200.17.74.1]) by hub.freebsd.org (Postfix) with ESMTP id D15EC37BB04 for ; Fri, 23 Jun 2000 22:29:39 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br (port12.tdnet.com.br [200.236.148.112]) by vicosa.dpi.ufv.br (AIX4.2/UCB 8.7/8.7) with ESMTP id CAA10550 for ; Sat, 24 Jun 2000 02:28:47 -0200 (GRNLNDDT) Message-ID: <39541CED.DBFBF2F5@tdnet.com.br> Date: Sat, 24 Jun 2000 02:29:01 +0000 From: Gustavo Vieira Goncalves Coelho Rios X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: modifying scsi device param! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am trying to switch some parameters, but what i do get is nothing updated, look: etosha# camcontrol negotiate -n da -u 0 -T enable -ac Current Parameters: (pass0:ahc0:0:6:0): sync parameter: 12 (pass0:ahc0:0:6:0): frequency: 20.000MHz (pass0:ahc0:0:6:0): offset: 8 (pass0:ahc0:0:6:0): bus width: 16 bits (pass0:ahc0:0:6:0): disconnection is disabled (pass0:ahc0:0:6:0): tagged queueing is disabled New Parameters: (pass0:ahc0:0:6:0): sync parameter: 12 (pass0:ahc0:0:6:0): frequency: 20.000MHz (pass0:ahc0:0:6:0): offset: 8 (pass0:ahc0:0:6:0): bus width: 16 bits (pass0:ahc0:0:6:0): disconnection is disabled (pass0:ahc0:0:6:0): tagged queueing is disabled I tried to get tag queueing enabled, but could not. Another thing, look the output of the following command: etosha# camcontrol inquiry -n da -u 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 199910440080 pass0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Question: How can Tag queueing being enabled here and the first command show as not being enabled! Thanks a lot! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message