Summary: | Burning ISO image (DVD) to dual-layer disc fails unless 'Verify written data' is checked. | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Unknown <null> |
Component: | Video DVD | Assignee: | k3b developers <k3b> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | chymian, jca6433, joerg.schilling, perpsectiveoffice, trueg |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
URL: | http://forum.kde.org/viewtopic.php?f=153&t=101876 | ||
Latest Commit: | Version Fixed In: |
Description
Unknown
2012-05-04 17:49:33 UTC
This behaviour has occurred for me since Kubuntu Oneiric (2011). It happens with hardware I have been successfully using to burn DVDs and D/L DVDs on Kubuntu for years. It only happens when burning more than 3.8 GB of data onto a DVD. I have no problems burning DVDs with less data on them than that. It happens no matter whether I am using k3b, k9copy, or even Brasero or Gnomebaker. The symptoms are freezing when data burned reaches about 3.9 GB, or a k3b abort, or an unusable/unreadable disc, or the mysterious "error 254." It makes me think there is a problem with wodim and/or genisoimage/growisofs, which Debian-based systems have substituted in their cdrkit for cdrecord and mkisofs of cdrtools. Further, k3b currently allows no method for selecting the writing package even when cdrtools (cdrecord and mkisofs) is once again installed. If I'm not mistaken, genisoimage is used for DVDs and growisofs is used for D/L DVDs, and each preconfigures data for wodim to write. Something is wrong with this chain of writing events... Another possibility (Instead of a cdrkit/wodim/genisoimage/growisofs problem) is a recent (Dec 2011) change to libdvdread -- maybe this isn't fixed completely? libdvdread (4.2.0-1ubuntu3) precise; urgency=low * Add 103-iforead-tt-srpt-pointerfix.patch: Fix read/write beyond end of an array due to using a length value taken from the DVD, which can exceed the allocated size, causing a segmentation fault. (LP: #894170) I have the same bug here, debian wheezy/testing as of 14 nov. 2012. trying to write a DL-DVD throws error at 50% can someone please take responsibility for that! Devices ----------------------- Optiarc DVD RW AD-7740H 1.00 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R doppelschichtig, DVD+R, DVD+RW, DVD+R doppelschichtig) [DVD-ROM, DVD-R sequenziell, Zweischichtige DVD-R sequenziell, Zweischicht-DVD-R-Sprung, DVD-RAM, DVD-RW Eingeschränktes Überbrennen, DVD-RW sequenziell, DVD+RW, DVD+R, Zweischichtige DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Eingeschränktes Überschreiben, Sprung zwischen DVD-Schichten] [%7] System ----------------------- K3b Version: 2.0.2 KDE Version: 4.8.4 (4.8.4) QT Version: 4.8.2 Kernel: 3.6.6-trunk-amd64 Used versions ----------------------- cdrecord: 1.1.11 cdrecord ----------------------- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 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 Driveropts: 'burnfree' Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'Optiarc ' Identification : 'DVD RW AD-7740H ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x002B (DVD+R/DL) Profile: 0x002B (DVD+R/DL) (current) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd). Driver flags : SWABAUDIO BURNFREE Supported modes: PACKET SAO Drive buf size : 884736 = 864 KB FIFO size : 12582912 = 12288 KB Speed set to 8310 KB/s Track 01: data 7703 MB Total size: 8846 MB (876:29.01) = 3944176 sectors Lout start: 8847 MB (876:31/01) = 3944176 sectors Current Secsize: 2048 HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction. Blocks total: 4173824 Blocks current: 4173824 Blocks remaining: 229648 Starting to write CD/DVD at speed 6.0 in real SAO mode for single session. Last chance to quit, starting real write in 2 seconds. 1 seconds. 0 seconds. Operation starts. dvd_dual_layer_split: read_dvd_structure returns invalid data Preparing middle zone location for this DVD+R dual layer disc Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Sending CUE sheet... Starting new track at sector: 0 Track 01: 0 of 7703 MB written. Track 01: 1 of 7703 MB written (fifo 100%) [buf 62%] 0.3x. ... Track 01: 4075 of 7703 MB written (fifo 100%) [buf 94%] 6.1x. Track 01: 4076 of 7703 MB written (fifo 100%) [buf 38%] 1.4x. Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error CDB: 2A 00 00 1F D9 F8 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 03 00 00 00 00 0A 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 0.994s timeout 200s /usr/bin/wodim: A write error occured. /usr/bin/wodim: Please properly read the error message above. write track data: error after 4275027968 bytes Writing time: 779.123s Average write speed 7.6x. Min drive buffer fill was 38% Fixating... Errno: 5 (Input/output error), close track/session scsi sendcmd: no error CDB: 5B 00 04 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 72 03 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x72 Qual 0x03 (session fixation error - incomplete track in session) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 1000s Errno: 5 (Input/output error), close track/session scsi sendcmd: no error CDB: 5B 00 05 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 72 03 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x72 Qual 0x03 (session fixation error - incomplete track in session) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 1000s Fixating time: 0.007s /usr/bin/wodim: fifo had 67527 puts and 67337 gets. /usr/bin/wodim: fifo was 0 times empty and 33514 times full, min fill was 95%. cdrecord command: ----------------------- /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=6 -sao driveropts=burnfree -data -tsize=3944176s - I double checked with "Verify written data" checked. worked flawless. so, how can a verity command, which is executed after the write-process, influence the write process, so that a DL-disc is only half written? and I triple checked with same wodim cmd from bash, which was used by k3b, writing the same iso: worked flawless! so, definitely a k3b-bug! /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=6 -sao driveropts=burnfree -data -tsize=3944176s walter-1a.iso TOC Type: 1 = CD-ROM scsidev: '/dev/sr0' devname: '/dev/sr0' scsibus: -2 target: -2 lun: -2 Linux sg driver version: 3.5.27 Wodim version: 1.1.11 Driveropts: 'burnfree' SCSI buffer size: 64512 Device type : Removable CD-ROM Version : 5 Response Format: 2 Capabilities : Vendor_info : 'Optiarc ' Identification : 'DVD RW AD-7740H ' Revision : '1.00' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x002B (DVD+R/DL) Profile: 0x002B (DVD+R/DL) (current) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc DVD-R(W) driver (mmc_mdvd). Driver flags : SWABAUDIO BURNFREE Supported modes: PACKET SAO Drive buf size : 884736 = 864 KB Beginning DMA speed test. Set CDR_NODMATEST environment variable if device communication breaks or freezes immediately after that. FIFO size : 12582912 = 12288 KB Track 01: data 7703 MB Total size: 8846 MB (876:29.01) = 3944176 sectors Lout start: 8847 MB (876:31/01) = 3944176 sectors Current Secsize: 2048 HINT: use dvd+rw-mediainfo from dvd+rw-tools for information extraction. Blocks total: 4173824 Blocks current: 4173824 Blocks remaining: 229648 Speed set to 8310 KB/s Starting to write CD/DVD at speed 6.0 in real SAO mode for single session. Last chance to quit, starting real write in 0 seconds. Operation starts. Preparing middle zone location for this DVD+R dual layer disc dvd_dual_layer_split: read_dvd_structure returns invalid data Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Sending CUE sheet... Starting new track at sector: 0 Track 01: 7703 of 7703 MB written (fifo 100%) [buf 94%] 2.5x. Track 01: Total bytes read/written: 8077672448/8077672448 (3944176 sectors). Writing time: 1368.010s Average write speed 4.3x. Min drive buffer fill was 37% Fixating... Fixating time: 208.497s /usr/bin/wodim: fifo had 127232 puts and 127232 gets. /usr/bin/wodim: fifo was 0 times empty and 61900 times full, min fill was 95%. I don't mean to pile on here in this thread, and certainly don't want to get into the politics of the situation so I'm going to call this my wish for K3b. I had to learn the hard way, through this and other fora about how to use K3b to burn DL DVDs. Until I did I was pretty much limited to Growisofs at the CLI. Out of the distro K3b comes with "Show Advanced Gui elements" deselected, and without that it does not seem possible to select growisofs as the writing app for DVDs. While cdrecord will successfully burn single layer DVDs it will not burn DL DVDs. My "wish", therefore is that the Great Folks on the K3b team please make "Show Advanced Gui Elements" the default config., OR make K3b default to growisofs for DVDs. Enough bug reports have been filed on this subject so I'm not going to do anything other than add this comment as my wish for K3b, and the unsuspecting users who have and will continue to burn lots of coasters before learning about this. Thanks for listening Did you try to use recent original software from ftp.berlios.de/pub/cdrecord/alpha/ instead of this intentionally byggy wodim that is known for not supporting DVDs or BDs.? Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Please however be careful: Some unfriendly Linux distros still ship the dead fork called "cdrkit" that results in a source state from May 2004. So you should warn your users in case that old software has been installed. Make sure to use a PATH that finds /opt/schily/bin/mkisofs before /usr/bin/mkisofs and inform your users that recent software is at this location: Bi-weekly snapshots (recommended): http://sourceforge.net/projects/schilytools/files/ Less frequent regular release: http://sourceforge.net/projects/cdrtools/files/alpha So called "stable" release: http://sourceforge.net/projects/cdrtools/files/ Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |