On Thu, 2003-09-25 at 11:55, John Richard Smith wrote:
<snip>
The test files were assembled with mkisofs along the lines you mention. They write out to the CD-RW OK.
then write to disc<snip>
tmp]$ cdrecord -v speed=4 dev=0,0,0 -eject -ignsize /tmp.iso (where dev=0,0,0 is whatever it should be on your system, ie cdrecord -scanbus, and speed is whatever is appropiate for your device)
I've used your cdrecord command - no joy.It's slightly different from
the one I used (cdrecord -v speed=2 dev=0,0,0 -data /tmp.iso)
There is a slight difference in the output at Sense Code:
here - Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
whereas it was -
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
I wondered whether that might mean cdrecord's power settings for CD-Rs on the Sony CDwriter were incorrect, whereas they were satisfactory for writing CD-RWs. What do you think?
DougB
"cdrecord -v speed=2 dev=0,0,0 -eject -ignsize corrimage Cdrecord 2.0 (i586-mandrake-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '0,0,0' scsibus: 0 target: 0 lun: 0 Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' atapi: 1 Device type : Removable CD-ROM Version : 0 Response Format: 1 Vendor_info : 'SONY ' Identifikation : 'CD-RW CRX175E2 ' Revision : 'S002' Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : MMC-2 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R Drive buf size : 1359872 = 1328 KB FIFO size : 4194304 = 4096 KB Track 01: data 0 MB padsize: 312 KB Total size: 0 MB (00:04.02) = 302 sectors Lout start: 1 MB (00:06/02) = 302 sectors Current Secsize: 2048 ATIP info from disk: Indicated writing power: 4 Is not unrestricted Is not erasable Disk sub type: Medium Type A, low Beta category (A-) (2) ATIP start of lead in: -12508 (97:15/17) ATIP start of lead out: 359848 (79:59/73) Disk type: Short strategy type (Phthalocyanine or similar) Manuf. index: 22 Manufacturer: Ritek Co. Blocks total: 359848 Blocks current: 359848 Blocks remaining: 359546 Forcespeed is OFF. Starting to write CD/DVD at speed 4 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. BURN-Free is ON. Turning BURN-Free off Performing OPC... Starting new track at sector: 0 Track 01: 0 of 0 MB written. Track 01: writing 312 KB of pad data. Track 01: Total bytes read/written: 294912/614400 (300 sectors). cdrecord: Input/output error. flush cache: scsi sendcmd: no error CDB: 35 00 00 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 03 00 00 00 00 0C 00 00 00 00 0C 00 00 00 Sense Key: 0x3 Medium Error, Segment 0 Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 5.073s timeout 120s Trouble flushing the cache Writing time: 15.920s Average write speed 0.8x. Fixating... cdrecord: Input/output error. close track/session: scsi sendcmd: no error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 03 00 00 00 00 0C 00 00 00 00 0C 00 00 00 Sense Key: 0x3 Medium Error, Segment 0 Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 40.434s timeout 480s cmd finished after 40.434s timeout 480s Fixating time: 40.438s cdrecord: fifo had 5 puts and 5 gets. cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%"
The only difference.
I think your on to something, take a look at, http://www.mail-archive.com/[EMAIL PROTECTED]/msg04341.html http://www.mail-archive.com/[EMAIL PROTECTED]/msg04350.html http://www.psychology4u.de/mcguinness/brenner_error.txt http://www.ale.org/archive/ale/ale-2000-09/msg00624.html
from man cdrecord,
DIAGNOSTICS
You have 9 seconds to type ^C to abort cdrecord after you see the mes-
sage:
Starting to write CD at speed %d in %s mode for %s session.
A typical error message for a SCSI command looks like:
cdrecord: I/O error. test unit ready: scsi sendcmd: no error
CDB: 00 20 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 25 00 00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x25 Qual 0x00 (logical unit not supported) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 40s
The first line gives information about the transport of the command.
The text after the first colon gives the error text for the system call
from the view of the kernel. It usually is: I/O error unless other
problems happen. The next words contain a short description for the
SCSI command that fails. The rest of the line tells you if there were
any problems for the transport of the command over the SCSI bus. fatal
error means that it was not possible to transport the command (i.e. no
device present at the requested SCSI address).
The second line prints the SCSI command descriptor block for the failed
command.
The third line gives information on the SCSI status code returned by
the command, if the transport of the command succeeds. This is error
information from the SCSI device.
The fourth line is a hex dump of the auto request sense information for
the command.
The fifth line is the error text for the sense key if available, fol-
lowed by the segment number that is only valid if the command was a
copy command. If the error message is not directly related to the cur-
rent command, the text deferred error is appended.
The sixth line is the error text for the sense code and the sense qual-
ifier if available. If the type of the device is known, the sense data
is decoded from tables in scsierrs.c . The text is followed by the
error value for a field replaceable unit.
The seventh line prints the block number that is related to the failed
command and text for several error flags. The block number may not be
valid.
The eight line reports the timeout set up for this command and the time
that the command really needed to complete.
Douglas, We are both on a learning curve here.
The sixth line is the error text for the sense code and the sense qual- ifier if available. If the type of the device is known, the sense data is decoded from tables in scsierrs.c
Question is , what is sense code ? , what is sense qualifier if available ?
I don't know, but at a pure outright guess I would say perhaps it is looking for a text identifyer built into the device, which is also stored in "tables in scsierrs.c" wherever that may be and cannot find one, but as I say I'm no expert.
Maybe others can help because at some time or other we will all come across such problems. Here is where I need advice too.
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
