From owner-freebsd-scsi Sun Jun 13 8:20:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 8B72D15079 for ; Sun, 13 Jun 1999 08:20:23 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip122.houston22.tx.pub-ip.psi.net [38.31.97.122]) by leap.innerx.net (Postfix) with ESMTP id 1151437071 for ; Sun, 13 Jun 1999 11:20:21 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id KAA06299 for scsi@FreeBSD.org; Sun, 13 Jun 1999 10:20:16 -0500 (CDT) (envelope-from chris) Date: Sun, 13 Jun 1999 10:20:16 -0500 From: Chris Costello To: scsi@FreeBSD.org Subject: scsiconf Message-ID: <19990613102016.D1127@holly.dyndns.org> Reply-To: chris@calldei.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm working on the hardware section of the handbook right now and there are references (as well as a man page) to scsiconf, which doesn't exist. Instead of adding an entry in scsiconf.c as the handbook says, what would the appropriate action to take be for 'devices with LUNs != 0', if anything? Thanks. -- Chris Costello Your e-mail has been returned due to insufficient voltage. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 14 6:11:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from isy.liu.se (isy.liu.se [130.236.48.10]) by hub.freebsd.org (Postfix) with ESMTP id 6D46A152DB for ; Mon, 14 Jun 1999 06:11:50 -0700 (PDT) (envelope-from kentp@isy.liu.se) Received: from [130.236.53.104] (allvis.isy.liu.se [130.236.53.104]) by isy.liu.se (8.9.1/8.9.1) with ESMTP id PAA29508; Mon, 14 Jun 1999 15:11:46 +0200 (MET DST) X-Sender: kentp@pop.isy.liu.se Message-Id: In-Reply-To: <199906111134.LAA22415@jhs.muc.de> References: Your message of "Thu, 10 Jun 1999 06:40:54 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Jun 1999 15:12:54 +0200 To: freebsd-scsi@FreeBSD.ORG From: Kent Palmkvist Subject: Re: sea driver - anyone porting from 2.2.8 to 3.?/current ? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I was working on the sea driver way back in 93/94. I would have looked at a CAM version of it if I still had a working card, but it burned a few years ago (while trying to add an external connector). I am still interrested in working with it. It is however a bit hard to get a card. If there is any interrest and any available card/testers, I am willing to put some work into getting a working driver. No guarantees of any type is given of course... best regards /Kent Kent Palmkvist email: kentp@isy.liu.se Dept. of Electrical Engineering http://www.es.isy.liu.se/staff/kentp Link=F6ping University SE-581 83 LINK=D6PING phone: +46 13 281347 Sweden fax: +46 13 139282 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 14 10:59:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from empirion.idirect.com (empirion.idirect.com [207.136.64.205]) by hub.freebsd.org (Postfix) with ESMTP id 9479214D6D for ; Mon, 14 Jun 1999 10:58:48 -0700 (PDT) (envelope-from erics@idirect.com) Received: from localhost (erics@localhost) by empirion.idirect.com (8.9.3/8.9.3) with ESMTP id NAA21884 for ; Mon, 14 Jun 1999 13:48:32 -0400 X-Authentication-Warning: empirion.idirect.com: erics owned process doing -bs Date: Mon, 14 Jun 1999 13:48:32 -0400 (EDT) From: Eric To: freebsd-scsi@freebsd.org Subject: More then 4 Partitions on a SCSI drive. 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, I couldn't find anything on the web site about this. I'm trying to make more then 4 partitions on one SCSI drive (Seagate Baracuda)... but anything after the 4th partition it creates a bogus devices called X. Is it possible to make more then 4 partitions or do i have to do an extra step. Thanks a lot. --- Eric Szreder Internet Direct Network Administration To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 14 14:44:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hydrogen.fircrest.net (metriclient-3.uoregon.edu [128.223.172.3]) by hub.freebsd.org (Postfix) with ESMTP id 4EB0314BEB for ; Mon, 14 Jun 1999 14:43:49 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id OAA05743; Mon, 14 Jun 1999 14:43:32 -0700 (PDT) Message-ID: <19990614144331.20884@hydrogen.fircrest.net> Date: Mon, 14 Jun 1999 14:43:31 -0700 From: John-Mark Gurney To: Kent Palmkvist Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sea driver - anyone porting from 2.2.8 to 3.?/current ? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Kent Palmkvist on Mon, Jun 14, 1999 at 03:12:54PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kent Palmkvist scribbled this message on Jun 14: > I was working on the sea driver way back in 93/94. I would have looked at a > CAM version of it if I still had a working card, but it burned a few years > ago (while trying to add an external connector). > > I am still interrested in working with it. It is however a bit hard to get > a card. If there is any interrest and any available card/testers, I am > willing to put some work into getting a working driver. No guarantees of > any type is given of course... I have an ST-02 card, but I was never able to get it to work... I'm not sure if the card just doesn't work, but depending on shipping, I'd be willing to send it to someone... when I tried to boot it with the bios, it would pause at probing devices and not go any farther, and then when I took the bios off, the machine would probe, but the kernel wouldn't see it... :( -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jun 14 23:27: 8 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 0CD8C15500 for ; Mon, 14 Jun 1999 23:26:49 -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 PAA19554; Tue, 15 Jun 1999 15:56:45 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA75983; Tue, 15 Jun 1999 15:56:41 +0930 (CST) Date: Tue, 15 Jun 1999 15:56:41 +0930 From: Greg Lehey To: Eric Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: More then 4 Partitions on a SCSI drive. Message-ID: <19990615155640.P75176@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Eric on Mon, Jun 14, 1999 at 01:48:32PM -0400 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 Monday, 14 June 1999 at 13:48:32 -0400, Eric wrote: > > Hi, > I couldn't find anything on the web site about this. I'm trying to make > more then 4 partitions on one SCSI drive (Seagate Baracuda)... but > anything after the 4th partition it creates a bogus devices called X. Is > it possible to make more then 4 partitions or do i have to do an extra > step. Thanks a lot. If you mean Microsoft partitions ("slices"), then no. That's the limit. 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 Jun 15 4:11:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from isy.liu.se (isy.liu.se [130.236.48.10]) by hub.freebsd.org (Postfix) with ESMTP id 81D6115421 for ; Tue, 15 Jun 1999 04:11:25 -0700 (PDT) (envelope-from kentp@isy.liu.se) Received: from [130.236.53.104] (allvis.isy.liu.se [130.236.53.104]) by isy.liu.se (8.9.1/8.9.1) with ESMTP id NAA17184; Tue, 15 Jun 1999 13:09:56 +0200 (MET DST) X-Sender: kentp@pop.isy.liu.se Message-Id: In-Reply-To: <19990614144331.20884@hydrogen.fircrest.net> References: ; from Kent Palmkvist on Mon, Jun 14, 1999 at 03:12:54PM +0200 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 15 Jun 1999 13:11:05 +0200 To: John-Mark Gurney From: Kent Palmkvist Subject: Re: sea driver - anyone porting from 2.2.8 to 3.?/current ? Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : >> a card. If there is any interrest and any available card/testers, I am >> willing to put some work into getting a working driver. No guarantees of >> any type is given of course... > >I have an ST-02 card, but I was never able to get it to work... I'm not >sure if the card just doesn't work, but depending on shipping, I'd be >willing to send it to someone... > >when I tried to boot it with the bios, it would pause at probing devices >and not go any farther, and then when I took the bios off, the machine >would probe, but the kernel wouldn't see it... :( > >-- > John-Mark Gurney Voice: +1 541 684 8449 : What version of FreeBSD was that? The kernel in 2.0.x (don't remember how long this behaviour was included, or if it changed) detected the card type using a signature in the BIOS. Does the card work in DOS? What version of the BIOS is on the card? What type of devices was connected to the SCSI bus? I think you could get the hanging at probe time by either having poor termination of the SCSI bus, or that the interrupts was set wrong (default setting of the card is to disable interrupts, but they are needed I think). It has however been a while since I had a look at the code. I want you to know that if you send me your card, it will not be returned for at least 6 months. So you would better be prepared to be without the ST02 for that period of time. Shipping to Sweden is also a bit expensive and slow (my FreeBSD subscription CDs cost approx $10 for shipping with surface mail). I guess its best to wait and see if anyone else living a bit closer has a card they can spare. best regards /Kent Kent Palmkvist email: kentp@isy.liu.se Dept. of Electrical Engineering http://www.es.isy.liu.se/staff/kentp Link=F6ping University SE-581 83 LINK=D6PING phone: +46 13 281347 Sweden fax: +46 13 139282 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 15 7:59: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from empirion.idirect.com (empirion.idirect.com [207.136.64.205]) by hub.freebsd.org (Postfix) with ESMTP id 4328915649 for ; Tue, 15 Jun 1999 07:58:34 -0700 (PDT) (envelope-from erics@idirect.com) Received: from localhost (erics@localhost) by empirion.idirect.com (8.9.3/8.9.3) with ESMTP id KAA23244; Tue, 15 Jun 1999 10:58:02 -0400 X-Authentication-Warning: empirion.idirect.com: erics owned process doing -bs Date: Tue, 15 Jun 1999 10:58:02 -0400 (EDT) From: Eric X-Sender: Eric To: Christian Weisgerber Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: More then 4 Partitions on a SCSI drive. 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 Tue, 15 Jun 1999, Christian Weisgerber wrote: > In article you write: > > > I couldn't find anything on the web site about this. I'm trying to make > > more then 4 partitions on one SCSI drive (Seagate Baracuda)... but > > anything after the 4th partition it creates a bogus devices called X. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > Could you elaborate? > My drive is effectively divided into six partitions (once upon a time > created with sysinstall's diskLabelEditor): > > naddy@bigeye[~] /sbin/disklabel da0 | tail > > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 19*) > b: 262144 3276800 swap # (Cyl. 310*- 335*) > c: 8899737 0 unused 0 0 # (Cyl. 0 - 844*) > e: 3072000 204800 4.2BSD 1024 8192 16 # (Cyl. 19*- 310*) > f: 1024000 3538944 4.2BSD 1024 8192 16 # (Cyl. 335*- 432*) > g: 1024000 4562944 4.2BSD 1024 8192 16 # (Cyl. 432*- 529*) > h: 3312793 5586944 4.2BSD 1024 8192 16 # (Cyl. 529*- 844*) Unfortunatly I don't get the samething. Once I create my 5 slices, here's what I see once I'm done with the Disklabel Editor Part Mount Size Newfs ---- ----- ---- ----- da0s1a / 996MB UFS Y da0s2b swap 251MB SWAP da0s3e /var 996MB UFS Y da0s4e /opt 996MB UFS Y X /usr 5436MB UFS Y It will always create a X device anything after the 4th patition. I was curious and commited the install and during creation of the filesystems, it gave the error "Device X does not exist". Sorry if I'm sending to the wrong list, I was told this was a SCSI issue. Once again thanks for any info. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 15 15:50:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 207AA14F49 for ; Tue, 15 Jun 1999 15:50:26 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id QAA76804; Tue, 15 Jun 1999 16:50:18 -0600 (MDT) Message-Id: <199906152250.QAA76804@panzer.plutotech.com> Subject: Re: scsiconf In-Reply-To: <19990613102016.D1127@holly.dyndns.org> from Chris Costello at "Jun 13, 1999 10:20:16 am" To: chris@calldei.com Date: Tue, 15 Jun 1999 16:50:18 -0600 (MDT) Cc: scsi@FreeBSD.ORG From: Kenneth 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 Chris Costello wrote... > I'm working on the hardware section of the handbook right now > and there are references (as well as a man page) to scsiconf, > which doesn't exist. Instead of adding an entry in scsiconf.c as > the handbook says, what would the appropriate action to take be > for 'devices with LUNs != 0', if anything? By default, devices with multiple luns are probed and supported under CAM. You don't have to do anything to turn it on. You have to turn off multi-lun probing if you don't want it. To turn off multi-lun probing, you'd need to add a quirk entry to the transport layer (sys/cam/cam_xpt.c) for the device with the CAM_QUIRK_NOLUNS bit set. Take a look in cam_xpt.c, and you'll see a few examples of this. 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 Tue Jun 15 18: 4:11 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 48BF2151EB; Tue, 15 Jun 1999 18:03:47 -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 KAA24135; Wed, 16 Jun 1999 10:33:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA95495; Wed, 16 Jun 1999 10:33:04 +0930 (CST) Date: Wed, 16 Jun 1999 10:33:04 +0930 From: Greg Lehey To: Eric Cc: Christian Weisgerber , FreeBSD Questions Subject: Re: More then 4 Partitions on a SCSI drive. Message-ID: <19990616103303.A521@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Eric on Tue, Jun 15, 1999 at 10:58:02AM -0400 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 [moved to -questions] On Tuesday, 15 June 1999 at 10:58:02 -0400, Eric wrote: > On Tue, 15 Jun 1999, Christian Weisgerber wrote: > >> In article you write: >> >>> I couldn't find anything on the web site about this. I'm trying to make >>> more then 4 partitions on one SCSI drive (Seagate Baracuda)... but >>> anything after the 4th partition it creates a bogus devices called X. >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> Could you elaborate? >> My drive is effectively divided into six partitions (once upon a time >> created with sysinstall's diskLabelEditor): >> >> naddy@bigeye[~] /sbin/disklabel da0 | tail >> >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 19*) >> b: 262144 3276800 swap # (Cyl. 310*- 335*) >> c: 8899737 0 unused 0 0 # (Cyl. 0 - 844*) >> e: 3072000 204800 4.2BSD 1024 8192 16 # (Cyl. 19*- 310*) >> f: 1024000 3538944 4.2BSD 1024 8192 16 # (Cyl. 335*- 432*) >> g: 1024000 4562944 4.2BSD 1024 8192 16 # (Cyl. 432*- 529*) >> h: 3312793 5586944 4.2BSD 1024 8192 16 # (Cyl. 529*- 844*) > > Unfortunatly I don't get the samething. Once I create my 5 slices, here's > what I see once I'm done with the Disklabel Editor > > Part Mount Size Newfs > ---- ----- ---- ----- > da0s1a / 996MB UFS Y > da0s2b swap 251MB SWAP > da0s3e /var 996MB UFS Y > da0s4e /opt 996MB UFS Y > X /usr 5436MB UFS Y You're making Microsoft partitions (which we call slices), not UNIX partitions (which is what Eric was demonstrating above). You can have a maximum of four slices (Microsoft partitions). Each slice can contain 8 (UNIX) partitions. You should use one slice and put all your partitions in it. > It will always create a X device anything after the 4th patition. I was > curious and commited the install and during creation of the filesystems, > it gave the error "Device X does not exist". Sorry if I'm sending to the > wrong list, I was told this was a SCSI issue. Once again thanks for any > info. This isn't a SCSI issue, it's an administrative issue, so I'm moving it to -questions. To do this right, 1. Use one slice only. In the partition editor, create one FreeBSD slice (Microsoft partition). 2. Go to the disk label editor and create 3 (UNIX) partitions: root file system (/), swap and /usr. Don't create any other file systems on the same disk unless you know *exactly* how big they need to be. Otherwise you're going to run out of space in one partition and have space left over in others. In your case, you'd expect to have: Part Mount Size Newfs ---- ----- ---- ----- da0s1a / 996MB UFS Y da0s1b swap 251MB SWAP da0s1e /usr 7400MB UFS Y 3. After installation, create a directory /usr/var and make /var a symbolic link to it. You don't need an /opt file system, but if you want one, do the same thing with it. Do I detect an SNI background? Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Wed Jun 16 1:33:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hydrogen.fircrest.net (metriclient-3.uoregon.edu [128.223.172.3]) by hub.freebsd.org (Postfix) with ESMTP id B4D6714D4D for ; Wed, 16 Jun 1999 01:33:36 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id BAA09552; Wed, 16 Jun 1999 01:33:22 -0700 (PDT) Message-ID: <19990616013322.04252@hydrogen.fircrest.net> Date: Wed, 16 Jun 1999 01:33:22 -0700 From: John-Mark Gurney To: Kent Palmkvist Cc: scsi@freebsd.org Subject: Re: sea driver - anyone porting from 2.2.8 to 3.?/current ? References: ; Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Kent Palmkvist on Tue, Jun 15, 1999 at 01:11:05PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kent Palmkvist scribbled this message on Jun 15: > : > >> a card. If there is any interrest and any available card/testers, I am > >> willing to put some work into getting a working driver. No guarantees of > >> any type is given of course... > > > >I have an ST-02 card, but I was never able to get it to work... I'm not > >sure if the card just doesn't work, but depending on shipping, I'd be > >willing to send it to someone... > > > >when I tried to boot it with the bios, it would pause at probing devices > >and not go any farther, and then when I took the bios off, the machine > >would probe, but the kernel wouldn't see it... :( > > What version of FreeBSD was that? The kernel in 2.0.x (don't remember how > long this behaviour was included, or if it changed) detected the card type > using a signature in the BIOS. Does the card work in DOS? What version of > the BIOS is on the card? What type of devices was connected to the SCSI bus? I'm not sure what version, it was something in the 2.2.x range though.. and I'm not sure if it does, I just popped it in a machine to use with a single 200meg disk from a ps/2, and when it didn't work to much, I gave up... the disk (and cables) work fine with an ahc2842... and the disk was the only thing connected... > I think you could get the hanging at probe time by either having poor > termination of the SCSI bus, or that the interrupts was set wrong (default > setting of the card is to disable interrupts, but they are needed I think). > It has however been a while since I had a look at the code. hmmm... pretty sure I had it set up properly... > I want you to know that if you send me your card, it will not be returned > for at least 6 months. So you would better be prepared to be without the > ST02 for that period of time. Shipping to Sweden is also a bit expensive > and slow (my FreeBSD subscription CDs cost approx $10 for shipping with > surface mail). I guess its best to wait and see if anyone else living a bit > closer has a card they can spare. oh, that shouldn't be to bad... and I haven't ever used it... I picked it up from a swap meet once, so, you could even keep it if you wanted to... :) it'd probably be cheaper for me to find another one locally than to have you ship it back... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 17 9:25: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 30E0514F0A for ; Thu, 17 Jun 1999 09:25:01 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id KAA88720 for scsi@FreeBSD.ORG; Thu, 17 Jun 1999 10:24:59 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906171624.KAA88720@panzer.plutotech.com> Subject: camcontrol format patches available To: scsi@FreeBSD.ORG Date: Thu, 17 Jun 1999 10:24:59 -0600 (MDT) 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 I've had this sitting around in my tree for a few weeks. These are some patches to camcontrol to implement a 'format' subcommand: http://www.freebsd.org/~ken/camcontrol.format.061799 By default, this issues an immediate format command, and then updates a percentage formatted display every second. You'll need to apply the patches, recompile and reinstall libcam, and then recompile and reinstall camcontrol. The camcontrol modifications depend on some new functionality in libcam. Hopefully the man page should explain how things work. I'd appreciate any feedback, comments, etc. The usual disclaimers apply -- use at your own risk. 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 Thu Jun 17 19:11:17 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 645F314C1A for ; Thu, 17 Jun 1999 19:11:15 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-208-166-127-117.dialup.HiWAAY.net [208.166.127.117]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA30647 for ; Thu, 17 Jun 1999 21:10:51 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA43562 for ; Thu, 17 Jun 1999 21:09:32 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199906180209.VAA43562@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org Subject: suspected bad block From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jun 1999 21:09:31 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is the first time something like this has popped up: Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): READ(10). CDB: 28 0 1 9 b6 2 0 0 2 0 Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): MEDIUM ERROR info:109b603 asc:11,b Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f Think "make release" was running at the time the above happened. "sks:80,2f" doesn't look like a block number to me. What is it? Is this junk being reported by my HD? This is what dmesg has to say about the drive: da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) Am running "dd if=/dev/rda0c ibs=64k of=/dev/null" on the device right now to see if I can prompt the problem again. Or if the drive has already remapped it. Have mentioned in the past, camcontrol isn't quite happy with the above HD and Asus SC875 SCSI card: # date; camcontrol defects -f block -G ; sleep 10; tail -5 /var/log/messages ; date Thu Jun 17 21:04:39 CDT 1999 error reading defect list: Input/output error Jun 17 21:03:47 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84800. Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400. Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. Jun 17 21:04:40 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400. Thu Jun 17 21:04:49 CDT 1999 # -- 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 Jun 17 19:17: 9 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 BE4E614E14 for ; Thu, 17 Jun 1999 19:17:07 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-208-166-127-117.dialup.HiWAAY.net [208.166.127.117]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA03801 for ; Thu, 17 Jun 1999 21:16:41 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA43581 for ; Thu, 17 Jun 1999 21:15:09 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199906180215.VAA43581@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org Subject: choice of a new SCSI drive? From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jun 1999 21:15:09 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not much discussion here lately of what is going on in the SCSI market. Ordered a new MB today, an Asus P2B-S, with onboard Adaptec 7890 and 3860 after checking the archives confirming others have run same. MB was cheaper than an Adaptec 2940U2W PCI card by itself from most vendors. Only $200 more than the SCSI-less (but one PCI slot more) P2B-F. Is the 3860 an LVD "SCSI bridge" Adaptec uses to separate LVD and single ended, and run both on the same bus? Am downloading Asus' 11MB PDF manual at this moment so I might be answering my own question in a moment. A long moment at 28.8k. Would favor IBM or Seagate drives over anything else based on past performance. Actually less on performance performance and more on reliability performance. I don't want a 10k drive, partly for the noise. Partly for the heat. Would favor cool and quiet, as long as its reliable. Changed employers recently. Seems at my old job all my HD bookmarks listed LVD drives for less than non-LVD. That doesn't appear to be the case. Then after hearing it mentioned here and confirming it on IBM's site, it appears most LVD drives can fall back into single-ended mode? So maybe the market has wizened up learning they can use the latest LVD on the old controllers? A prime candidate HD for my new MB is at: http://www.onsale.com/category/inv/00037892/01605738.htm The is an "IBM ULTRASTAR 18ES 9.1GB HD U2SCSI 68-PIN 7200RPM LVD". For $350 (includes UPS ground shipping) it appears to be a good value. Among other nice things it has a 2MB cache. A nasty thing about Onsale/ AtCost is one can't get a straight answer as to the product's warranty, they link you to phone numbers where you can call the manufacturer and ask. IBM lists 5 years for over-the-counter drives. Seagate is well known for two warranty tiers, over-the-counter, and OEM. The OEM product is only warranted to the OEM. Its gotten so bad Seagate now has a serial number checker on their web site. A good thing about Onsale is I've dealt with them before and don't believe they would simply pocket my credit card number and jump across the border. A bad thing is all my credit cards have sent me those awful addendums stating they won't go to battle for me against the vendor if the purchase was made over 100 miles from my billing address. For my purposes, LVD is overkill. But I sorta feel like treating myself to something excessive at the moment. Ay pointers to sources of internal LVD cables and terminators? Some vendors advertise the drives prominently but forget about the essentials. -- 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 Jun 17 19:37:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id ED192155D7 for ; Thu, 17 Jun 1999 19:37:14 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id UAA92294; Thu, 17 Jun 1999 20:37:12 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906180237.UAA92294@panzer.plutotech.com> Subject: Re: suspected bad block In-Reply-To: <199906180209.VAA43562@nospam.hiwaay.net> from David Kelly at "Jun 17, 1999 09:09:31 pm" To: dkelly@HiWAAY.net (David Kelly) Date: Thu, 17 Jun 1999 20:37:11 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG 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 Kelly wrote... > This is the first time something like this has popped up: > Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): READ(10). CDB: 28 0 1 9 b6 2 0 0 2 0 > Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): MEDIUM ERROR info:109b603 asc:11,b > Jun 16 06:02:16 nospam /kernel: (da0:ncr0:0:0:0): Unrecovered read error - recommend reassignment sks:80,2f > > Think "make release" was running at the time the above happened. > > "sks:80,2f" doesn't look like a block number to me. What is it? Is this > junk being reported by my HD? The sks (sense key specific) value for errors with a MEDIUM ERROR sense key referrs to the drive's actual retry count for the command. The info field above shows the block. The block number with the problem is 0x109b603. From the READ CDB above, we know that it was a 2-block read request starting at block 0x109b602. So, the block number makes sense. > This is what dmesg has to say about the drive: > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > > Am running "dd if=/dev/rda0c ibs=64k of=/dev/null" on the device right > now to see if I can prompt the problem again. Or if the drive has > already remapped it. You'll probably see the error again. The drive can generally only remap a block if it has good data to put in place of the data it can't retrieve. Sometimes it can use ECC data to reconstruct the block, but if it can't, it probably won't be able to remap it. (There are rules the drive follows, which can be adjusted in mode page 1. Read the SCSI spec for details.) > Have mentioned in the past, camcontrol isn't quite > happy with the above HD and Asus SC875 SCSI card: > > # date; camcontrol defects -f block -G ; sleep 10; tail -5 /var/log/messages ; date > Thu Jun 17 21:04:39 CDT 1999 > error reading defect list: Input/output error > Jun 17 21:03:47 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84800. > Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400. > Jun 17 21:04:39 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > Jun 17 21:04:40 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0a84400. > Thu Jun 17 21:04:49 CDT 1999 Yeah, I think I remember your saying something about it. I will say that IBM drives typically don't like the block defect format. The physical sector format usually works for most drives. Quantum disks often work with the block format, but Seagate and IBM don't. It would help if I could figure out what the error above from the NCR driver means. Maybe if Stefan or Gerard are reading this, they might be able to help. If I get time this weekend (and if I can remember) I may hook up a disk to an NCR controller and see if I can reproduce this. Assuming you've got AWRE turned on, you can force the drive to remap the block, probably like this: camcontrol cmd -n da -u 0 -v -c "2a 0 1 09 b6 03 0 0 1 0" -o 512 - < /dev/null Use the above command at your own risk. It should write one block worth of nulls to the bad sector in question, but I might have gotten it wrong. 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 Thu Jun 17 19:54:42 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 A25E114E14 for ; Thu, 17 Jun 1999 19:54:39 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-208-166-127-117.dialup.HiWAAY.net [208.166.127.117]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id VAA27273; Thu, 17 Jun 1999 21:54:37 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id VAA43859; Thu, 17 Jun 1999 21:54:35 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199906180254.VAA43859@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: suspected bad block In-reply-to: Message from "Kenneth D. Merry" of "Thu, 17 Jun 1999 20:37:11 MDT." <199906180237.UAA92294@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Jun 1999 21:54:35 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > David Kelly wrote... > > Am running "dd if=/dev/rda0c ibs=64k of=/dev/null" on the device right > > now to see if I can prompt the problem again. Or if the drive has > > already remapped it. > > You'll probably see the error again. The drive can generally only remap a > block if it has good data to put in place of the data it can't retrieve. > Sometimes it can use ECC data to reconstruct the block, but if it can't, it > probably won't be able to remap it. (There are rules the drive follows, > which can be adjusted in mode page 1. Read the SCSI spec for details.) Well, it make a complete pass of dd without complaining. Maybe it got remapped later. If the drive remaps a block, will it be reported and appear in /var/log/messages? In any case I now know where the block is. So might be able to script dd to give the area a good workout with reads. > > Have mentioned in the past, camcontrol isn't quite > > happy with the above HD and Asus SC875 SCSI card: [...] > Yeah, I think I remember your saying something about it. I will say that > IBM drives typically don't like the block defect format. The physical > sector format usually works for most drives. Quantum disks often work with > the block format, but Seagate and IBM don't. > > It would help if I could figure out what the error above from the NCR > driver means. Maybe if Stefan or Gerard are reading this, they might be > able to help. > > If I get time this weekend (and if I can remember) I may hook up a disk to > an NCR controller and see if I can reproduce this. None of the reporting formats work: # camcontrol defects -f bfi -G error reading defect list: Input/output error # camcontrol defects -f phys -G error reading defect list: Input/output error This one was a little different. It takes longer so I timed it: # time camcontrol defects -f phys -P error reading defect list: Input/output error 0.002u 0.000s 0:03.87 0.0% 0+0k 0+0io 0pf+0w # time camcontrol defects -f bfi -P error reading defect list: Input/output error 0.000u 0.003s 0:03.88 0.0% 0+0k 0+0io 0pf+0w # time camcontrol defects -f block -P error reading defect list: Input/output error 0.000u 0.003s 0:03.94 0.0% 0+0k 0+0io 0pf+0w for comparison's sake: # time camcontrol defects -f phys -G error reading defect list: Input/output error 0.000u 0.003s 0:00.01 0.0% 0+0k 0+0io 0pf+0w Messages in /var/log/messages are identical for all of the above. > Assuming you've got AWRE turned on, you can force the drive to remap the > block, probably like this: > > camcontrol cmd -n da -u 0 -v -c "2a 0 1 09 b6 03 0 0 1 0" -o 512 - < /dev/null > > Use the above command at your own risk. It should write one block worth of > nulls to the bad sector in question, but I might have gotten it wrong. Its late. I'm tired. For some reason the above tickled my funny bone. I believe I will pass on trying the above. At least unless things get worse. -- 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 Jun 17 19:55: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DEDC15571 for ; Thu, 17 Jun 1999 19:54:54 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id UAA92425; Thu, 17 Jun 1999 20:54:52 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906180254.UAA92425@panzer.plutotech.com> Subject: Re: choice of a new SCSI drive? In-Reply-To: <199906180215.VAA43581@nospam.hiwaay.net> from David Kelly at "Jun 17, 1999 09:15:09 pm" To: dkelly@HiWAAY.net (David Kelly) Date: Thu, 17 Jun 1999 20:54:51 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG 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 Kelly wrote... > Not much discussion here lately of what is going on in the SCSI market. > Ordered a new MB today, an Asus P2B-S, with onboard Adaptec 7890 and > 3860 after checking the archives confirming others have run same. MB was > cheaper than an Adaptec 2940U2W PCI card by itself from most vendors. > Only $200 more than the SCSI-less (but one PCI slot more) P2B-F. That's a good buy. Nowadays, it's generally cheaper to get SCSI on the motherboard. You can even get Adaptec 7896/97 parts on there if you want. > Is the 3860 an LVD "SCSI bridge" Adaptec uses to separate LVD and single > ended, and run both on the same bus? Am downloading Asus' 11MB PDF > manual at this moment so I might be answering my own question in a > moment. A long moment at 28.8k. Yes, it is a SE<->LVD bridge. > Would favor IBM or Seagate drives over anything else based on past > performance. Actually less on performance performance and more on > reliability performance. I don't want a 10k drive, partly for the noise. > Partly for the heat. Would favor cool and quiet, as long as its > reliable. > > Changed employers recently. Seems at my old job all my HD bookmarks > listed LVD drives for less than non-LVD. That doesn't appear to be the > case. Then after hearing it mentioned here and confirming it on IBM's > site, it appears most LVD drives can fall back into single-ended mode? LVD disks work fine in single-ended mode, with the caveat that they do not come with terminators. So you need an external terminator (the one on those twisty LVD cables will do) or you need to use a device with SE terminators to do the termination on the bus. > So maybe the market has wizened up learning they can use the latest LVD > on the old controllers? I suppose so. > A prime candidate HD for my new MB is at: > http://www.onsale.com/category/inv/00037892/01605738.htm > > The is an "IBM ULTRASTAR 18ES 9.1GB HD U2SCSI 68-PIN 7200RPM LVD". For > $350 (includes UPS ground shipping) it appears to be a good value. Just for reference, NECX (www.necx.com) has the same drive for $365.00. > Among other nice things it has a 2MB cache. A nasty thing about Onsale/ > AtCost is one can't get a straight answer as to the product's warranty, > they link you to phone numbers where you can call the manufacturer and > ask. IBM lists 5 years for over-the-counter drives. Seagate is well > known for two warranty tiers, over-the-counter, and OEM. The OEM product > is only warranted to the OEM. Its gotten so bad Seagate now has a serial > number checker on their web site. Well, the disks you get from NECX are full-warranty disks. Their page for the 9G Ultrastar 18ES says that it has a 5 year warranty. If you're worried about whether Onsale's disks have warranties, just pay the extra $15 and buy it from NECX. > For my purposes, LVD is overkill. But I sorta feel like treating myself > to something excessive at the moment. > > Ay pointers to sources of internal LVD cables and terminators? Some > vendors advertise the drives prominently but forget about the > essentials. You often get a cable set with your ASUS motherboard. The LVD cable will be a twisty cable with a terminator block on the end. If it didn't come with a cable set, you can generally pick them up at a computer store or at www.scsi-cables.com. 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 Thu Jun 17 20: 2:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D99614E14 for ; Thu, 17 Jun 1999 20:02:27 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id VAA92490; Thu, 17 Jun 1999 21:02:25 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906180302.VAA92490@panzer.plutotech.com> Subject: Re: suspected bad block In-Reply-To: <199906180254.VAA43859@nospam.hiwaay.net> from David Kelly at "Jun 17, 1999 09:54:35 pm" To: dkelly@hiwaay.net (David Kelly) Date: Thu, 17 Jun 1999 21:02:25 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG 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 Kelly wrote... > "Kenneth D. Merry" writes: > > David Kelly wrote... > > > Am running "dd if=/dev/rda0c ibs=64k of=/dev/null" on the device right > > > now to see if I can prompt the problem again. Or if the drive has > > > already remapped it. > > > > You'll probably see the error again. The drive can generally only remap a > > block if it has good data to put in place of the data it can't retrieve. > > Sometimes it can use ECC data to reconstruct the block, but if it can't, it > > probably won't be able to remap it. (There are rules the drive follows, > > which can be adjusted in mode page 1. Read the SCSI spec for details.) > > Well, it make a complete pass of dd without complaining. Maybe it got > remapped later. If the drive remaps a block, will it be reported and > appear in /var/log/messages? Generally, recovered errors (as successfully remapped blocks are) won't be reported. > In any case I now know where the block is. So might be able to script > dd to give the area a good workout with reads. > > > Have mentioned in the past, camcontrol isn't quite > > > happy with the above HD and Asus SC875 SCSI card: > [...] > > Yeah, I think I remember your saying something about it. I will say that > > IBM drives typically don't like the block defect format. The physical > > sector format usually works for most drives. Quantum disks often work with > > the block format, but Seagate and IBM don't. > > > > It would help if I could figure out what the error above from the NCR > > driver means. Maybe if Stefan or Gerard are reading this, they might be > > able to help. > > > > If I get time this weekend (and if I can remember) I may hook up a disk to > > an NCR controller and see if I can reproduce this. > > None of the reporting formats work: > # camcontrol defects -f bfi -G > error reading defect list: Input/output error > # camcontrol defects -f phys -G > error reading defect list: Input/output error > > This one was a little different. It takes longer so I timed it: > # time camcontrol defects -f phys -P > error reading defect list: Input/output error > 0.002u 0.000s 0:03.87 0.0% 0+0k 0+0io 0pf+0w > # time camcontrol defects -f bfi -P > error reading defect list: Input/output error > 0.000u 0.003s 0:03.88 0.0% 0+0k 0+0io 0pf+0w > # time camcontrol defects -f block -P > error reading defect list: Input/output error > 0.000u 0.003s 0:03.94 0.0% 0+0k 0+0io 0pf+0w Well, the PLIST is generally larger than the GLIST. Although the 4 seconds that is taking is sorta close to the 5 second timeout. You might try bumping the timeout (with -t) just for grins, but I don't think it'll help. > for comparison's sake: > # time camcontrol defects -f phys -G > error reading defect list: Input/output error > 0.000u 0.003s 0:00.01 0.0% 0+0k 0+0io 0pf+0w > > Messages in /var/log/messages are identical for all of the above. 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 Sat Jun 19 7:57: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp2.xs4all.nl (smtp2.xs4all.nl [194.109.6.52]) by hub.freebsd.org (Postfix) with ESMTP id EDA3114BDD for ; Sat, 19 Jun 1999 07:57:03 -0700 (PDT) (envelope-from pblote@xs4all.nl) Received: (from root@localhost) by smtp2.xs4all.nl (8.8.8/8.8.8) id QAA17261; Sat, 19 Jun 1999 16:57:02 +0200 (CEST) From: patrickblote To: freebsd-scsi@freebsd.org X-Via: imploder /usr/local/lib/mail/news2mail/news2mail at smtp2.xs4all.nl Subject: adaptec2940U2W & seagate barracuda Date: Sat, 19 Jun 1999 16:49:47 +0200 Organization: XS4ALL Internet BV Message-ID: <376BAE0A.2E3A4EFA@XS4ALL.NL> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having trouble with my SCSI Seagate drive and my Adaptec 2940U2W I think! When i attache my seagete drive on my adaptec the following happens: - My adaptec card sees the seaget and it has its own id. also he sees my Yamaha cd-writer which also has its own id. -then windows 95 starts up from my IDE harddisk: windows doesn't see my scsi harddisk and my Yamaha. It also says that my adaptec isn't properly installed. - if I take the scsi harddisk out then there is no problem. So please anyone help, of with suggestions please help me!!!!! mail to: pblote@xs4all.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jun 19 10:30:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BD0B14CD3 for ; Sat, 19 Jun 1999 10:30:27 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id LAA06406; Sat, 19 Jun 1999 11:30:22 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199906191730.LAA06406@panzer.plutotech.com> Subject: Re: adaptec2940U2W & seagate barracuda In-Reply-To: <376BAE0A.2E3A4EFA@XS4ALL.NL> from patrickblote at "Jun 19, 1999 04:49:47 pm" To: pblote@xs4all.nl (patrickblote) Date: Sat, 19 Jun 1999 11:30:22 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG 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 patrickblote wrote... > I am having trouble with my SCSI Seagate drive and my Adaptec 2940U2W I > think! > > When i attache my seagete drive on my adaptec the following happens: > - My adaptec card sees the seaget and it has its own id. > also he sees my Yamaha cd-writer which also has its own id. > -then windows 95 starts up from my IDE harddisk: > windows doesn't see my scsi harddisk and my Yamaha. It also says that my > adaptec isn't properly installed. > - if I take the scsi harddisk out then there is no problem. > > So please anyone help, of with suggestions please help me!!!!! Why are you posting to a FreeBSD list with a Windows 95 problem? You should call Adaptec or Microsoft tech support if you're having trouble with their products. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message