From owner-freebsd-questions@FreeBSD.ORG Fri Apr 18 19:11:54 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 1544D37B401 for ; Fri, 18 Apr 2003 19:11:54 -0700 (PDT) Received: from smtp0.adl1.internode.on.net (smtp0.adl1.internode.on.net [203.16.214.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD35743FCB for ; Fri, 18 Apr 2003 19:11:52 -0700 (PDT) (envelope-from Malcolm.Kay@internode.on.net) Received: from beta.home (ppp1831.sa.padsl.internode.on.net [150.101.26.38]) h3J2BnZe005457; Sat, 19 Apr 2003 11:41:50 +0930 (CST) Content-Type: text/plain; charset="iso-8859-1" From: Malcolm Kay Organization: At home To: Michelle Weeks , Date: Sat, 19 Apr 2003 11:47:41 +0930 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200304191147.41296.Malcolm.Kay@internode.on.net> 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: Sat, 19 Apr 2003 02:11:54 -0000 On Sat, 19 Apr 2003 08:04, Michelle Weeks wrote: > 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 dri= ve > >> on the bus. i've put the cd in the tray several times, tried multip= le > >> cds that can be read by another freebsd machine and still the error > >> "device not configured". this is a production server and i would li= ke > >> to avoid bringing the server down if at all possible. is there a wa= y > >> 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 t= he > > 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 n= o > > 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? I am certainly no expert in this matter; but it sounds to me as though you might be missing /dev/ata which I think is used by atacontrol. If it is missing then from /dev running './MAKEDEV ata' might get atacont= rol=20 working. As an aside I have had problems with at least one FreeBSD release and cdrom on a master IDE port but no problem on a slave port. Malcolm Kay=20