From owner-freebsd-questions@FreeBSD.ORG Wed Sep 15 18:36:56 2004 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 0684816A4CE for ; Wed, 15 Sep 2004 18:36:56 +0000 (GMT) Received: from zeus.itg.uiuc.edu (zeus.itg.uiuc.edu [130.126.126.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id A260F43D41 for ; Wed, 15 Sep 2004 18:36:55 +0000 (GMT) (envelope-from philipp1@zeus.itg.uiuc.edu) Received: from zeus.itg.uiuc.edu (localhost.localdomain [127.0.0.1]) by zeus.itg.uiuc.edu (8.12.11/8.12.11) with ESMTP id i8FIahnH004442; Wed, 15 Sep 2004 13:36:43 -0500 Received: (from philipp1@localhost) by zeus.itg.uiuc.edu (8.12.11/8.12.11/Submit) id i8FIahRF004440; Wed, 15 Sep 2004 13:36:43 -0500 Date: Wed, 15 Sep 2004 13:36:43 -0500 From: Anthony Philipp To: marju ignatjeva Message-ID: <20040915183643.GA2565@zeus.itg.uiuc.edu> References: <200405171432.38987.4711@chello.at> <20040915063328.GA8455@zeus.itg.uiuc.edu> <20040915113547.K236@localhost.starman.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040915113547.K236@localhost.starman.ee> User-Agent: Mutt/1.4.1i cc: freebsd-questions@freebsd.org Subject: Re: cd stuck in cd drive after failed burn 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: Wed, 15 Sep 2004 18:36:56 -0000 On Wed, Sep 15, 2004 at 11:59:44AM +0300, marju ignatjeva wrote: > Hi, > offering a rude solution and _mostly_ asking for help on the same issue... > > On Wed, 15 Sep 2004, Anthony Philipp wrote: > > After burning trying to burn a cd with too much information on it, it ended up with this error. > > > > only wrote -1 of 37632 bytes: Input/output error > > > > burncd: ioctl(CDRIOCFLUSH): Input/output error > > > > But the cd was stuck in the drive, and would not respond when I pressed the eject button. I was just wondering if this was a common error or just a bug that since been fixed. Also if this happens again, is there a way to force a cd eject without rebooting? I am running FreeBSD-5.2-RELEASE. Thanks for the help. > > I've had a similar experience with my no-brand ATAPI cd-r device (the > motherboard is i440LX which doesn't in fact recognize the drive as to its > BIOS; my FreeBSD 4.8-R is able to mount data cds and reads them OK); so > anyway, the burncd fixating process always fails to finish the cd (the > writing part is always fine), > does not respond and after receiving CTRL-C outputs the friendly > cd9660: /dev/acd0c: Input/output > or something similar to your > burncd: ioctl(CDRIOCFLUSH)): Input/output error > AND the cd gets stuck, the drive doesn't respond. > Some kernel messages have always been issued, however I wasn't able to > find them in the log files known to me (where does the system log media > read/write errors and the like?). > > My rough and rude solution to removing the stuck cd has usually been > 1) try to mount the failed cd on purpose (results in > cd9660: /dev/acd0c: Input/output error or > cd9660: /dev/acd0c: Invalid argument ) > 2) then try to umount /cdrom on purpose (results in > umount: /cdrom: not currently mounted) > after which i have usually been able to get in touch with the drive again > and remove the disk. > Sounds pretty (very) violent to me. > > So on one hand, it has been possible to remove the now-useless disk > without rebooting (well, the very last time the system actually > _did_ crash along with a continous beep), but... > > So whoever is trying to lend a helping hand, please share your opinions on > whether it might be the old and tired motherboard that has problems with > my cd-r drive (in my case) (enabling or disabling DMA has not changed > matters)? > Or might some other solutions be looked for? > The mailing lists I have scanned through have not offered anything > relevant or helpful regarding this issue. > > Lastly, I have tested the same drive with a different board which managed > to recognize the drive as to its BIOS, however, no burncd software was > available at that occasion. > > Thanks a lot in advance, > > marju Well I should probably add that I have only experienced this problem once, and that usually burning a cd goes just fine, I have burned plenty of cds with it before. So if anyone has any idea whether it is a software or hardware bug, I would really appreciate the feedback. Thanks again Anthony