From owner-freebsd-current Tue Sep 29 11:33:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12650 for freebsd-current-outgoing; Tue, 29 Sep 1998 11:33:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12525 for ; Tue, 29 Sep 1998 11:32:30 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.8.8) with SMTP id OAA04546; Tue, 29 Sep 1998 14:31:57 -0400 (EDT) (envelope-from scrappy@hub.org) Date: Tue, 29 Sep 1998 14:31:57 -0400 (EDT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: current@FreeBSD.ORG Subject: Re: [CAM?] Device not configured... In-Reply-To: <199809291806.MAA18359@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Sep 1998, Justin T. Gibbs wrote: > In article you wrote: > > da5: Fixed Direct Access SCSI2 device > > You should be running L915 on that drive. L912 is known to occassionally > go out to lunch. Ya, we caught on to that one shortly after I sent out the message, the drive has been removed and is being replaced tomorrow morning...*sigh* > > How can I get it back, short of rebooting the system? If I can? > > Use camcontrol to see if the system still can see the device. If it > can't, use camcontrol -r to rescan for it. You will have to > "umount -f" any filesystems that reference the device before the system > will allow you to access them normally. Will log this one...ended up rebooting th emachine, and the drive didn't come back up any better then it was...camcontrol won't have done any good :( Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message