From owner-freebsd-questions Sat May 18 10:21:27 2002 Delivered-To: freebsd-questions@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-questions@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-questions" in the body of the message