Re: cdrecord problems
On Tue, Dec 18, 2001 at 01:52:13PM -0500, yugami wrote:
> try running xcdroast and seeing if you can get that setup and working first.
>
No luck. :-( I think there is problem with cdrecord, both gcombust and
xcdroast use this util to write to CD.
Here goes log info:
Calling: /usr/lib/xcdroast-0.98/bin/xcdrwrap CDRECORD dev= "0,1,0"
fs=4096k -v driveropts=burnproof speed=4 -eject -pad tsize=64720s -
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Linux sg driver version: 3.1.20
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
TOC Type: 1 = CD-ROM
Using libscg version 'schily-0.5'
Driveropts: 'burnproof'
atapi: 1
Device type : Removable CD-ROM
Version : 0
Response Format: 1
Vendor_info : 'PLEXTOR '
Identifikation : 'CD-R PX-W1610A'
Revision : '1.04'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
Driver flags : SWABAUDIO
Drive buf size : 1190112 = 1162 KB
FIFO size : 4194304 = 4096 KB
cdrecord: Drive needs to reload the media to return to proper status.
Track 01: data 126 MB padsize: 30 KB
Total size: 145 MB (14:23.16) = 64737 sectors
Lout start: 145 MB (14:25/12) = 64737 sectors
Current Secsize: 2048
ATIP info from disk:
Indicated writing power: 6
Reference speed: 0
Is not unrestricted
Is erasable
ATIP start of lead in: -11078 (97:34/22)
ATIP start of lead out: 359849 (79:59/74)
speed low: 0 speed high: 4
power mult factor: 3 5
recommended erase/write power: 3
A2 values: 5C C6 26
Disk type: Phase change
Manuf. index: 11
Manufacturer: Mitsubishi Chemical Corporation
Trying to clear drive status.
Blocks total: 1166730 Blocks current: 1166730 Blocks remaining: 1101993
Starting to write CD/DVD at speed 4 in write mode for single0 seconds.
Operation starts.
Waiting for reader process to fill input buffer ...
cdrecord: Turning BURN-Proof on
input buffer ready.
Performing OPC...
Writing time: 8.804s
cdrecord: Input/output error. read track info: scsi sendcmd: no error
Fixating...
CDB: 52 01 00 00 00 FF 00 00 1C 00
Fixating time: 0.001s
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 240s
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 05 00 00 00 00 0A 00 00 00 00 2C 04 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x2C Qual 0x04 (current program area is empty) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 480s
cmd finished after 0.000s timeout 480s
cdrecord: fifo had 64 puts and 0 gets.
cdrecord: fifo was 0 times empty and 0 times full, min fill was 100%.
<!-- till here -->
>
> ----- Original Message -----
> From: "Patrik Modesto" <mody@quick.cz>
> To: <debian-user@lists.debian.org>
> Sent: Tuesday, December 18, 2001 1:29 PM
> Subject: cdrecord problems
>
>
> > Hi,
> > I'm out of ideas, so I need Your help. I'm trying to write some files to
> > CD-RW, but without success. :-( I'm using Debian Woody (daily updated),
> > with custom kernel 2.4.16 (enabled scsi emulation, reiserfs, ext3). I
> > tried everything I found in CD-Writing howto, but still no good. Only
> > few Kb gets on CD. Dummy mode is off. Funny is, that I can do fast-erase
> > of CD-RW disk. Full-erase freezes whole Gnome. :-(
> > Can someone help?
> >
> > Thanks
> >
> > Patrik
> >
> > Here is some info:
> >
> > cdrecord -scanbus:
> > -----------------
> > Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
> > Linux sg driver version: 3.1.20
> > Using libscg version 'schily-0.5'
> > scsibus0:
> > 0,0,0 0) 'IOMEGA ' 'ZIP 100 ' '14.A' Removable
> > Disk
> > 0,1,0 1) 'PLEXTOR ' 'CD-R PX-W1610A' '1.04'
> > Removable CD-ROM
> > 0,2,0 2) *
> > 0,3,0 3) *
> > 0,4,0 4) *
> > 0,5,0 5) *
> > 0,6,0 6) *
> > 0,7,0 7) *
> >
> >
> > gcombust - cdrecord output:
> > --------------------------
> > Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
> > TOC Type: 1 = CD-ROM
> > Using libscg version 'schily-0.5'
> > Driveropts: 'burnproof'
> > atapi: 1
> > Device type : Removable CD-ROM
> > Version : 0
> > Response Format: 1
> > Vendor_info : 'PLEXTOR '
> > Identifikation : 'CD-R PX-W1610A'
> > Revision : '1.04'
> > Device seems to be: Generic mmc CD-RW.
> > Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> > Driver flags : SWABAUDIO
> > Drive buf size : 1190112 = 1162 KB
> > FIFO size : 4194304 = 4096 KB
> > Track 01: data 126 MB padsize: 30 KB
> > Lout start: 145 MB (14:25/12) = 64737 sectors
> > Current Secsize: 2048
> > ATIP info from disk:
> > Indicated writing power: 6
> > Reference speed: 0
> > Is not unrestricted
> > Is erasable
> > ATIP start of lead in: -11078 (97:34/22)
> > ATIP start of lead out: 359849 (79:59/74)
> > speed low: 0 speed high: 4
> > power mult factor: 3 5
> > recommended erase/write power: 3
> > A2 values: 5C C6 26
> > Disk type: Phase change
> > Manuf. index: 11
> > Manufacturer: Mitsubishi Chemical Corporation
> > Blocks total: 359849 Blocks current: 359849 Blocks
> > remaining: 295112
> > Starting to write CD/DVD at speed 4 in write mode
> > for single session.
> > scsidev: '0,1,0'
> > scsibus: 0 target: 1 lun: 0
> > Linux sg driver version: 3.1.20iCdrecord 1.10
> > (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg
> > Schilling
> > TOC Type: 1 = CD-ROM
> > Using libscg version 'schily-0.5'
> > Driveropts: 'burnproof'
> > atapi: 1
> > Device type : Removable CD-ROM
> > Version : 0
> > Response Format: 1
> > Vendor_info : 'PLEXTOR '
> > Identifikation : 'CD-R PX-W1610A'
> > Revision : '1.04'
> > Device seems to be: Generic mmc CD-RW.
> > Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> > Driver flags : SWABAUDIO
> > Drive buf size : 1190112 = 1162 KB
> > FIFO size : 4194304 = 4096 KB
> > Track 01: data 126 MB padsize: 30 KB
> > Lout start: 145 MB (14:25/12) = 64737 sectors
> > Current Secsize: 2048
> > ATIP info from disk:
> > Indicated writing power: 6
> > Reference speed: 0
> > Is not unrestricted
> > Is erasable
> > ATIP start of lead in: -11078 (97:34/22)
> > ATIP start of lead out: 359849
> > (79:59/74)
> > speed low: 0 speed high: 4
> > power mult factor: 3 5
> > recommended erase/write power: 3
> > A2 values: 5C C6 26
> > Disk type: Phase change
> > Manuf. index: 11
> > Manufacturer: Mitsubishi
> > Chemical Corporation
> > Blocks total: 359849 Blocks
> > current: 359849 Blocks
> > remaining: 295112
> > Starting to write CD/DVD at
> > speed 4 in write mode for single
> > session.
> > scsidev: '0,1,0'
> > scsibus: 0 target: 1 lun: 0
> > Linux sg driver version: 3.1.20
> > Performing OPC...
> > /usr/bin/cdrecord: Turning
> > BURN-Proof on
> >
> > /usr/bin/cdrecord: Input/output
> > error. write_g1: scsi sendcmd:
> > retryable error
> > CDB: 2A 00 00 00 00 1F 00 00 1F
> > 00
> > status: 0x0 (GOOD STATUS)
> > cmd finished after 0.933s
> > timeout 40s
> > Track 01: 0 of 126 MB written.
> > write track data: error after
> > 63488 bytes
> > Trouble flushing the cache
> > Writing time: 11.943s
> > Sense Bytes: 70 00 00 00 00 00
> > 00 0A 00 00 00 00 00 00 00 00 00
> > 00
> > /usr/bin/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 06 00 00 00
> > 00 0A 00 00 00 00 29 00 00 00
> > Sense Key: 0x6 Unit Attention,
> > Segment 0
> > Sense Code: 0x29 Qual 0x00
> > (power on, reset, or bus device
> > reset occurred) Fru 0x0
> > Sense flags: Blk 0 (not valid)
> > cmd finished after 0.000s
> > timeout 120s
> > /usr/bin/cdrecord: fifo had 65
> > puts and 2 gets.
> > /usr/bin/cdrecord: fifo was 0
> > times empty and 1 times full,
> > min fill was 98%.
> >
> > /var/log/messages:
> > -----------------
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: DMA disabled
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: ATAPI reset complete
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x49 { DriveReady
> > DataRequest Error }
> > Dec 18 19:18:16 mody kernel: hdd: status error: error=0x04
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:16 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:16 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:17 mody kernel: hdd: ATAPI reset complete
> > Dec 18 19:18:17 mody kernel: hdd: status error: status=0x49 { DriveReady
> > DataRequest Error }
> > Dec 18 19:18:17 mody kernel: hdd: status error: error=0x04
> > Dec 18 19:18:17 mody kernel: hdd: drive not ready for command
> > Dec 18 19:18:22 mody kernel: hdd: status error: status=0x58 { DriveReady
> > SeekComplete DataRequest }
> > Dec 18 19:18:22 mody kernel: hdd: drive not ready for command
> >
> >
> > --
> > To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
> >
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: