Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Jan 1999 20:27:36 -0500
From:      Nathan Dorfman <nathan@rtfm.net>
To:        Alfred Perlstein <bright@hotjobs.com>, "John W. DeBoskey" <jwd@unx.sas.com>
Cc:        freebsd-hackers@FreeBSD.ORG
Subject:   Re: cdrecord / projected & actual sizes don't seem right
Message-ID:  <19990105202736.B16219@rtfm.net>
In-Reply-To: <Pine.BSF.4.05.9901041738150.37756-100000@bright.fx.genx.net>; from Alfred Perlstein on Mon, Jan 04, 1999 at 05:41:40PM -0500
References:  <199901042116.QAA28139@bb01f39.unx.sas.com> <Pine.BSF.4.05.9901041738150.37756-100000@bright.fx.genx.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 04, 1999 at 05:41:40PM -0500, Alfred Perlstein wrote:
> 
> On Mon, 4 Jan 1999, John W. DeBoskey wrote:
> 
> > Hi,
> > 
> >    I'm using cdrecord 1.6.1 on a -current system. I've run into
> > a size/time issue that I don't seem to have any luck figuring out.
> > 
> >    I am using 73 minute cd-r media. When I run cdrecord to write
> > the isofs to the cd media, everything seems to work correctly, but
> > the process is stopping prematurely. Could someone with more 
> > experience shed some light on where I need to look to figure out
> > what I'm doing wrong? The sense Blk invalid msg below is also
> > interesting.
> 
> i just purchased my own CD-RW, ( i think it's the same model as yours ) 
> 
> try running cdrecord with nice -18: (from the man page)
> 
> cd /cdwork 
> nice -18 cdrecord dev=5,0 speed=4 -v cd1.image 
> 
> try not to jostle (sp?) the machine while recording, what i mean is don't
> start up something likely to cause pageing, it'll probably ruin the burn.
> 
> you may even want to run it with 'rtprio' but i haven't tried that myself
> yet.
> 
> i just got it last night and had a bit of trouble using RW media, but i
> haven't tried it with 'nice -18' yet, i'll see what helps me in that
> situation and post about it.

I have the same CD-RW drive (Yamaha CDRW-4260), running cdrecord 1.6.1
on -current. I have no problems with burning whatsoever. I never run
cdrecord with any special priorities (nice, rtprio, etc.). On the contrary,
it always runs with X running, and Netscape, mp3 player, and other
miscellaneous applications are sometimes open. Never any buffer overruns
or anything similar, I've never even noticed the fifo dip below 95% full!

John, as for your error, I have never seen it before but it looks like
it writes the data fine and then chokes on fixate...nice -anything
wouldn't affect this as it's not a buffer overrun but some kind of real
error. How many times have you tried it? Maybe the media is faulty? Try
a different brand of CD-R media and see if you get the same error?

Al, as for your error, I've been using RW media with cdrecord, -current,
and the CDRW4260 ever since I got it. What's the problem you're having?
Maybe you're forgetting that a) you need to blank CDRW media before recording
onto it, cdrecord blank=all or b) the drive writes RW media at 2x, so set
speed=2.

> -Alfred
> 
> > 
> > Oh well,
> > Thanks!
> > John
> > 
> > Fixating...
> > cdrecord: Input/output error. close track/session: scsi sendcmd: retryable error
> > CDB:  5B 00 02 00 00 00 00 00 00 00
> > status: 0x2 (CHECK CONDITION)
> > Sense Bytes: 70 00 04 D1 C0 00 00 0A 00 00 00 00 09 01 00 00 00 00 00 00 00 08 00 00 00 00 00 00 08 00 01 06
> > Sense Key: 0x4 Hardware Error, Segment 0
> > Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0
> > Sense flags: Blk -775946240 (not valid) 
> > cmd finished after 41.576s timeout 480s
> > Fixating time:   43.587s
> > cdrecord: fifo had 9194 puts and 9127 gets.
> > cdrecord: fifo was 0 times empty and 9126 times full, min fill was 98%.

-- 
   ________________    ___________________________________________
  / Nathan Dorfman \  / "`IE4 brings the web to UNIX'? *laughing*
 / nathan@rtfm.net  \/ Isn't that similar to Ronald McDonald bringing
/ finger for PGP key \ religion to the pope?" -Jamie Bowden

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



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