From owner-freebsd-questions@FreeBSD.ORG Thu Jul 29 01:57:31 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F18816A4CE for ; Thu, 29 Jul 2004 01:57:31 +0000 (GMT) Received: from richard2.pil.net (richard2.pil.net [208.8.16.11]) by mx1.FreeBSD.org (Postfix) with SMTP id A69A843D39 for ; Thu, 29 Jul 2004 01:57:30 +0000 (GMT) (envelope-from up@3.am) Received: (qmail 6167 invoked by uid 1825); 29 Jul 2004 01:57:21 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Jul 2004 01:57:21 -0000 Date: Wed, 28 Jul 2004 21:57:21 -0400 (EDT) From: up@3.am X-X-Sender: up@richard2.pil.net To: Dan Nelson In-Reply-To: <20040729011550.GA26125@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD ISP List cc: freebsd-questions@freebsd.org Subject: Re: DLT "device not configured" errors X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jul 2004 01:57:31 -0000 On Wed, 28 Jul 2004, Dan Nelson wrote: > In the last episode (Jul 28), up@3.am said: > > A few months ago I brought up a new server using an Adaptec 2200S RAID > > card, and it's been running fine with a RAID 1 array on channel 0. Today > > I tried to move the DLT (Quantum 4000) over to this server to make it the > > amanda server, so I plugged it into the controller's external port for > > channel 1. When I do, neither amanda or mt will see the device, I get: > > > > mt: /dev/nsa0: Device not configured > > This could mean that there's no tape in the drive. Does "camcontrol > devlist" see the drive? Also make sure you have the "aacp" device in the > kernel; that allows non-disk devices to pass through the raid controller and > be seen by FreeBSD. I should have added: camcontrol doesn't see *any* devices, including the disks (and a rescan does nothing either). I did not have the aacp option enabled, so I will also try that. It does not appear that any kernel options are neccessary for camcontrol to work, as it works in all my older (4.9 and earlier) versions with virtually the same kernel options as in this box (4.10) James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am =========================================================================