Re: cdrecord issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Okay, now that it looks that it is writing CDs, I went to burn the first
iso image of fc3. Here is what I received using cdrecord:

cdrecord -v -eject speed=4 FC3-i386-disc1.iso
cdrecord: No write mode specified.
cdrecord: Asuming -tao mode.
cdrecord: Future versions of cdrecord may have different drive dependent
default s.
cdrecord: Continuing in 5 seconds...
Cdrecord-Clone 2.01-dvd (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg
Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to
http://bugzilla.redhat.com/ bugzilla
Note: The author of cdrecord should not be bothered with problems in
this versio n.
TOC Type: 1 = CD-ROM
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using
setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version
(schily - Red Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c       
1.83 04/05/20 Copyright 1997 J. Schilling').
Driveropts: 'burnfree'
SCSI buffer size: 64512
atapi: 1
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'HL-DT-ST'
Identifikation : 'DVDRAM GSA-4160B'
Revision       : 'A300'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009
Profile: 0x0012
Profile: 0x0011
Profile: 0x0014
Profile: 0x0013
Profile: 0x001A
Profile: 0x001B
Profile: 0x002B
Profile: 0x0010
Profile: 0x0009 (current)
Profile: 0x000A
Profile: 0x0008
Profile: 0x0002
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P
RAW/R96R
Drive buf size : 1053696 = 1029 KB
cdrecord: Success. read buffer: scsi sendcmd: no error
CDB:  3C 00 00 00 00 00 00 FC 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 10 87 69 65 80 08 03 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error
(ultra-dma/32))  Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 64512
cmd finished after 0.004s timeout 40s
FIFO size      : 4194304 = 4096 KB
Track 01: data   617 MB
Total size:      708 MB (70:12.18) = 315914 sectors
Lout start:      708 MB (70:14/14) = 315914 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in:  -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 43932
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
cdrecord: Permission denied. WARNING: Cannot set priority using
setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
Speed set to 706 KB/s
Starting to write CD/DVD at speed   4.0 in real TAO mode for single
session.
Last chance to quit, starting real write    0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
trackno=0
BURN-Free is ON.
Performing OPC...
Starting new track at sector: 0
Track 01:    3 of  617 MB written (fifo 100%) [buf  99%]  
4.2x.cdrecord: Succes s. write_g1: scsi sendcmd: no error
CDB:  2A 00 00 00 07 25 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 10 77 22 FA 80 08 03 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x03 (logical unit communication crc error
(ultra-dma/32))  Fru 0x0
Sense flags: Blk 0 (not valid)
resid: 63488
cmd finished after 0.101s timeout 40s
 
write track data: error after 3745792 bytes
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
Writing  time:   17.565s
Average write speed 240.4x.
Min drive buffer fill was 99%
Fixating...
Fixating time:   63.191s
cdrecord: fifo had 123 puts and 60 gets.
cdrecord: fifo was 0 times empty and 47 times full, min fill was 79%.

It seems to burn small files with no problem, but when I use large
files, I get the same message.

I have tried searching through the archives, but I couldn't find issue
similar to mine.

Any suggestions?

Thanks!

Chris

On Sun, 2004-12-05 at 09:43, Paul Howarth wrote:
> On Sun, 2004-12-05 at 01:22 +0100, Alexander Dalloz wrote:
> > Am Sa, den 04.12.2004 schrieb Christian Del Pino um 23:25:
> > > What I typed in that made it work was cdrecord dev=cdrom, as in my
> > > cdrecord.conf file. Now my question, is my conf file wrong, or do I need
> > > to reconfigure that cd burning apps with the correct device name?
> > 
> > "cdrecord dev=cdrom" is wrong IMHO. The proper syntax is
> > 
> > cdrecord dev=/dev/hdc ...
> > 
> > or if you did set your burning device in the cdrecord.conf, you then
> > don't need to pass cdrecord any information about the device to use.
> 
> Nothing wrong with dev=cdrom (if cdrom is a named device is
> cdrecord.conf), but it's usually redundant when there's only one cd
> writing device specified in cdrecord.conf. However, if there are
> multiple cd writing devices specified, dev=cdrom would be necessary in
> order to specify device "cdrom" rather than say "dvdwriter".
> 
> Paul.
> -- 
> Paul Howarth <paul@xxxxxxxxxxxx>


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux