Date: Mon, 24 Apr 2000 00:03:34 GMT From: Salvo Bartolotta <bartequi@neomedia.it> To: Jim Conner <jconner@enterit.com>, freebsd-questions@FreeBSD.ORG Subject: Re: how to burn Message-ID: <20000424.33400@bartequi.ottodomain.org> References: <4.3.1.2.20000422171041.01f57320@pseudonet.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Well, then perhaps you could help me. I have posted the question many=
> a time here and no one has ever responded.
> (hist 528)# cdrecord -version
> Cdrecord release 1.8a21 Copyright (C) 1995-1999 J=F6rg Schilling
> (hist 529)# uname -v
> FreeBSD 3.4-RELEASE #5: Wed Feb 2 12:02:10 EST
> 2000 root@localhost:/usr/src/sys/compile/nj
> cd0: <SONY CD-R CDU920S 2.0c> Removable Worm SCSI-2 device
> cd0: 4.032MB/s transfers (4.032MHz, offset 15)
> cd0: cd present [316269 x 2048 byte records]
> cdrecord: No such file or directory. WARNING: RR-scheduler not
> available, disabling.
Dear Jim Conner,
I seem to understand the following:
1) you can burn under other Oses (e.g. Windoze);
2) you cannot burn under FreeSBD 3.4-Release.
If this is the case, **what** can you burn under, say, Windows ?
> fs: 4194304 buflen: 4198400
> cdrecord: shared memory segment attached: 2810c000
> buf: 2810C000 bufend: 2850D000, buflen: 4198400
> buf: 2810C000 bufend: 2850D000, buflen: 4198400 (align 0)
> File: '/services/etc_bak.iso' tracksize: 1089536 secsize: 2048
> tracktype: 3 =3D CD-ROM XA mode 2 sectype: 2 =3D CD-ROM mode 2=20
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ =20
You are trying to burn this tracktype.
> dbtype: CD-ROM XA mode 2 form 1 flags 10C0
This piece of information, taken from cdrecord(1) on my 3.4-STABLE
system, might be relevant:
<blockquote>
The Sony CDU-924 has been tested, but does not support XA-mode2 in
hardware.
The sony therefore cannot create conforming multi session disks.
</blockquote>
> dev: 1,6,0 speed: -1 fs: -1
> Cdrecord release 1.8a21 Copyright (C) 1995-1999 J^vrg Schilling
> TOC Type: 3 =3D CD-ROM XA mode 2
^^^^^^^^^^^^^^^^
> scsidev: '1,6,0'
> scsibus: 1 target: 6 lun: 0
> scsi_getbuf: 64512 bytes
> atapi: 0
> Device type : Removable WORM
> Version : 2
> Response Format: 2
> Capabilities : SYNC LINKED
> Vendor_info : 'SONY '
> Identifikation : 'CD-R CDU920S '
> Revision : '2.0c'
> Device seems to be: Sony CDU-924S.
^^^^^^^^^^^^^^
Here it comes into play.
> Using driver for Sony CDU-924 (sony_cdu924).
^^^^^^^^^^^^^^^^^^^^^^^^^^
We seem to have found the guilty party.=20
> Driver flags : SWABAUDIO
> Drive buf size : 1048576 =3D 1024 KB
> FIFO size : 4194304 =3D 4096 KB
> bufsize: 65536 buffers: 64 hdrsize 1024
> bufsize: 65536 buffers: 64 hdrsize 1024
> cdrecord: Undefined error: 0. WARNING: RR-scheduler not available,
disabling.
> Track 01: data 1 MB
> Total size: 1 MB (00:07.12) =3D 534 sectors
> Lout start: 1 MB (00:09/09) =3D 534 sectors
> Pages: 0x1 0x2 0x8 0xd 0xe 0x20 0x22 0x23 0x31
> Density: 0x0
> Blocks: 0
> Blocklen:2048
> Current Secsize: 2048
> ATIP info from disk:
> Indicated writing power: 4
> Is not unrestricted
> Disk application code: 0
> ATIP start of lead in: -11320 (97:31/05)
> ATIP start of lead out: 336225 (74:45/00)
> ATIP start of lead out: 336225 (74:45/00)
> Disk type: Phthalocyanine or similar
> Manuf. index: 22
> Manufacturer: Ritek Co.
> Blocks total: 336225 Blocks current: 336225 Blocks remaining: 335691
> Using 64 buffers of 64512 bytes.
> Starting to write CD/DVD at speed 1 in write mode for single session.
> Last chance to quit, starting real write in 1 seconds.
> Waiting for reader process to fill input-buffer ... cdrecord:
Input/output
> error. write_track: scsi sendcmd: retryable error
> status: 0x2 (CHECK CONDITION)
> input-buffer ready.
> CDB: F5 00 00 00 00 00 00 00 00 00
> Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 C9 00 00 00 00 00 00
00 20
> 06 00 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0xC9 Qual 0x00 (illegal block length for write command)
Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.018s timeout 40s
Another piece of information that might be useful, again from
cdrecord(1):
<blockquote>
DIAGNOSTICS
You have 9 seconds to type ^C to abort cdrecord after you
see the message:
Starting to write CD at speed %d in %s mode for %s ses-
sion.
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)
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 ker-
nel. It usually is: I/O error unless other problems hap-
pen. 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 pos-
sible 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, followed by the segment number that is only
valid if the command was a copy command. If the error mes-
sage is not directly related to the current command, the
text deferred error is appended.
The sixth line is the error text for the sense code and
the sense qualifier 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 following message is not an error:
Track 01: Total bytes read/written: 2048/2048 (1
sectors).
cdrecord: I/O error. flush cache: scsi sendcmd: no error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 05 80 00 00 27 0A 00 00 00 00 B5 00
00 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0xB5 Qual 0x00 (dummy data blocks added) Fru
0x0
Sense flags: Blk -2147483609 (valid)
It simply notifies, that a track that is smaller than the
minimum size has been expanded to 300 sectors.
</blockquote>
> Writing time: 0.186s
> Fixating...
> cdrecord: Input/output error. finalize: scsi sendcmd: retryable error
> status: 0x2 (CHECK CONDITION)
> CDB: F1 00 00 00 00 00 00 00 00 00
> Sense Bytes: 70 00 05 00 00 00 00 12 00 00 00 00 89 00 00 00 00 00 00
00 02
> 06 00 00 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x89 Qual 0x00 (inappropriate command) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.023s timeout 480s
> cdrecord: fifo had 18 puts and 0 gets.
> cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
> Fixating time: 0.023s
> That is the .out that Igot the last time I tried to burn an image to
> cdr. Any thoughts and ides would be nice. I've been attempting to
burn
> for about a year now.
> TIA
> - Jim
These errors might be of hardware and/or of software
nature (ie some bug.) Have you tried burning a **different** type of
track ?
<SUGGESTION I>
You should upgrade to 3.4-STABLE. Next, try the above-mentioned
operations again.
</SUGGESTION I>
<SUGGESTION II>
If you have the opportunity to do it, you should put a 4.0-STABLE
system on one of your "partitions" (in DOS parlance), and perform the
suggested tests with cdrecord. Some of the tests *might* be
successful whereas under 3.4-STABLE they might not.
</SUGGESTION II>
I hope this will somehow help you. If somebody more knowledgeable
about this specific issue is reading this letter, he or she is kindly
invited to jump in :-)
My best wishes and regards,
Salvo
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000424.33400>