From owner-freebsd-questions@FreeBSD.ORG Fri Apr 18 15:19:15 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 32CEA37B404 for ; Fri, 18 Apr 2003 15:19:15 -0700 (PDT) Received: from mail.airnet.com.au (mail.airnet.com.au [202.174.32.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 8827C43F93 for ; Fri, 18 Apr 2003 15:19:13 -0700 (PDT) (envelope-from ws@senet.com.au) Received: (qmail 16900 invoked from network); 18 Apr 2003 22:19:12 -0000 Received: from dsl2-81.gw1.adl1.airnet.com.au (HELO predatorii) (202.174.37.81) by mail.airnet.com.au with SMTP; 18 Apr 2003 22:19:12 -0000 Message-ID: <053701c305f8$c0886b60$0264a8c0@ovirt.dyndns.ws> From: "W. Sierke" To: "Michelle Weeks" , References: Date: Sat, 19 Apr 2003 07:50:43 +0930 Organization: OVirt Technologies MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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:19:15 -0000 "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. :( Good luck with it. Wayne