From owner-freebsd-scsi Tue May 14 1: 4:57 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from gate.volant.org (gate.volant.org [207.111.218.246]) by hub.freebsd.org (Postfix) with ESMTP id BBE4737B408 for ; Tue, 14 May 2002 01:04:54 -0700 (PDT) Received: from 216-55-134-176.dsl.san-diego.abac.net ([216.55.134.176] helo=asimov) by gate.volant.org with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.33 #1) id 177XIf-000Dpy-00 for scsi@freebsd.org; Tue, 14 May 2002 01:04:49 -0700 Date: Tue, 14 May 2002 01:04:47 -0700 From: Pat Lashley To: scsi@freebsd.org Subject: Looking for driver for Initio INI-A100U2W Message-ID: <203000000.1021363487@asimov> X-Mailer: Mulberry/2.1.1 (SunOS/SPARC Demo) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm looking for drivers to support an Initio INI-A100U2W on FreeBSD 4.5-STABLE. The Initio site's drivers page has a link for 'FreeBSD 4 & 5' drivers to www.sevenislands.net; but it appears to be defunct - I can't get DNS to resolve it. The BSD Drivers database has an entry for an ihb driver, but it doesn't seem to have been updated since the initial entry almost a year ago. I'd like to get the latest and most stable version available. Thanks, -Pat "Reserve your right to think, for even to think wrongly is better than not to think at all" "To teach superstitions as truth is a most terrible thing." -Hypatia 370(?)-415 AD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 15 10:59: 9 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id BD07F37B8D3 for ; Wed, 15 May 2002 10:57:33 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id F1559D983; Wed, 15 May 2002 13:51:30 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id E3AA1D982 for ; Wed, 15 May 2002 13:51:30 -0400 (EDT) Date: Wed, 15 May 2002 13:51:30 -0400 (EDT) From: David Miller X-Sender: dmiller@search.sparks.net To: freebsd-scsi@FreeBSD.ORG Subject: Adaptec 3200S + Dell 2100S problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The basics: FreeBSD 4.5R Adaptec 3200S with firmware dowloaded from the adaptec web site today Dell 2100S with 12 18 GB 15K RPM drives FreeBSD finds the RAID controller fine on boot: de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:40:81:25 pcib2: at device 14.0 on pci0 pci2: on pcib2 asr0: mem 0xd8000000-0xd9ffffff irq 10 at device 14. 1 on pci0 asr0: major=154 asr0: ADAPTEC 3200S FW Rev. 370F, 2 channel, 256 CCBs, Protocol I2O isab0: at device 17.0 on It finds the configured drives OK: acd0: CDROM at ata1-master using PIO3 pass0 at asr0 bus 0 target 15 lun 0 pass0: Removable Processor SCSI-3 device pass4 at asr0 bus 1 target 15 lun 0 pass4: Removable Processor SCSI-3 device da0 at asr0 bus 1 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 86831MB (177829888 512 byte sectors: 255H 63S/T 11069C) da1 at asr0 bus 1 target 8 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Tagged Queueing Enabled da1: 86831MB (177829888 512 byte sectors: 255H 63S/T 11069C) da2 at asr0 bus 1 target 13 lun 0 da2: Fixed Direct Access SCSI-3 device da2: Tagged Queueing Enabled da2: 17366MB (35566461 512 byte sectors: 255H 63S/T 2213C) Mounting root from ufs:/dev/ad0s1a THE PROBLEM: I can't label the new drives. fdisk seems OK: bash-2.05a# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=11069 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=11069 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 177823422 (86827 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 828/ head 254/ sector 63 but disklabel doesn't want to work: bash-2.05a# disklabel -e -r da0 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) I walked through /stand/sysinstall first and came back to the CLI in order to get better error messages. Any idea what's ailing the addition the disk space? Other potentially useful info: bash-2.05a# camcontrol devlist at scbus0 target 15 lun 0 (pass0) at scbus1 target 1 lun 0 (pass1,da0) at scbus1 target 8 lun 0 (pass2,da1) at scbus1 target 13 lun 0 (pass3,da2) at scbus1 target 15 lun 0 (pass4) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 15 11:31:24 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 2ACEB37B40B for ; Wed, 15 May 2002 11:31:16 -0700 (PDT) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g4FIT9992912; Wed, 15 May 2002 12:29:09 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200205151829.g4FIT9992912@aslan.scsiguy.com> To: David Miller Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 3200S + Dell 2100S problems In-Reply-To: Your message of "Wed, 15 May 2002 13:51:30 EDT." Date: Wed, 15 May 2002 12:29:09 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Warning: BIOS sector numbering starts with sector 1 >Information from DOS bootblock is: >The data for partition 1 is: > >The data for partition 2 is: > >The data for partition 3 is: > >The data for partition 4 is: >sysid 165,(FreeBSD/NetBSD/386BSD) > start 63, size 177823422 (86827 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 828/ head 254/ sector 63 > >but disklabel doesn't want to work: > >bash-2.05a# disklabel -e -r da0 >disklabel: bad pack magic number (label is damaged, or pack is unlabeled) disklabel -e only works if there is a pre-existing label on the drives. Try disklabel -w -r da0 auto followed by disklabel -e -r da0. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 15 11:55: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id 890CB37B408 for ; Wed, 15 May 2002 11:55:02 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id C2CE9D983; Wed, 15 May 2002 14:48:59 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id B5608D982; Wed, 15 May 2002 14:48:59 -0400 (EDT) Date: Wed, 15 May 2002 14:48:59 -0400 (EDT) From: David Miller To: "Justin T. Gibbs" Cc: David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 3200S + Dell 2100S problems In-Reply-To: <200205151829.g4FIT9992912@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 15 May 2002, Justin T. Gibbs wrote: > >but disklabel doesn't want to work: > > > >bash-2.05a# disklabel -e -r da0 > >disklabel: bad pack magic number (label is damaged, or pack is unlabeled) > > disklabel -e only works if there is a pre-existing label on the drives. > Try disklabel -w -r da0 auto followed by disklabel -e -r da0. bash-2.05a# disklabel -w -r da0 usage: disklabel [-r] disk (to read label) disklabel -w [-r] [-n] disk type [ packid ] (to write label with existing boot program) disklabel -e [-r] [-n] disk (to edit label) disklabel -R [-r] [-n] disk protofile (to restore label with existing boot program) disklabel -B [-n] [ -b boot1 [ -s boot2 ] ] disk [ type ] (to install boot program with existing label) disklabel -w -B [-n] [ -b boot1 [ -s boot2 ] ] disk type [ packid ] (to write label and boot program) disklabel -R -B [-n] [ -b boot1 [ -s boot2 ] ] disk protofile [ type ] (to restore label and boot program) disklabel [-NW] disk (to write disable/enable label) Maybe this is why /stand/sysinstall doesn't work? --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 15 11:58:58 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 5DB5437B406 for ; Wed, 15 May 2002 11:58:55 -0700 (PDT) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g4FIum993819; Wed, 15 May 2002 12:56:48 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200205151856.g4FIum993819@aslan.scsiguy.com> To: David Miller Cc: David Miller , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 3200S + Dell 2100S problems In-Reply-To: Your message of "Wed, 15 May 2002 14:48:59 EDT." Date: Wed, 15 May 2002 12:56:48 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >On Wed, 15 May 2002, Justin T. Gibbs wrote: >> >but disklabel doesn't want to work: >> > >> >bash-2.05a# disklabel -e -r da0 >> >disklabel: bad pack magic number (label is damaged, or pack is unlabeled) >> >> disklabel -e only works if there is a pre-existing label on the drives. >> Try disklabel -w -r da0 auto followed by disklabel -e -r da0. > >bash-2.05a# disklabel -w -r da0 You forgot "auto" at the end. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 15 13:38:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id D615337B40F for ; Wed, 15 May 2002 13:38:30 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id 12528D983; Wed, 15 May 2002 16:32:28 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id F09A3D982; Wed, 15 May 2002 16:32:27 -0400 (EDT) Date: Wed, 15 May 2002 16:32:27 -0400 (EDT) From: David Miller To: "Justin T. Gibbs" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 3200S + Dell 2100S problems In-Reply-To: <200205151856.g4FIum993819@aslan.scsiguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 15 May 2002, Justin T. Gibbs wrote: > >On Wed, 15 May 2002, Justin T. Gibbs wrote: > >> >but disklabel doesn't want to work: > >> > > >> >bash-2.05a# disklabel -e -r da0 > >> >disklabel: bad pack magic number (label is damaged, or pack is unlabeled) > >> > >> disklabel -e only works if there is a pre-existing label on the drives. > >> Try disklabel -w -r da0 auto followed by disklabel -e -r da0. > > > >bash-2.05a# disklabel -w -r da0 > > You forgot "auto" at the end. That wasn't very clever of me, now was it? :( The problem appears to be solved; apparently there was an intermittently bad disk that was not letting the boot block get updated. When I configured that one out of the array things started working. Sorry to be a nuisance; I should have seen that before posting in the first place. --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 17 22:26:21 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 04D2D37B40B for ; Fri, 17 May 2002 22:26:18 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4I5M4209856 for ; Fri, 17 May 2002 22:22:04 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Fri, 17 May 2002 22:22:04 -0700 (PDT) From: Patrick Thomas To: Subject: how do I know when RAID fails ? (mylex, PERC, etc) Message-ID: <20020517221728.V44320-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have a few systems running dell PERC raid controllers, and a few running mylex controllers. All of them are being used to provide RAID mirrors, which I use to run FreeBSD on. So the question is, what happens when I am happily running along, and a drive fails ? Certainly things keep running, since they are mirrors, but how do I know a drive has failed ? Does the driver report to syslog ? I would really hate to wake up someday and lose the second drive in a mirror volume, only to realize the first drive had died a month ago and I never knew about it. So how do I know when bad things happen with my RAID drives? thanks, pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 17 23:39:10 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [207.200.153.226]) by hub.freebsd.org (Postfix) with ESMTP id A4D7837B40F for ; Fri, 17 May 2002 23:39:06 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 178x1f-0005vd-00; Fri, 17 May 2002 22:45:07 -0700 Date: Fri, 17 May 2002 22:45:04 -0700 (PDT) From: Tom Samplonius To: Patrick Thomas Cc: freebsd-scsi@freebsd.org Subject: Re: how do I know when RAID fails ? (mylex, PERC, etc) In-Reply-To: <20020517221728.V44320-100000@utility.clubscholarship.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 17 May 2002, Patrick Thomas wrote: ... > So the question is, what happens when I am happily running along, and a > drive fails ? Certainly things keep running, since they are mirrors, but > how do I know a drive has failed ? > > Does the driver report to syslog ? ... The mly driver logs to syslog. I'm surprised you haven't done a simulated drive failure (just remove a drive while the array is running). I always do that with every server to make sure everything is working, particular that the SAFTE enclosure reports that a drive has installed to trigger the autorebuild. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 18 8:41:26 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 7226737B408; Sat, 18 May 2002 08:41:18 -0700 (PDT) Received: from pacbell.net ([64.171.188.238]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GWB00BCPCWTOA@mta5.snfc21.pbi.net>; Sat, 18 May 2002 08:41:18 -0700 (PDT) Date: Sat, 18 May 2002 08:44:52 -0700 From: richard childers Subject: "/dev/nsa0: Device not configured" To: freebsd-questions@FreeBSD.ORG Cc: freebsd-scsi@freebsd.org Message-id: <3CE676F4.64768D6F@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.79 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've been a happy (and loyal) user (and proponent) of FreeBSD since version 2.2. After moving, recently, I was distressed to find that my server didn't work. Maybe that misapplied 220 UPS had something to do with it. )-: Good thing I have backups. Figured I'd combine the hardware upgrade with an OS upgrade. I had been running 4.3, now 4.4 was available, 4.5 would be due soon. Things were delayed by my employer's decision to relocate the office (T1s, phone switches, web sites, etc) to a new location; everyone's doing it in San Francisco, as leases are renegotiated downwards, with much wringing of hands on the parts of owners. C'est la vie. But I digress. Finally got the time; installed 4.4. Tried to rewind the tape drive, out of the box. root# mt status mt: /dev/nsa0: Device not configured To make a long story short, I'll add that at this point I: (a) checked the kernel (and rebuilt a slightly different one that was more specific regarding SCSI bus and whatnot - no errors, now I had two kernels whose behavior I could compare), then (b), swapped out SCSI cards and then SCSI tapes (I have a few 8mm Exabytes lying about, you can get 'em at Dot-Com Depot, in Sunnyvale, for around $50), and (c) searched the web (including freebsd.org) for pointers to this error, and, yes, I put a tape in, and yes, it was write-enabled, and no, it's didn'ty make any difference. Here's the annoying part. I installed FreeBSD 4.3 off the CDROM set and everything works fine, including your basic "mt status" (my first test). Here's another annoyance; because of the lapse, FreeBSD 4.5 was now available. I ordered it and the exact same thing is happening, as happened in FreeBSD 4.4. What am I missing? This seems like such a large problem that a release could not possibly make it out of the door without being fixed. Am I doomed to run FreeBSD 4.3 (not a bad number, all things considered, for BSD worshippers :-) as a legacy operating system for 8mm backups on all my servers? Don't get me wrong; there are advantages to upgrading, too, for instance, there's the wi0 driver. I can handle running 4.5 on laptop(s) only. But it's hard to explain to potential customers; 'Oh, yeah, the 8mm drive isn't working in this version, so sorry, we have to step back a few years to be sure that things work right.' (-; Thanks for your time and thought, ahead of time. -- richard Richard A Childers / KG6HAC fscked@pacbell.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 18 10:21:26 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 1910237B40A; Sat, 18 May 2002 10:21:11 -0700 (PDT) Received: from pacbell.net ([64.171.188.238]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GWB002A3HJABW@mta6.snfc21.pbi.net>; Sat, 18 May 2002 10:21:10 -0700 (PDT) Date: Sat, 18 May 2002 10:24:44 -0700 From: richard childers Subject: Re: "/dev/nsa0: Device not configured" To: freebsd-questions@FreeBSD.ORG, freebsd-scsi@freebsd.org Message-id: <3CE68E5C.7EBC1DDE@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.79 [en] (WinNT; U) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Accept-Language: en References: <3CE676F4.64768D6F@pacbell.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I wanted to add two things. (1), Yes, the device entries exist. Sure, I can remake them but their dates of creation indicate they were just made when I installed FreeBSD, shortly before the time at which I first log in. (2), I've noticed in the boot messages that the kernel sees the SCSI controller (ahc0) but never does the "Waiting 15 seconds for SCSI devices to settle" thing, and never reports seeing the attached 8mm drive at ID #4. The SCSI controller always sees the device when I test it, by typing ^A during boot, entering the SCSI controller's onboard software interface and using it to poll the bus and see what it sees. This hardware works perfectly under FreeBSD 4.3 but not under 4.4 or 4.5; and the error reported under 4.4 and 4.5 is identical. And now, I will go off and do a 'MAKEDEV'; and, you know, I think I *did* do this, 'way back last week when I was first getting into this. But, really, if the /dev entries exist, and their major and minor numbers are as coded in /dev/MAKEDEV (which is a shellscript) remaking them should not effect anything. -- richard richard childers wrote: > I've been a happy (and loyal) user (and proponent) of FreeBSD since > version 2.2. > > After moving, recently, I was distressed to find that my server didn't > work. Maybe that misapplied 220 UPS had something to do with it. )-: > Good thing I have backups. > > Figured I'd combine the hardware upgrade with an OS upgrade. I had been > running 4.3, now 4.4 was available, 4.5 would be due soon. Things were > delayed by my employer's decision to relocate the office (T1s, phone > switches, web sites, etc) to a new location; everyone's doing it in San > Francisco, as leases are renegotiated downwards, with much wringing of > hands on the parts of owners. C'est la vie. But I digress. > > Finally got the time; installed 4.4. Tried to rewind the tape drive, out > of the box. > > root# mt status > mt: /dev/nsa0: Device not configured > > To make a long story short, I'll add that at this point I: > > (a) checked the kernel (and rebuilt a slightly different one that was > more specific regarding SCSI bus and whatnot - no errors, now I had two > kernels whose behavior I could compare), then > > (b), swapped out SCSI cards and then SCSI tapes (I have a few 8mm > Exabytes lying about, you can get 'em at Dot-Com Depot, in Sunnyvale, > for around $50), and > > (c) searched the web (including freebsd.org) for pointers to this error, > and, yes, I put a tape in, and yes, it was write-enabled, and no, it's > didn'ty make any difference. > > Here's the annoying part. I installed FreeBSD 4.3 off the CDROM set and > everything works fine, including your basic "mt status" (my first test). > > Here's another annoyance; because of the lapse, FreeBSD 4.5 was now > available. I ordered it and the exact same thing is happening, as > happened in FreeBSD 4.4. > > What am I missing? This seems like such a large problem that a release > could not possibly make it out of the door without being fixed. Am I > doomed to run FreeBSD 4.3 (not a bad number, all things considered, for > BSD worshippers :-) as a legacy operating system for 8mm backups on all > my servers? > > Don't get me wrong; there are advantages to upgrading, too, for > instance, there's the wi0 driver. I can handle running 4.5 on laptop(s) > only. But it's hard to explain to potential customers; 'Oh, yeah, the > 8mm drive isn't working in this version, so sorry, we have to step back > a few years to be sure that things work right.' (-; > > Thanks for your time and thought, ahead of time. > > -- richard > > Richard A Childers / KG6HAC > fscked@pacbell.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 18 20:36:51 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from search.sparks.net (d-207-5-180-136.gwi.net [207.5.180.136]) by hub.freebsd.org (Postfix) with ESMTP id E7CD037B406 for ; Sat, 18 May 2002 20:36:36 -0700 (PDT) Received: by search.sparks.net (Postfix, from userid 100) id 24F85D983; Sat, 18 May 2002 23:30:23 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id 0EDF9D982 for ; Sat, 18 May 2002 23:30:23 -0400 (EDT) Date: Sat, 18 May 2002 23:30:22 -0400 (EDT) From: David Miller To: freebsd-scsi@FreeBSD.ORG Subject: More RAID/disklabel woes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I started over with the system, formatting all 12 drives. On boot everything looks OK: avalanche:dmiller# dmesg |egrep "asr|da" [snip stuff from before booting] asr0: mem 0xd8000000-0xd9ffffff irq 10 at device 14 1 on pci0 asr0: major=154 asr0: ADAPTEC 3200S FW Rev. 370F, 2 channel, 256 CCBs, Protocol I2O pass2 at asr0 bus 0 target 15 lun 0 pass4 at asr0 bus 1 target 15 lun 0 da0 at asr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Tagged Queueing Enabled da0: 86830MB (177827840 512 byte sectors: 255H 63S/T 11069C) da1 at asr0 bus 0 target 5 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Tagged Queueing Enabled da1: 17366MB (35566461 512 byte sectors: 255H 63S/T 2213C) da2 at asr0 bus 1 target 13 lun 0 da2: Fixed Direct Access SCSI-3 device da2: Tagged Queueing Enabled da2: 17366MB (35566461 512 byte sectors: 255H 63S/T 2213C) The fdisk looks OK with both RAID and JBOD drive: avalanche:dmiller# fdisk da0 ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=11112 heads=254 sectors/track=63 (16002 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=11112 heads=254 sectors/track=63 (16002 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 0,(unused) start 0, size 177823422 (86827 Meg), flag 0 beg: cyl 0/ head 0/ sector 1; end: cyl 828/ head 253/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: avalanche:dmiller# fdisk da1 ******* Working on device /dev/da1 ******* parameters extracted from in-core disklabel are: cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 35551782 (17359 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: ... but it just doesn't want to disklabel: avalanche:dmiller# disklabel -w -r da0 auto disklabel: /dev/da0c: Undefined error: 0 avalanche:dmiller# disklabel -w -r da1 auto disklabel: No space left on device The details: Adaptec 3200S raid controller, flashed with firmware from adaptecs site yesterday. Dell 2100S 12 drive scsi enclosure with split backplane. FreeBSD 4.5R. I've tried setting termination on and ultra-3 rates on the 3200S. The only difference was that at the ULTRA-3 setting the disklabel on da0 also gave a "no space left on device" message. Other possibly useful info: avalanche:dmiller# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 5 lun 0 (pass1,da1) at scbus0 target 15 lun 0 (pass2) at scbus1 target 13 lun 0 (pass3,da2) at scbus1 target 15 lun 0 (pass4) avalanche:dmiller# camcontrol inquiry 0:0:0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number + camcontrol: error getting transfer settings avalanche:dmiller# camcontrol inquiry 0:5:0 pass1: Fixed Direct Access SCSI-3 device pass1: Serial Number 3CC0S1MA000072071MCY camcontrol: error getting transfer settings Ideas welcome:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 18 23:57:37 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from utility.clubscholarship.com (utility.clubscholarship.com [198.78.70.175]) by hub.freebsd.org (Postfix) with ESMTP id 3402137B40F for ; Sat, 18 May 2002 23:57:30 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4J6r0W16018; Sat, 18 May 2002 23:53:01 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Sat, 18 May 2002 23:53:00 -0700 (PDT) From: Patrick Thomas To: Tom Samplonius Cc: Subject: Re: how do I know when RAID fails ? (mylex, PERC, etc) In-Reply-To: Message-ID: <20020518192557.V44320-100000@utility.clubscholarship.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Well...hot yanking drives bothers me - when they are expensive drives, and the possibility exists of killing the drive by yanking it (a drive that is otherwise healthy) I am reluctant to do this just to test. What about PERC ? Do _all_ the raid drivers have a facility to log to syslog when bad things happen, or is it dependent on the particular driver ? --pt On Fri, 17 May 2002, Tom Samplonius wrote: > > On Fri, 17 May 2002, Patrick Thomas wrote: > > ... > > So the question is, what happens when I am happily running along, and a > > drive fails ? Certainly things keep running, since they are mirrors, but > > how do I know a drive has failed ? > > > > Does the driver report to syslog ? > ... > > The mly driver logs to syslog. I'm surprised you haven't done a > simulated drive failure (just remove a drive while the array is running). > I always do that with every server to make sure everything is working, > particular that the SAFTE enclosure reports that a drive has installed to > trigger the autorebuild. > > Tom > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message