TCLUG Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TCLUG:7972] CDR burning
Use a lower speed. Set the speed to 2 or 4. The fifo should
never get empty and that is what is happening when data is
being written to the CDR.
Hope this helps
--
sandipan
Bob Tanner wrote:
>
> Quoting mailinglists (mlists@mad-seumas.net):
> > On Fri, 27 Aug 1999, Bob Tanner wrote:
> >
> > > Using cdrecord, can someone give me the command line to copy a iso format
> > > CD in /dev/cdrom to my cdr in /dev/scd0 using 8x for writting?
> >
> > cdrecord -v dev=0,x,0 speed=8 -isosize /dev/cdrom
> > (bus,id,lun)
> >
> > In case you forget again she's in the CD-Writing HOWTO :)
>
> Read It, Learn It, Lived It.
>
> This is the error I get burning RedHat's Sparc Linux Disk 1.
>
> Track 01: 339 MB written (fifo 0%).cdrecord: Input/output error. write_g1:
> scsi sendcmd: retryable error
> CDB: 2A 00 00 02 A7 80 00 00 10 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: F0 00 03 00 02 A8 18 0A 00 00 00 00 0C 09 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x0C Qual 0x09 (write error - loss of streaming) Fru 0x0
> Sense flags: Blk 174104 (valid)
> cmd finished after 0.111s timeout 40s
>
> write track data: error after 356253696 bytes
> 68.46% done, estimate finish Fri Aug 27 16:46:51 1999
> Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00
> Writing time: 306.393s
> Fixating...
> Fixating time: 34.173s
> cdrecord: fifo had 11064 puts and 10873 gets.
> cdrecord: fifo was 937 times empty and 15 times full, min fill was 0%.
> Broken pipe
>