Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Sep 2004 16:36:45 -0500
From:      Anthony Philipp <philipp1@itg.uiuc.edu>
To:        "Sheets, Jason (OZ CEEDR)" <jason.sheets@hp.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: cd stuck in cd drive after failed burn
Message-ID:  <20040915213645.GA6029@zeus.itg.uiuc.edu>
In-Reply-To: <2D8BB15C7B5C214F81C32D3A83B3273601186722@idbexc01.americas.cpqcorp.net>
References:  <2D8BB15C7B5C214F81C32D3A83B3273601186722@idbexc01.americas.cpqcorp.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 15, 2004 at 02:26:03PM -0600, Sheets, Jason (OZ CEEDR) wrote:
> I would consider this a hardware problem, what type of media are you
> using?  
> 
> There is usually a whole in the front of the drive that allows you to
> insert a paper clip or other object to physically open the drive as long
> as it is not in use.
> 
> I've had drives hang because of a failed burn with low quality media, it
> also depends on the quality of the drive itself and the quality of the
> firmware on the drive, those companies that skimp on firmware
> development time have less reliable drives.
> 
> Did you upgrade or alter the OS in any way since you saw this problem,
> is it reproducible, if so have you tried using a different media or
> burning the media at a slower speed (just because media claims to work
> at say 48X doesn't mean all drives will be capable of burning it
> successfully at 48X).
> 
> Jason
Well I did insert the paper clip into the drive, and it did not respond. I have not had time to try and reproduce it, but I have burned cds with this media at 32x before with no problems. In fact I've done this many times, but this is the first time I've had the problem with the cd getting stuck in the drive. Also I have not changed the OS since. I dont really have access to other media since I bought 100 of these, but they've worked before so I have no reason to suspect the media. I'll try to reproduce it tonight.
Thanks for your response
Anthony

> 
> > -----Original Message-----
> > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-
> > questions@freebsd.org] On Behalf Of Anthony Philipp
> > Sent: Wednesday, September 15, 2004 12:37 PM
> > To: marju ignatjeva
> > Cc: freebsd-questions@freebsd.org
> > Subject: Re: cd stuck in cd drive after failed burn
> > 
> > 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
> > _______________________________________________
> > freebsd-questions@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "freebsd-questions-
> > unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040915213645.GA6029>