wodim fails to write iso files on DL media

Bug #530141 reported by rennradler on 2010-03-01
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Baltix
Undecided
Unassigned
cdrkit (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: wodim

I am running kubuntu 9.10 64bit on an AMD machine. I thing the bug is in wodim 9:1.1.9-1ubuntu2

I tried to burn a 8GB iso file with k3b (I tried this for the first time). Burning started and after approx. 4.2 GB k3b stopped burning with an error message. I checked the error log and got this:

......
Track 01: 4214 of 8058 MB written (fifo 98%) [buf 75%] 4.9x.
Track 01: 4215 of 8058 MB written (fifo 100%) [buf 60%] 3.5x.
Track 01: 4216 of 8058 MB written (fifo 98%) [buf 79%] 4.9x.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 20 F1 93 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 09 01 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 4421621760 bytes
Writing time: 885.681s
Average write speed 7.3x.
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.000s 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.000s timeout 1000s
Fixating time: 0.010s
/usr/bin/wodim: fifo had 69836 puts and 69646 gets.
/usr/bin/wodim: fifo was 0 times empty and 13796 times full, min fill was 94%.

cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=8 -sao driveropts=burnfree -data -tsize=4125952s -

I retried burning with the cdrecord from berios (cdrtools-2.01.01a77) which I built from the sources. Now it worked like a charme. Therefore I guess wodim has a bug.

Schily (schilling-fokus) wrote :

It is a well known fact that wodim does not support to write DVDs correctly.
With other DVD media types, it may work under some conditions but DVD Dual
layer media does not work at all when using wodim.

This is a result from removing the mature DVD support in the original cdrecord
and replacing this code by something half baken.

It is also a well known fact that wodim was created by some Debian packetizers
as a social attack against the cdrtools project and it is a pitty that Ubuntu supports
this social attack instead of supporting Open Source Software.

In a few weeks, cdrtools-3.0-final will be released and Ubuntu has the chance
to whether Ubuntu is willing to correct a mistake from the past....

salemboot (salemboot) wrote :

This is ridicules, hindering productivity is only going to drive users away. I hope Ubuntu, Canonical gives users the option of choice over using Debian's wodim or the industry standard cdrtools. I, among one other that I know of have put an entry into Ubuntu Brainstorm to recomend including cdrtools. It got deferred to being a question of Packaging. I call shenanigans.

Putting people back into the stone-ages just to protect them from a possible freedom violation is as much a crime as the make-believe crime that would have taken place.

Open your "fracking" eyes Canonical. Many of us are out here recommending your product. But when it screws up consistently because of a known issue, "Debian Obsessiveness" we got problems. I can't always go to some potential users' house and install it for them.

Schily keep up the good work.

My external burner has never worked with wodim.

salemboot (salemboot) wrote :
Download full text (9.8 KiB)

Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1799)
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_set_output_size_for_current_track
BraseroBurnURI stopping
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_session_output_size
BraseroBurnURI output set (IMAGE) image = /tmp/brasero_tmp_G3XAAV.bin toc = none
BraseroBurnURI called brasero_job_get_action
BraseroBurnURI called brasero_job_get_current_track
BraseroBurnURI no burn:// URI found
BraseroBurnURI stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_set_output_size_for_current_track
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_session_output_size
BraseroLocalTrack output set (IMAGE) image = /tmp/brasero_tmp_NAYAAV.bin toc = none
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_flags
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage called brasero_job_get_fd_in
BraseroChecksumImage called brasero_job_set_output_size_for_current_track
BraseroChecksumImage stopping
BraseroChecksumImage called brasero_job_get_current_track
BraseroChecksumImage called brasero_job_get_action
BraseroChecksumImage There is a checksum already 0
BraseroWodim called brasero_job_get_action
BraseroWodim getting varg
BraseroWodim called brasero_job_get_action
BraseroWodim got varg:
BraseroWodim deactivating
BraseroWodim called brasero_job_get_action
BraseroWodim getting varg
BraseroWodim called brasero_job_get_action
BraseroWodim called brasero_job_get_device
BraseroWodim called brasero_job_get_flags
BraseroWodim called brasero_job_get_speed
BraseroWodim called brasero_job_get_flags
BraseroWodim called brasero_job_get_input_type
BraseroWodim called brasero_job_get_fd_in
BraseroWodim called brasero_job_get_current_track
BraseroWodim called brasero_job_set_current_action
BraseroWodim got varg:
 wodim
 -v
 dev=/dev/sr1
 speed=10
 driveropts=burnfree
 fs=16m
 -data
 -nopad
 /media/mybook/LinuxMint-8-x64.iso
