error using K3B to burn cd-rw of Ubuntu ISO

Asked by Mike Miller

Using K3B to burn Ubuntu 8.10 ISO to cd-rw.

Error number 5 almost at start of operation

HERE IS THE LOG FILE:
---------------------------------------------------------------------------------------------------------------------------------------------
KDE Version: 3.5.10
QT Version: 3.3.8b
Kernel: 2.6.24-23-generic
Devices
-----------------------
ATAPI CD-R/RW CRW6206A 1.3A (/dev/scd1, ) [CD-R, CD-RW, CD-ROM] [Error] [TAO, RAW, RAW/R16]

PIONEER DVD-ROM DVD-105 1.33 (/dev/scd0, ) [CD-ROM, DVD-ROM] [DVD-ROM, CD-ROM] [None]
Used versions
-----------------------
cdrecord: 1.1.6

cdrecord
-----------------------
/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/scd1'
devname: '/dev/scd1'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.6
SCSI buffer size: 64512
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
TOC Type: 1 = CD-ROM
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'ATAPI '
Identification : 'CD-R/RW CRW6206A'
Revision : '1.3A'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC SWABAUDIO
Supported modes: TAO PACKET RAW/R16
Drive buf size : 393216 = 384 KB
FIFO size : 12582912 = 12288 KB
Speed set to 353 KB/s
Track 01: data 698 MB
Total size: 802 MB (79:30.64) = 357798 sectors
Lout start: 802 MB (79:32/48) = 357798 sectors
Current Secsize: 2048
  ATIP start of lead in: -11079 (97:34/21)
  ATIP start of lead out: 359849 (79:59/74)
Disk type: Phase change
Manuf. index: 11
Manufacturer: Mitsubishi Chemical Corporation
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 2051
Starting to write CD/DVD at speed 2.0 in real TAO mode for single session.
Last chance to quit, starting real write in 2 seconds.
   1 seconds.
   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Errno: 5 (Input/output error), send opc scsi sendcmd: no error
CDB: 54 01 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 03 00 00 00 00 0A 00 02 95 5C 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (valid)
cmd finished after 11.839s timeout 60s
/usr/bin/wodim: OPC failed.
Errno: 5 (Input/output error), start/stop unit scsi sendcmd: no error
CDB: 1B 00 00 00 02 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F0 00 04 00 00 00 00 0A 00 02 95 62 53 00 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x53 Qual 0x00 (media load or eject failed) Fru 0x0
Sense flags: Blk 0 (valid)
cmd finished after 0.033s timeout 40s
/usr/bin/wodim: Cannot eject media.
/usr/bin/wodim: fifo had 192 puts and 0 gets.
/usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was 100%.
Writing time: 11.939s

cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/scd1 speed=2 -tao -eject -data -tsize=357796s -
-------------------------------------------------------------------------------------------------------------------------------
END OF LOG FILE

Thank you to anyone who has any suggestions.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu cdrkit Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#1

Seems related to:

/usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/scd1' devname: '/dev/scd1'

Please read this already reported bug list... related to wodim (cdrkit)
https://bugs.launchpad.net/ubuntu/+source/cdrkit

Then consider to report new bug... from here:

https://answers.launchpad.net/ubuntu/+source/cdrkit/+question/62127/+makebug

Hope this helps

Can you help with this problem?

Provide an answer of your own, or ask Mike Miller for more information if necessary.

To post a message you must log in.