From owner-freebsd-scsi Sun May 19 5: 9:53 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from axel.truedestiny.net (a185066.upc-a.chello.nl [62.163.185.66]) by hub.freebsd.org (Postfix) with ESMTP id D03F137B40C; Sun, 19 May 2002 05:09:39 -0700 (PDT) Received: by axel.truedestiny.net (Postfix, from userid 1000) id 5A54E49AB2; Sun, 19 May 2002 14:09:40 +0200 (CEST) Date: Sun, 19 May 2002 14:09:40 +0200 From: Axel Scheepers To: richard childers Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@freebsd.org Subject: Re: "/dev/nsa0: Device not configured" Message-ID: <20020519140939.J64761@mars.thuis> Reply-To: Axel Scheepers References: <3CE676F4.64768D6F@pacbell.net> <3CE68E5C.7EBC1DDE@pacbell.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3CE68E5C.7EBC1DDE@pacbell.net>; from fscked@pacbell.net on Sat, May 18, 2002 at 10:24:44AM -0700 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 Sat, May 18, 2002 at 10:24:44AM -0700, richard childers wrote: > (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 So FreeBSD doesn't probe it right, no driver gets installed and hence you can't use /dev/nsa0 since there's nothing on it. > > 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. Very strange, the driver seems to be updated a lot since 4.3 you might take a look at the changes from that version to get a clue what's causing this. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/aic7xxx/ahc_pci.c It is that controller right? > > 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. Indeed, since no driver gets loaded the existance of a device is totally irrelevant here. Your /dev/nsa0 does exist and is fine. There's just no driver loaded for your drive. Did you check if your tape drive was doing anything the moment it got probed? It might be still rewinding/initialising the tape or so, and that might cause the faulty probe too. > > > -- richard > Gr, -- Axel Scheepers UNIX System Administrator email: axel@axel.truedestiny.net a.scheepers@iae.nl http://axel.truedestiny.net/~axel ------------------------------------------ A new koan: If you have some ice cream, I will give it to you. If you have no ice cream, I will take it away from you. It is an ice cream koan. ------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 19 9:21:22 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 34C6937B422 for ; Sun, 19 May 2002 09:20:49 -0700 (PDT) Received: from bremen.shuttle.de (localhost [127.0.0.1]) by bremen.shuttle.de (Postfix) with ESMTP id DD3B317E9E for ; Sun, 19 May 2002 18:09:04 +0200 (CEST) Received: (from uucp@localhost) by bremen.shuttle.de (8.12.3/8.12.3/Debian -4) with UUCP id g4JG94Ne028378 for freebsd-scsi@freebsd.org; Sun, 19 May 2002 18:09:04 +0200 Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) by hal9000.schweikhardt.net (8.12.3/8.12.3) with ESMTP id g4JE3FeC059964 for ; Sun, 19 May 2002 16:03:15 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.3/8.12.3/Submit) id g4JE3FuE059963 for freebsd-scsi@freebsd.org; Sun, 19 May 2002 16:03:15 +0200 (CEST) Date: Sun, 19 May 2002 16:03:14 +0200 From: Jens Schweikhardt To: FreeBSD SCSI Subject: Adaptec BIOS update with On-Board aic7880 and additional 29160 Message-ID: <20020519160314.B42731@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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 hello, world\n a question before I shoot myself in the foot. I've got an ASUS P2L97-S with an on-board aic7880 and an Adaptec 29160 PCI card, e.g. $ dmesg|grep ahc ahc0: port 0xd000-0xd0ff mem 0xdf800000-0xdf800fff irq 15 at device 6.0 on pci0 ahc1: port 0xb800-0xb8ff mem 0xdf000000-0xdf000fff irq 12 at device 11.0 on pci0 Of course, each of them has its own (different) bios. I want to update the bios on the 29160, so I got the 29160_bios_3100.exe from the adaptec support site. If I start the bios upgrade (from an OS that shall remain nameless) will it be smart enough to not update the wrong bios? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 19 11:36:12 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 3703937B405 for ; Sun, 19 May 2002 11:36:08 -0700 (PDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 179Uh4-0003RC-00; Sun, 19 May 2002 10:42:06 -0700 Date: Sun, 19 May 2002 10:42: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: <20020518192557.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 Sat, 18 May 2002, Patrick Thomas wrote: > 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. Well, if the drives dies during a hotswap out, it can't be that good of a drive to begin with. If the warranty is already over, and potential replacement is a concern, they are definitely not expensive. I love those 5 year warranties. > 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 > ? There are many PERC cards. What driver is it using? What does that driver's manpage say? > --pt Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 19 14:25:13 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2BAE337B408 for ; Sun, 19 May 2002 14:25:09 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4JLOxZ51028; Sun, 19 May 2002 15:24:59 -0600 (MDT) (envelope-from ken) Date: Sun, 19 May 2002 15:24:59 -0600 From: "Kenneth D. Merry" To: Jens Schweikhardt Cc: FreeBSD SCSI Subject: Re: Adaptec BIOS update with On-Board aic7880 and additional 29160 Message-ID: <20020519152458.A50807@panzer.kdm.org> References: <20020519160314.B42731@schweikhardt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020519160314.B42731@schweikhardt.net>; from schweikh@schweikhardt.net on Sun, May 19, 2002 at 04:03:14PM +0200 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 Sun, May 19, 2002 at 16:03:14 +0200, Jens Schweikhardt wrote: > hello, world\n > > a question before I shoot myself in the foot. I've got an ASUS P2L97-S > with an on-board aic7880 and an Adaptec 29160 PCI card, e.g. > $ dmesg|grep ahc > ahc0: port 0xd000-0xd0ff > mem 0xdf800000-0xdf800fff irq 15 at device 6.0 on pci0 > ahc1: port 0xb800-0xb8ff > mem 0xdf000000-0xdf000fff irq 12 at device 11.0 on pci0 > > Of course, each of them has its own (different) bios. I want to update > the bios on the 29160, so I got the 29160_bios_3100.exe from the adaptec > support site. If I start the bios upgrade (from an OS that shall remain > nameless) will it be smart enough to not update the wrong bios? The Adaptec BIOS upgrade programs typically check the PCI ID of the chip/board against the PCI ID embedded in the BIOS file, and won't allow you to put the wrong BIOS on the wrong board. Also, most motherboards with embedded Adaptec chips (this probably applies to other vendors as well) include the Adaptec SCSI BIOS in the same image as the system BIOS. (So the bios update mechanism would probably be somewhat different for the onboard controller anyway.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 19 22:44:25 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 4B4EC37B410 for ; Sun, 19 May 2002 22:44:22 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4K5dpW82786; Sun, 19 May 2002 22:39:51 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Sun, 19 May 2002 22:39:51 -0700 (PDT) From: Patrick Thomas To: Tom Samplonius Cc: Subject: more information on PERC failures (RAID) In-Reply-To: Message-ID: <20020519223238.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 ok, I read the man page and release notes for `aac` and found that there is a kernel option: AAC_DEBUG which allows me to: The adapter can send status and alert messages asynchronously to the driver. These messages are printed on the system console, and are also queued for retrieval by a management application. So, two questions come to mind: 1. is syslog ever involved ? It seems like the answer is no, since even when you set AAC_DEBUG, it just logs to console and are "queued for retrieval by a management application". 2. where is this management application ? No clues are given in the manpage in terms of related files... thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 19 22:47:22 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 EECF937B40B for ; Sun, 19 May 2002 22:47:19 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4K5guh82915; Sun, 19 May 2002 22:42:56 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Sun, 19 May 2002 22:42:56 -0700 (PDT) From: Patrick Thomas To: Tom Samplonius Cc: Subject: related PERC topic - are adaptec PERC 3/Di safe with FreeBSD ? In-Reply-To: Message-ID: <20020519223955.F44320-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 Background: http://cvs.openbsd.org/cgi-bin/wwwgnats.pl/full/2415 I realize this is an openBSD bug - but just to be on the safe side (since subsequent list discussion told stories of dead/locked servers) Is PERC 3/Di safe with 4.5-RELEASE ? Will I encounter any lockups or errors as related to this bug report ? thanks, pt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 20 3: 9:59 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from itursa.com (213-98-177-112.uc.nombres.ttd.es [213.98.177.112]) by hub.freebsd.org (Postfix) with ESMTP id A81D037B427 for ; Mon, 20 May 2002 03:09:49 -0700 (PDT) Received: from CAMINO1 by itursa.com with SMTP (MDaemon.Standard.v5.0.1.R) for ; Mon, 20 May 2002 12:07:51 +0200 From: "Camino Conde" To: Subject: Date: Mon, 20 May 2002 12:08:25 +0200 Message-ID: <000901c1ffe5$614f86c0$3c01a8c0@CAMINO1> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Return-Path: CConde@itursa.com X-MDaemon-Deliver-To: scsi@freebsd.org 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 ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- -------------------- CAMINO CONDE Iturralde y Sagüés, INGENIEROS Sancho el Fuerte 49 Bajo 31007 Pamplona (Navarra) Tfno: 948 199 400 Fax: 948 199 401 e-mail: CConde@itursa.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 20 9:59:21 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by hub.freebsd.org (Postfix) with ESMTP id 1287337BDB3 for ; Mon, 20 May 2002 09:37:31 -0700 (PDT) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.10.2+Sun/8.10.2) with ESMTP id g4KGZLj17535; Mon, 20 May 2002 09:35:21 -0700 (PDT) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id JAA21512; Mon, 20 May 2002 09:35:19 -0700 (PDT) Received: from btcexc01.btc.adaptec.com (btcexc01 [10.100.0.23]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id KAA12780; Mon, 20 May 2002 10:35:14 -0600 (MDT) Received: by btcexc01.btc.adaptec.com with Internet Mail Service (5.5.2653.19) id ; Mon, 20 May 2002 10:35:15 -0600 Message-ID: <2C7CBDC6EA58D6119E4A00065B3A24CB046351@btcexc01.btc.adaptec.com> From: "Long, Scott" To: "'Patrick Thomas'" , Tom Samplonius Cc: freebsd-scsi@freebsd.org Subject: RE: related PERC topic - are adaptec PERC 3/Di safe with FreeBSD ? Date: Mon, 20 May 2002 10:35:08 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain 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 Patrick, I thought that I sent you an email on Saturday that answered your questions, but maybe you did not receive it. Recap: The aac RAID family (of which the PERC3/Di is a member) will send text messages to the host driver when something particularly bad happens. This includes drive failure, unexpected bus resets, and array failures. These messages will appear on the FreeBSD console, and will be copied to the syslog. Dell distributes a set of management tools for the card for Linux. If you compile the aac driver with AAC_COMPAT_LINUX (see /sys/i386/conf/LINT for details), you can use these tools. They will allow you to control and monitor the card and arrays, create/delete arrays, etc. There is also an SNMP agent, but I have not tested it yet. You can also pick up the FreeBSD native tools from the Adaptec website if you look for the Adaptec 5400S card. If I have time, I'll see what I can do about making the SNMP agent work. So the answer to your concern is 'yes, you will know when something bad happens'. As for OpenBSD, I really have not paid attention to their camp. The FreeBSD driver is written and sponsored by Adaptec, while the OpenBSD driver is not. Hmmm... it seems to be a port of my driver. Maybe they haven't caught up with all of the bug fixes yet. Scott > -----Original Message----- > From: Patrick Thomas [mailto:root@utility.clubscholarship.com] > Sent: Sunday, May 19, 2002 11:43 PM > To: Tom Samplonius > Cc: freebsd-scsi@freebsd.org > Subject: related PERC topic - are adaptec PERC 3/Di safe with > FreeBSD ? > > > > Background: > > http://cvs.openbsd.org/cgi-bin/wwwgnats.pl/full/2415 > > I realize this is an openBSD bug - but just to be on the safe > side (since > subsequent list discussion told stories of dead/locked servers) > > Is PERC 3/Di safe with 4.5-RELEASE ? Will I encounter any lockups or > errors as related to this bug report ? > > thanks, > > pt > > > 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 Mon May 20 10:20:32 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 0D2D337B41A for ; Mon, 20 May 2002 10:18:49 -0700 (PDT) Received: from localhost (root@localhost) by utility.clubscholarship.com (8.11.6/8.11.6) with ESMTP id g4KHE6w18049; Mon, 20 May 2002 10:14:06 -0700 (PDT) (envelope-from root@utility.clubscholarship.com) Date: Mon, 20 May 2002 10:14:05 -0700 (PDT) From: Patrick Thomas To: "Long, Scott" Cc: Tom Samplonius , Subject: RE: related PERC topic - are adaptec PERC 3/Di safe with FreeBSD ? In-Reply-To: <2C7CBDC6EA58D6119E4A00065B3A24CB046351@btcexc01.btc.adaptec.com> Message-ID: <20020520101226.B44320-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 Thank you - I appreciate your help. However the one item I am still not clear on is, will _anything_ go to syslog if I don't have AAC_DEBUG on ? Or is AAC_DEBUG required for even the most basic of messages (like "hey a drive just failed") thanks! On Mon, 20 May 2002, Long, Scott wrote: > Patrick, > > I thought that I sent you an email on Saturday that answered your > questions, but maybe you did not receive it. > > Recap: > > The aac RAID family (of which the PERC3/Di is a member) will send > text messages to the host driver when something particularly bad > happens. This includes drive failure, unexpected bus resets, > and array failures. These messages will appear on the FreeBSD > console, and will be copied to the syslog. > > Dell distributes a set of management tools for the card for Linux. > If you compile the aac driver with AAC_COMPAT_LINUX (see > /sys/i386/conf/LINT for details), you can use these tools. They > will allow you to control and monitor the card and arrays, > create/delete arrays, etc. There is also an SNMP agent, but I > have not tested it yet. You can also pick up the FreeBSD native > tools from the Adaptec website if you look for the Adaptec 5400S > card. If I have time, I'll see what I can do about making the > SNMP agent work. > > So the answer to your concern is 'yes, you will know when > something bad happens'. As for OpenBSD, I really have not paid > attention to their camp. The FreeBSD driver is written and > sponsored by Adaptec, while the OpenBSD driver is not. Hmmm... > it seems to be a port of my driver. Maybe they haven't caught > up with all of the bug fixes yet. > > Scott > > > -----Original Message----- > > From: Patrick Thomas [mailto:root@utility.clubscholarship.com] > > Sent: Sunday, May 19, 2002 11:43 PM > > To: Tom Samplonius > > Cc: freebsd-scsi@freebsd.org > > Subject: related PERC topic - are adaptec PERC 3/Di safe with > > FreeBSD ? > > > > > > > > Background: > > > > http://cvs.openbsd.org/cgi-bin/wwwgnats.pl/full/2415 > > > > I realize this is an openBSD bug - but just to be on the safe > > side (since > > subsequent list discussion told stories of dead/locked servers) > > > > Is PERC 3/Di safe with 4.5-RELEASE ? Will I encounter any lockups or > > errors as related to this bug report ? > > > > thanks, > > > > pt > > > > > > 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 May 21 2:51: 0 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 2F80037B409 for ; Tue, 21 May 2002 02:50:54 -0700 (PDT) Received: from cicely5.cicely.de (cicely5.cicely.de [IPv6:3ffe:400:8d0:301:200:92ff:fe9b:20e7]) (authenticated bits=0) by srv1.cosmo-project.de (8.12.3/8.12.3) with ESMTP id g4L9oeHc085793 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 21 May 2002 11:50:45 +0200 (CEST) (envelope-from ticso@cicely5.cicely.de) Received: from cicely5.cicely.de (localhost [IPv6:::1]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g4L9oc95076628 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 21 May 2002 11:50:38 +0200 (CEST)?g (envelope-from ticso@cicely5.cicely.de) Received: (from ticso@localhost) by cicely5.cicely.de (8.12.1/8.12.1/Submit) id g4L9oaDu076627; Tue, 21 May 2002 11:50:36 +0200 (CEST)?g (envelope-from ticso) Date: Tue, 21 May 2002 11:50:35 +0200 From: Bernd Walter To: David Miller Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: More RAID/disklabel woes Message-ID: <20020521095035.GH72276@cicely5.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely5.cicely.de 5.0-CURRENT i386 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 Sat, May 18, 2002 at 11:30:22PM -0400, David Miller wrote: > 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: > Fine - you have allocated space for slice 1. > 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: > Also fine - allocated space for slice 1. > ... 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 Of course it won't. First you need to disklabel da0s1 and da1s1 because you have created a slice fdisk partition table. And you might to wipe out the first blocks of a slice to create a virgin disklabel. E.g. dd if=/dev/zero bs=64k count=10 of=/dev/da1s1 Finaly you want to read the Handbook section about adding new disks - it's all explained there. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 21 8:56:55 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from vinyl2.sentex.ca (vinyl2.sentex.ca [199.212.134.13]) by hub.freebsd.org (Postfix) with ESMTP id 9021337B403; Tue, 21 May 2002 08:56:30 -0700 (PDT) Received: from house.sentex.net (cage.simianscience.com [64.7.134.1]) (authenticated bits=0) by vinyl2.sentex.ca (8.12.3/8.12.2) with ESMTP id g4LFuPdd047562 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO); Tue, 21 May 2002 11:56:27 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20020521114013.0555e948@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 21 May 2002 11:56:24 -0400 To: freebsd-scsi@freebsd.org From: Mike Tancsa Subject: tape changer problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 Since our backups are getting bigger and bigger, I figured it was time for a tape changer. We picked up a Sony TSL-9000 which *seems* to work ok. Before I move to something like Amanda, I wanted to at least go through the process manually. Briefly, I can seeming dump out to multiple volumes, but never read beyond the first tape. So far I have tried the following 1) Load up the mag with 8 tapes. 2) chio move drive 0 slot 0 At this point, chio status -S shows backup2# chio status -S picker 0: source: <> slot 0: source: <> slot 1: source: <> slot 2: source: <> slot 3: source: <> slot 4: source: <> slot 5: source: <> slot 6: source: <> slot 7: source: <> drive 0: source: <> backup2# Looks good so far. 3) dump -0 -u -a -n -f /dev/nrsa1 /tmpbackup 4) When prompted because the tape runs out, I issue a mt -f /dev/nrsa1 offline and chio status shows that I am pointing to the next slot. I then continue with the dump on the next tape. Once everything is written out mt -f /dev/nrsa1 offline until I am at the start again and do a chio move drive 0 slot 0. Note, I dont know if its a limitation of the unit, but I can never do a move until I return the unit to its native position (i.e. the position right after I physically put the magazine in.) So far so good (it seems) Now I try a restore. restore -rf /dev/nrsa1 or restore -i -f /dev/nrsa1 add my files and start at vol 1 From the first tape all is restoring great. But when it hits the end of the tape, I get an error and Tape read error while trying to resynchronize with the following in kern.* May 19 21:55:37 backup2 /kernel: (sa1:ahc0:0:5:0): SCB 0x3 - timed out May 19 21:55:37 backup2 /kernel: ahc0: Dumping Card State while idle, at SEQADDR 0x8 May 19 21:55:37 backup2 /kernel: ACCUM = 0x0, SINDEX = 0x38, DINDEX = 0xe4, ARG_2 = 0x0 May 19 21:55:37 backup2 /kernel: HCNT = 0x0 SCBPTR = 0x6 May 19 21:55:37 backup2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0x6 May 19 21:55:37 backup2 /kernel: DFCNTRL = 0x0, DFSTATUS = 0x89 May 19 21:55:37 backup2 /kernel: LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x80 May 19 21:55:37 backup2 /kernel: SSTAT0 = 0x0, SSTAT1 = 0xa May 19 21:55:37 backup2 /kernel: STACK == 0x3, 0x10d, 0x165, 0xec May 19 21:55:38 backup2 /kernel: SCB count = 140 May 19 21:55:38 backup2 /kernel: Kernel NEXTQSCB = 23 May 19 21:55:38 backup2 /kernel: Card NEXTQSCB = 23 May 19 21:55:38 backup2 /kernel: QINFIFO entries: May 19 21:55:38 backup2 /kernel: Waiting Queue entries: May 19 21:55:38 backup2 /kernel: Disconnected Queue entries: 18:3 May 19 21:55:38 backup2 /kernel: QOUTFIFO entries: May 19 21:55:38 backup2 /kernel: Sequencer Free SCB List: 6 11 21 2 15 14 1 5 25 28 12 13 30 26 9 19 31 0 4 20 16 3 27 23 17 29 22 1 0 8 24 7 May 19 21:55:38 backup2 /kernel: Sequencer SCB Info: 0(c 0x60, s 0x47, l 0, t 0xff) 1(c 0x60, s 0x47, l 0, t 0xff) 2(c 0x60, s 0x27, l 0, t 0xff) 3(c 0x60, s 0x47, l 0, t 0xff) 4(c 0x60, s 0x27, l 0, t 0xff) 5(c 0x60, s 0x27, l 0, t 0xff) 6(c 0x60, s 0x27, l 0, t 0xff) 7(c 0x60, s 0x47, l 0, t 0xff) 8(c 0x40, s 0x57, l 0, t 0xff) 9(c 0x60, s 0x27, l 0, t 0xff) 10(c 0x60, s 0x47, l 0, t 0xff) 1 1(c 0x60, s 0x27, l 0, t 0xff) 12(c 0x60, s 0x27, l 0, t 0xff) 13(c 0x60, s 0x47, l 0, t 0xff) 14(c 0x60, s 0x27, l 0, t 0xff) 15(c 0x60, s 0x47, l 0, t 0xff) 16(c 0x60, s 0x27, l 0, t 0xff) 17(c 0x40, s 0x57, l 0, t 0xff) 18(c 0x44, s 0x57, l 0, t 0x3) 19(c 0x60, s 0x27, l 0, t 0xff) 20(c 0x60, s 0x27, l 0, t 0xff) 21(c 0x60, s 0x27, l 0, t 0xff) 22(c 0x60, s 0x27, l 0, t 0xff) 23(c 0x60, s 0 x27, l 0, t 0xff) 24(c 0x60, s 0x47, l 0, t 0xff) 25(c 0x60, s 0x47, l 0, t 0xff) 26(c 0x60, s 0x27, l 0, t 0xff) 27(c 0x60, s 0x27, l 0, t 0xff) 28(c 0x60, s 0x47, l 0, t 0xff) 29(c 0x60, s 0x47, l 0, t 0xff) 30(c 0x60, s 0x47, l 0, t 0xff) 31(c 0x60, s 0 May 19 21:55:38 backup2 /kernel: , t 0xff) May 19 21:55:38 backup2 /kernel: Pending list: 3(c 0x40, s 0x57, l 0) May 19 21:55:38 backup2 /kernel: Kernel Free SCB list: 56 15 66 95 99 7 88 6 10 86 34 32 83 138 71 122 60 76 67 93 78 36 43 77 29 12 1 58 11 17 81 68 18 44 20 64 0 73 94 1 13 87 12 4 33 52 47 46 92 97 96 28 50 139 59 35 80 54 120 79 82 45 30 65 98 49 61 22 72 5 123 124 125 126 127 128 129 110 111 112 113 114 115 116 117 118 119 100 101 102 103 104 105 106 107 108 109 90 91 74 40 9 27 63 62 8 48 38 24 57 16 42 37 41 69 39 75 89 19 51 21 31 26 85 2 53 25 55 70 84 14 137 136 135 134 133 132 131 130 May 19 21:55:38 backup2 /kernel: Untagged Q(5): 3 May 19 21:55:38 backup2 /kernel: sg[0] - Addr 0x13c82000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[1] - Addr 0x130c3000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[2] - Addr 0x2e0c4000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[3] - Addr 0x4725000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[4] - Addr 0x22aa6000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[5] - Addr 0x1bfa7000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[6] - Addr 0xb228000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[7] - Addr 0x3c49000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[8] - Addr 0x2594a000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[9] - Addr 0x1dc2b000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[10] - Addr 0x2906c000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[11] - Addr 0x2f6d000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[12] - Addr 0x504e000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[13] - Addr 0x698f000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[14] - Addr 0xa4d0000 : Length 4096 May 19 21:55:38 backup2 /kernel: sg[15] - Addr 0x1b71000 : Length 4096 May 19 21:55:38 backup2 /kernel: (sa1:ahc0:0:5:0): Queuing a BDR SCB May 19 21:55:38 backup2 /kernel: (sa1:ahc0:0:5:0): Bus Device Reset Message Sent May 19 21:55:38 backup2 /kernel: (sa1:ahc0:0:5:0): no longer in timeout, status = 34b May 19 21:55:38 backup2 /kernel: ahc0: Bus Device Reset on A:5. 1 SCBs aborted May 19 22:04:11 backup2 /kernel: (sa1:ahc0:0:5:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM command to clear this state. I try a mt -f /dev/nrsa1 offline to move to the next tape, but no dice on continuing the restore. The machine is 4.6-RC FreeBSD 4.6-RC #1: Thu May 16 16:56:59 EDT 2002 May 16 17:00:30 backup2 /kernel: Copyright (c) 1992-2002 The FreeBSD Project. May 16 17:00:30 backup2 /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 16 17:00:30 backup2 /kernel: The Regents of the University of California. All rights reserved. May 16 17:00:30 backup2 /kernel: FreeBSD 4.6-RC #1: Thu May 16 16:56:59 EDT 2002 May 16 17:00:30 backup2 /kernel: mdtancsa@backup2.sentex.ca:/usr/obj/usr/src/sys/backup May 16 17:00:30 backup2 /kernel: Timecounter "i8254" frequency 1193182 Hz May 16 17:00:30 backup2 /kernel: Timecounter "TSC" frequency 803413761 Hz May 16 17:00:30 backup2 /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (803.41-MHz 686-class CPU) May 16 17:00:30 backup2 /kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 May 16 17:00:30 backup2 /kernel: Features=0x383f9ff May 16 17:00:30 backup2 /kernel: real memory = 805224448 (786352K bytes) May 16 17:00:30 backup2 /kernel: config> q May 16 17:00:30 backup2 /kernel: avail memory = 779894784 (761616K bytes) May 16 17:00:30 backup2 /kernel: Preloaded elf kernel "kernel" at 0xc0366000. May 16 17:00:30 backup2 /kernel: Preloaded userconfig_script "/boot/kernel.conf" at 0xc036609c. May 16 17:00:30 backup2 /kernel: netsmb_dev: loaded May 16 17:00:30 backup2 /kernel: Pentium Pro MTRR support enabled May 16 17:00:30 backup2 /kernel: md0: Malloc disk May 16 17:00:30 backup2 /kernel: Using $PIR table, 7 entries at 0xc00f1250 May 16 17:00:30 backup2 /kernel: npx0: on motherboard May 16 17:00:30 backup2 /kernel: npx0: INT 16 interface May 16 17:00:30 backup2 /kernel: pcib0: on motherboard May 16 17:00:30 backup2 /kernel: pci0: on pcib0 May 16 17:00:30 backup2 /kernel: pcib2: at device 1.0 on pci0 May 16 17:00:30 backup2 /kernel: pci1: on pcib2 May 16 17:00:30 backup2 /kernel: pci1: at 0.0 May 16 17:00:30 backup2 /kernel: isab0: at device 4.0 on pci0 May 16 17:00:30 backup2 /kernel: isa0: on isab0 May 16 17:00:30 backup2 /kernel: atapci0: port 0xb800-0xb80f at device 4.1 on pci0 May 16 17:00:30 backup2 /kernel: ata0: at 0x1f0 irq 14 on atapci0 May 16 17:00:30 backup2 /kernel: ata1: at 0x170 irq 15 on atapci0 May 16 17:00:30 backup2 /kernel: pci0: (vendor=0x1106, dev=0x3057) at 4.4 May 16 17:00:30 backup2 /kernel: fxp0: port 0xa800-0xa81f mem 0xf9000000-0xf90fffff,0xfd000000-0xf d000fff irq 11 at device 13.0 on pci0 May 16 17:00:30 backup2 /kernel: fxp0: Ethernet address 00:a0:c9:89:d5:ba May 16 17:00:30 backup2 /kernel: inphy0: on miibus0 May 16 17:00:30 backup2 /kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 16 17:00:30 backup2 /kernel: atapci1: port 0x9000-0x90ff,0x9400-0x9403,0x9800-0x9807,0xa000 -0xa003,0xa400-0xa407 irq 10 at device 14.0 on pci0 May 16 17:00:30 backup2 /kernel: ata2: at 0xa400 on atapci1 May 16 17:00:30 backup2 /kernel: ata3: at 0x9800 on atapci1 May 16 17:00:30 backup2 /kernel: fxp1: port 0x8800-0x881f mem 0xf8800000-0xf88fffff,0xfc000000-0xf c000fff irq 12 at device 15.0 on pci0 May 16 17:00:30 backup2 /kernel: fxp1: Ethernet address 00:90:27:25:bf:8b May 16 17:00:30 backup2 /kernel: inphy1: on miibus1 May 16 17:00:30 backup2 /kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 16 17:00:30 backup2 /kernel: ahc0: port 0x8400-0x84ff mem 0xf8000000-0xf8000fff irq 11 at dev ice 17.0 on pci0 May 16 17:00:30 backup2 /kernel: aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs May 16 17:00:30 backup2 /kernel: pcib1: on motherboard May 16 17:00:30 backup2 /kernel: pci2: on pcib1 May 16 17:00:30 backup2 /kernel: orm0: