[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: CD Burning Software



Hi,

davidson wrote:
> https://help.ubuntu.com/community/CdDvd/Burning#Burning_a_CD_or_DVD_using_C
ommand_Line_tools

  "Sometimes Ubuntu fails to detect and configure your Burner. This results
   in "no media found" if you use 'wodim dev=/dev/cdrw'. Even 'wodim -scanbus'
   does not work [...] Ok so we know, it is hda."

Well, /dev/cdrw should be a softlink to some /dev/sr*. Whether you get
it nowadays is a matter of udev.

wodim -scanbus suffers from bitrot because Linux discontinued the /dev/sd*
device files for which -scanbus is looking. (Create a softlink /dev/scd0
from /dev/sr0 and it will appeari in wodim -scanbus output.)
If the Linux kernel is old enough to show /dev/hda, then wodim -scanbus does
not find the device for the reverse reason: wodim is then too young.
(Option dev=ATA: might then help. But i cannot test this any more.)

The article is about 10 years behind.
Our own wiki about command line burning is more up to date.
  https://wiki.debian.org/BurnCd


Hans wrote:
> I believe, k3b and brasero are just GUIs for wodim.

Both prefer growisofs over wodim for DVD and BD media. Brasero in Debian
uses libburn by default for CD, DVD, BD media. (Xfburn uses libburn
unconditionally.)

The big GUIs are not only frontends to burn programs but also to ISO 9660
formatting programs (genisoimage, libisofs, xorriso) and to media stream
converters (e.g. gstreamer). Further they use 50+ libraries which have
nothing to do with burning, filesystem formatting, or stream conversion.

-----------------------------------------------------------------------

Use wodim only with CD media. It might halfways work with DVD but you
are always potential victims to clueless handling of the medium.

With BD-RE it reports:

  ...
  wodim: Drive needs to reload the media to return to proper status.

The drive tray goes out and in. wodim then continues:

  ...
  wodim: Cannot get next writable address for 'invisible' track.
  wodim: This means that we are checking recorded media.
  wodim: This media cannot be written in streaming mode anymore.
  wodim: If you like to write to 'preformatted' RW media, try to blank the media first.

This would be the occasion to bail out in dignity. But it goes on:

  Starting to write CD/DVD at speed  51.0 in real TAO mode for single session.
  ...
  Errno: 5 (Input/output error), read track info scsi sendcmd: no error
  CDB:  52 01 00 00 00 FF 00 00 1C 00
  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

The attempted command is appropriate only for CD and DVD+R.

At that point the drive is really fed up. If it could, then it would
come out of its box and slap the program and its user in the face.

Still wodim does not show any understanding, but rather goes on

  Writing  time:    4.344s
  Average write speed 999.0x.
  Fixating...
  Errno: 5 (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 30 06 00 00
  Sense Key: 0x5 Illegal Request, Segment 0
  Sense Code: 0x30 Qual 0x06 (cannot format medium - incompatible medium) Fru 0x0
 
This time it tried to close a formatted medium.

But in the end, it does one thing right: Its exit value is non-zero.
So it knows that it failed to do the job.


Have a nice day :)

Thomas


Reply to: