From owner-freebsd-questions@FreeBSD.ORG Fri Apr 18 15:34:08 2003 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 52E8E37B401 for ; Fri, 18 Apr 2003 15:34:08 -0700 (PDT) Received: from newtonsecond.com (adsl-63-207-117-158.dsl.snfc21.pacbell.net [63.207.117.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 571F143FBF for ; Fri, 18 Apr 2003 15:34:07 -0700 (PDT) (envelope-from tristan11@mindspring.com) Received: from [12.43.53.1] (account michelle HELO mindspring.com) by newtonsecond.com (CommuniGate Pro SMTP 3.5.9) with ESMTP-TLS id 581635 for freebsd-questions@freebsd.org; Fri, 18 Apr 2003 15:34:04 -0700 Date: Fri, 18 Apr 2003 15:34:05 -0700 Mime-Version: 1.0 (Apple Message framework v551) From: Michelle Weeks To: In-Reply-To: <053701c305f8$c0886b60$0264a8c0@ovirt.dyndns.ws> Message-Id: X-Mailer: Apple Mail (2.551) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Re: cdrom - device not configured error 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: Fri, 18 Apr 2003 22:34:08 -0000 On Friday, April 18, 2003, at 03:20 PM, W. Sierke wrote: > "Michelle Weeks" wrote: >> i'm trying to mount /dev/acd0c and i keep getting the error "device >> not >> configured". the freebsd handbook states that either the drive does >> not think there is a cd in the tray or the machine can't see the drive >> on the bus. i've put the cd in the tray several times, tried multiple >> cds that can be read by another freebsd machine and still the error >> "device not configured". this is a production server and i would like >> to avoid bringing the server down if at all possible. is there a way >> to tell if the machine can see the cdrom drive on the bus? or is >> there >> something else that could be causing this behavior? > > atacontrol should be useful. Note the warnings in the manpage about > potential (bad!) results of incorrect usage, however! But should be > fine to > use the 'list' command for this purpose: > > # atacontrol list > ATA channel 0: > Master: ad0 ATA/ATAPI rev 6 > Slave: no device present > ATA channel 1: > Master: acd0 ATA/ATAPI rev 0 > Slave: no device present > > That should at least tell you if it's seeing the drive. You could > perhaps > try the "reinit" command on the appropriate channel (if it only has the > cdrom, etc. on it), but perhaps only as a last resort in case it has > unwanted consequences! It's quite possible that the drive is simply no > longer serviceable. :( > > thank you wayne. i tried the command atacontrol list and get the following error: atacontrol: control device not found: No such file or directory?