Enables the recognition of pathspecs which consist of a target address in the ISO filesystem (e.g. /photos) and a source address on hard disk (e.g. /home/user/photos). Both are separated by a = character.

So this example puts the disk directory /home/user/photos, /home/user/mail and /home/user/holidays/photos, respectively in the ISO image as /photos, /mail and /photos/holidays.

Programs mkisofs and xorrisofs accept the same options. For secure backups consider to use xorrisofs with option --for_backup, which records eventual ACLs and stores an MD5 checksum for each data file.

img/ccd を ISO イメージに変換する

オプティカルドライブの名前を確認する

For the remainder of this section the name of your recording device is assumed to be /dev/sr0.

Check this by

$ wodim dev=/dev/sr0 -checkdrive

which should report "Vendor_info" and "Identification" of the drive.

If no drive is found, check whether any /dev/sr* exist and whether they offer read/write permission (wr-) to you or your group.
If no /dev/sr* exists then try

# modprobe sr_mod

CD, DVD, BD から ISO イメージを読み込む

You should determine the size of the ISO filesystem before copying it to hard disk. Most media types deliver more data than was written to them with the most recent burn run.

Use program isosize out of package util-linux to obtain the image size

$ blocks=$(expr $(isosize /dev/sr0) / 2048)

Have a look whether the obtained number of blocks is plausible

$ echo "That would be $(expr $blocks / 512) MB"

That would be 589 MB

Then copy the determined amount of data from medium to hard disk :

$ dd if=/dev/sr0 of=isoimage.iso bs=2048 count=$blocks

Omit count=$blocks if you did not determine the size. You will probably get more data than needed. The resulting file will nevertheless be mountable. It should still fit onto a medium of the same type as the medium from which the image was copied.

If the original medium was bootable, then the copy will be a bootable image. You may use it as pseudo CD for a virtual machine or burn it onto optical media which should then become bootable.

CD-RW や DVD-RW を消去する

Used CD-RW media need to be erased before you can write over the previously recorded data. This is done by

$ wodim -v dev=/dev/sr0 blank=fast

Unformatted DVD-RW media need the same treatment before re-use. But fast blanking deprives them of the capability for multi-session and recording of streams of unpredicted length. So one should apply

$ dvd+rw-format -blank=full /dev/sr0

dvd+rw-format is part of package dvd+rw-tools. Alternative commands are

書き込んだ ISO イメージを確かめる

You can verify the integrity of the burnt medium to make sure it contains no errors. Always eject the medium and reinsert it before verifying. The kernel will learn about the new content only by that reinsertion.

First calculate the md5sum of the original ISO image:

$ md5sum isoimage.iso

e5643e18e05f5646046bb2e4236986d8 isoimage.iso

Next calculate the md5sum of the ISO filesystem on the medium.
Although some media types deliver exactly the same amount of data as have been submitted to the burn program, many others append trailing garbage when being read. So you should restrict reading to the size of the ISO image file.

Both runs should yield the same MD5 sum (here: e5643e18e05f5646046bb2e4236986d8). If they do not, you will propbably also get an i/o error message from the dd run. dmesg might then tell about SCSI errors and block numbers, if you are interested.

ISO 9660 and Burning On-The-Fly

It is not necessary to store an emerging ISO filesystem on hard disk before writing it to optical media. Only very old CD drives at very old computers could suffer misburns due to empty drive buffer.

If you omit option -o from genisoimage then it writes the ISO image to standard output. This can be piped into the standard input of burn programs.

Option -waiti is not really needed here. It prevents wodim from writing to the medium before genisoimage starts its output. This would allow genisoimage to read the medium without disturbing an already started burn run. See next section about multi-session.

On DVD and BD you may letgrowisofs operate genisoimage for you and burn its output on-the-fly

マルチセッション

ISO 9660 multi-session means that a medium with readable filesystem is still writable at its first unused block address, and that a new ISO directory tree gets written to this unused part.
The new tree is accompanied by the content blocks of newly added or overwritten data files. The blocks of data files, which shall stay as in the old ISO tree, will not be written again.

Linux and many other operating systems will mount the directory tree in the last session on the medium. This youngest tree will normally show the files of the older sessions, too.

wodim によるマルチセッション

CD-R and CD-RW stay writable (aka "appendable") if wodim option -multi was used

$ wodim -v -multi dev=/dev/sr0 isoimage.iso

Then the medium can be inquired for the parameters of the next session

$ m=$(wodim dev=/dev/sr0 -msinfo)

By help of these parameters and of the readable medium in the drive you can produce the add-on ISO session

Programs cdrskin and xorrecord do this too with DVD-R, DVD+R, BD-R and unformatted DVD-RW. Program cdrecord does multi-session with at least DVD-R and DVD-RW. They all do with CD-R and CD-RW, of course.

Most re-usable media types do not record a session history that would be recognizable for a mounting kernel. But with ISO 9660 it is possible to achieve the multi-session effect even on those media.

growisofs and xorriso can do this and hide most of the complexity.

growisofs によるマルチセッション

growisofs forwards most of its program arguments to a program that is compatible to mkisofs. See above examples of genisoimage.
It bans option -o and deprecates option -C.
By default it uses the installed program named "mkisofs". You may let it choose one of the others by setting environment variable MKISOFS

$ export MKISOFS="genisoimage"
$ export MKISOFS="xorrisofs"

The wish to begin with a new ISO filesystem on the optical medium is expressed by option -Z

$ growisofs -Z /dev/sr0 -V "ARCHIVE_2013_07_27" -r -J ./for_iso

The wish to append more files as new session to an existing ISO filesystem is expressed by option -M

$ growisofs -M /dev/sr0 -V "ARCHIVE_2013_07_28" -r -J ./more_for_iso

For details see the growisofs manual and the manuals of genisoimage, mkisofs, xorrisofs.

xorriso によるマルチセッション

xorriso learns the wish to begin with a new ISO filesystem from the blank state of the medium. So it is appropriate to blank it if it contains data. The command -blank as_needed applies to all kinds of re-usable media and even to ISO images in data files on hard disk. It does not cause error if applied to a blank write-once medium.

BD Defect Management

BD-RE and formatted BD-R media are normally written with enabled Defect Management. This feature reads the written blocks while they are still stored in the drive buffer. In case of poor read quality the blocks get written again or redirected to the Spare Area where the data get stored in replacement blocks.

This checkreading reduces write speed to at most half of the nominal speed of drive and BD medium. Sometimes it is even worse. Heavy use of the Spare Area causes long delays during read operations. So Defect Management is not always desirable.

cdrecord does not format BD-R. It has no means to prevent Defect Management on BD-RE media, though.

growisofs formats BD-R by default. This can be prevented by option -use-the-force-luke=spare:none. It has no means to prevent Defect Management on BD-RE media, though.

Some software only likes CUE/BIN pair, you can make a CUE sheet with toc2cue (part of cdrdao):

$ toc2cue IMAGE.toc IMAGE.cue

Burn backend problems

If you experience problems, you may ask for advise at mailing list cdwrite@other.debian.org . Or ask for advise at the support mail addresses if some are listed near the end of the program's man page.

Tell the command lines you tried, the medium type (e.g. CD-R, DVD+RW, ...), and the symptoms of failure (program messages, disappointed user expectation, ...).
You will possibly get asked to obtain the newest release or development version of the affected program and to make test runs. But the answer might as well be, that your drive dislikes the particular medium.

dvdbackup — Tool for pure data extraction which does not transcode. It is useful for creating exact copies of encrypted DVDs in conjunction with libdvdcss or for decrypting video for other utilities unable to read encrypted DVDs.

FFmpeg — Complete and free Internet live audio and video broadcasting solution for Linux/Unix, capable to do a direct rip in any format (audio/video) from a DVD-Video ISO image, just select the input as the ISO image and proceed with the desired options. It also allows to downmixing, shrinking, spliting, selecting streams among other features.

Hybrid — Multi platform Qt based frontend for a bunch of other tools which can convert nearly every input to x264/Xvid/VP8 + ac3/ogg/mp3/aac/flac inside an mp4/m2ts/mkv/webm/mov/avi container, a Blu-ray or an AVCHD structure.

MEncoder — Free command line video decoding, encoding and filtering tool released under the GNU General Public License. It is a close sibling to MPlayer and can convert all the formats that MPlayer understands into a variety of compressed and uncompressed formats using different codecs. Wrapper programs like h264encAUR and undvdAUR can provide an assistive interface. Many front-ends are available.

Ripping a DVD is often a simple matter of selecting the preferred codec(s), selecting the desired titles, then clicking the "Rip" button.

トラブルシューティング

K3b locale エラー

When running K3B, if the following message appears:

System locale charset is ANSI_X3.4-1968
Your system's locale charset (i.e. the charset used to encode file names) is
set to ANSI_X3.4-1968. It is highly unlikely that this has been done intentionally.
Most likely the locale is not set at all. An invalid setting will result in
problems when creating data projects.Solution: To properly set the locale
charset make sure the LC_* environment variables are set. Normally the distribution
setup tools take care of this.

Brasero fails to find blank discs

Brasero uses gvfs to manage CD/DVD burning devices. Also make sure that your session is not broken.

Brasero fails to normalize audio CD

If you try to burn it may stop at the first step called Normalization.

As a workaround you can disable the normalization plugin using the Edit > Plugins menu

VLC: Error "... could not open the disc /dev/dvd"

If you get the error, "vlc dvdread could not open the disc "/dev/dvd"" it may be because there is no device node /dev/dvd on your system. Udev no longer creates /dev/dvd and instead uses /dev/sr0. To fix this edit the VLC configuration file (~/.config/vlc/vlcrc):

Playback does not work with new computer (new DVD-Drive)

If playback does not work and you have a new computer (new DVD-Drive) the reason might be that the region code is not set. You can read and set the region code with regionsetAUR from the AUR.

None of the above programs are able to rip/encode a DVD to my hard disk!

Make sure the region of your DVD-reader is set correctly, otherwise you will get loads of unexplainable CSS-related errors. Use regionsetAUR to do so.

GUI program log indicates problems with backend program

If you use a GUI program and experience problems which the program's log blames on some backend program, then try to reproduce the problem by the logged backend program arguments.
Whether you succeed with reproducing or not, you may report the logged lines and your own findings to the places mentioned in section Burn Backend Problems.

Special case: medium error / write error

Here are some typical messages about the drive disliking the medium. This can only be solved by using a different drive or a different medium. A different program will hardly help.