BraseroWodim Launching command
BraseroWodim called brasero_job_get_fd_out
BraseroWodim stderr: wodim: No write mode specified.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: wodim: Asuming -tao mode.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: wodim: Future versions of wodim may have different drive dependent defaults.
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.scsidev: '/dev/sr1'
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: devname: '/dev/sr1'
BraseroWodim called brasero_job_get_flags
BraseroWodim stderr: scsibus: -2 target: -2 lun: -2
B...

Joe User (axyz-yahoo) wrote :

This problem still exists with a brand new installation of kubuntu 10.10.

I cannot burn dual-layer DVD's if the data to be burned requires the second DVD layer.

I can build the cdrtools-3.00 as suggested by Schilly, and burn the DVD's just fine with the same data and hardware.

This problem has existed for a long time. Let's fix this by replacing wodim with the latest and greatest cdrecord.

If we're voting, I vote to replace wodim.

Schily (schilling-fokus) wrote :

The problem you see, has a social background and you need to find a way to
deal with the social problems introduced by Debian before your technical problem
will be fixed. Unfortunately even Ubuntu neither seems to care about its users
nor about legality.

The problem has been introduced im May 2004 when a new Debian packetizer
stopped collaborating with upstream after he has become upset because a buggy
patch from him on mkisofs could not be accepted for the official development. This
person later came up with a fairy tale that there was a legal problem in the original
project in order to harm the original project as a revenge for not being able to place
his buggy code.

Meanwhile numerous lawyers confirmed that there is no such legal problem in the
original software and the person who attacked the project of course never was able
to give any prove for his claim.

If you believe you can help with this social problem, you are welcome!

Thanks for the reply.

If the problem is social, and 6 years old, I'll despair of it ever being fixed.

Do you know of any source for a packaged fix for this? If no one else has done it, I will just package cdrecord into a .deb file, and install that. So, I will still be able to use kubuntu packages without worrying about kubuntu changes disabling k3b.

Thanks.

--- On Tue, 11/2/10, Schily <email address hidden> wrote:

> From: Schily <email address hidden>
> Subject: [Bug 530141] Re: wodim fails to write iso files on DL media
> To: <email address hidden>
> Date: Tuesday, November 2, 2010, 4:56 AM
> The problem you see, has a social
> background and you need to find a way to
> deal with the social problems introduced by Debian before
> your technical problem
> will be fixed.  Unfortunately even  Ubuntu
> neither seems to care about its users
> nor about legality.
>
> The problem has been introduced im May 2004 when a new
> Debian packetizer
> stopped collaborating with upstream after he has become
> upset because a buggy
> patch from him on mkisofs could not be accepted for the
> official development. This
> person later came up with a fairy tale that there was a
> legal problem in the original
> project in order to harm the original project as a revenge
> for not being able to place
> his buggy code.
>
> Meanwhile numerous lawyers confirmed that there is no such
> legal problem in the
> original software and the person who attacked the project
> of course never was able
> to give any prove for his claim.
>
> If you believe you can help with this social problem, you
> are welcome!
>
> --
> wodim fails to write  iso files on DL media
> https://bugs.launchpad.net/bugs/530141
> You received this bug notification because you are a direct
> subscriber
> of a duplicate bug (669274).
>

Mantas Kriaučiūnas (mantas) wrote :

It seems, that Jörg Schilling recommends to use cdrecord/cdrtools from ppa:brandonsnider/cdrtools repository, see https://bugs.launchpad.net/ubuntu/+source/cdrtools/+bug/556595/comments/4 :

Schily wrote on 2010-04-07:
> I recommend you to first upgrade to recent original software:
> http://cdrecord.berlios.de/
> https://launchpad.net/~brandonsnider/+archive/cdrtools

I've checked cdrtools_3.00-0ubuntu1~ppa1 from ppa:brandonsnider/cdrtools sources packaging and can confirm, that these packages are original cdrtools-3.00 packages without any patches applied.

Also I copied cdrtools-3.00 from ppa:brandonsnider/cdrtools to main Baltix GNU/Linux repository - ppa:baltix-members/ppa

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers