Re: k3b + wodim fails to burn
On Friday 22 December 2006 16:35, Giacomo Montagner wrote:
> Hi!
> I just upgraded and have these packages installed:
>
> Package: wodim
> Architecture: i386
> Source: cdrkit
> Version: 9:1.1.0-1
>
> Package: k3b
> Architecture: i386
> Version: 0.12.17-5
>
> When I try to burn data-cd using k3b it fails with the following error:
>
> ===========================================================================
>=====
>
> [BLAH BLAH BLAH...]
> Starting to write CD/DVD at speed 10.
> 0 in real SAO 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...
> Sending CUE sheet...
> Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
> CDB: 2A 00 FF FF FF 6A 00 00 1F 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 05 00 00 00 00 10 2A 00 00 90 30 05 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru
> 0x0
> Sense flags: Blk 0 (not valid)
> resid: 63488
> cmd finished after 0.002s timeout 200s
> Writing pregap for track 1 at -150
> write track pad data: error after 0 bytes
> BFree: 1029 K BSize: 1029 K
> Starting new track at sector: 0
> Track 01: 0 of 666 MB written.
> Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
> CDB: 2A 00 00 00 00 00 00 00 1F 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 05 00 00 00 00 10 2A 00 00 90 30 05 00 00
> Sense Key: 0x5 Illegal Request, Segment 0
> Sense Code: 0x30 Qual 0x05 (cannot write medium - incompatible format) Fru
> 0x0
> Sense flags: Blk 0 (not valid)
> resid: 63488
> cmd finished after 0.002s timeout 200s
> /usr/bin/X11/wodim: A write error occured.
> /usr/bin/X11/wodim: Please properly read the error message above.
> write track data: error after 0 bytes
> Writing time: 38.150s
> Average write speed 119.4x.
> Fixating...
> Fixating time: 0.004s
>
> cdrecord command:
> -----------------------
> /usr/bin/X11/wodim -v gracetime=2 dev=1,0,0 speed=10 -dao
> driveropts=burnfree -eject -overburn -data -tsize=341118s -
>
> mkisofs
> -----------------------
> Warning: creating filesystem that does not conform to ISO-9660.
> Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in
> the OS.
> Warning: creating filesystem that does not conform to ISO-9660.
> Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in
> the OS.
> 341118
> Warning: creating filesystem that does not conform to ISO-9660.
> Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in
> the OS.
> I: -input-charset not specified, using utf-8 (detected in locale settings)
> 0.15% done, estimate finish Fri Dec 22 15:27:27 2006
> 0.29% done, estimate finish Fri Dec 22 15:21:53 2006
> 0.44% done, estimate finish Fri Dec 22 15:19:58 2006
> 0.59% done, estimate finish Fri Dec 22 15:19:02 2006
>
> mkisofs command:
> -----------------------
> /usr/bin/X11/mkisofs -gui -graft-points -volid label -volset -appid K3B
> THE CD KREATOR (C) 1998-2005 SEBASTIAN TRUEG AND THE K3B TEAM -publisher
> -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort
> /tmp/kde-username/k3b5OEJwb.tmp -rational-rock -hide-list
> /tmp/kde-username/k3bypiyec.tmp -joliet -joliet-long -hide-joliet-list
> /tmp/kde-username/k3bZrqy7a.tmp -untranslated-filenames
> -max-iso9660-filenames -iso-level 3 -path-list
> /tmp/kde-username/k3bnL9xYb.tmp
>
> ===========================================================================
>=====
>
> What seems strange to me is that I tried creating only the iso image with
> k3b, then burnt the cd using:
>
> dd if=/tmp/k3b_image.iso | cdrecord speed=10 dev=/dev/scd0
> driveropts=BURNFREE -v -
>
> and it worked perfectly... then I discovered (amazingly enough) that
> cdrecord is a symlink to wodim...
>
> Any ideas on what's going wrong?
K3B does not work with wodim and the cdrecord simply symlinks to wodim. Since
mkisofs has also been similarly replaced, expect even more problems. There is
nothing wrong with the iso file and wodim apparently is OK with the command
line options in your "dd" (hey, a cool way of doing this!).
To me, there is no good reason why one cannot have both cdrecord and wodim
(and mkisofs and genisofs) one one's system. The newer upgrades throw away
the older programs which may still be needed by other software.
Reply to: