Troubleshooting CD Burning

CdDvdBurning - Community Ubuntu Documentation https://help.ubuntu.com/community/CdDvdBurning?high...

1 of 4 02/19/2008 11:25 AM

Contents

Burning CDs,

DVDs, and

Blu-Ray discs

Burning

Files to a

CD or DVD

1.

Burning ISO

images

2.

Copying

Discs and

Other

Advanced

Operations

3.

Blu-Ray

Burning

4.

Burning a

CD or DVD

using

Command

Line tools

5.

1.

CdDvdBurning

Burning CDs, DVDs, and Blu-Ray discs

There are several ways to burn CDs and DVDs. In

this tutorial, we will cover the default burning

software provided with Ubuntu as well as

command line burning. There are also alternative

burning programs that you may want to consider

such as xcdroast or k3b.

Burning Files to a CD or DVD

Insert a blank CD or DVD into your drive 1.

Wait for the pop-up and choose Data or Music

CD (older versions of Ubuntu may also offer

a Photo CD option. This is the same as a

Data CD)

To burn a Music CD, see

AudioCDCreation

To burn a Data CD, drag the data over

to the window and click Burn

2.

Burning ISO images

Right click a .iso file and select Open with CD/DVD Creator

Copying Discs and Other Advanced Operations

You can copy CDs and DVDs, as well and blank rewritable emdia and other

operations, using GnomeBaker, a traditional dedicated CD burning

program.

Install the gnomebaker package


2 of 4 02/19/2008 11:25 AM

Click Applications -> Sound and Video -> CD/DVD Writer

GnomeBaker

Create a new project when prompted.

Click Help -> Contents if further help is needed.

Blu-Ray Burning

There are currently no graphical tools that support Blu-Ray disc burning.

See (see Burning a DVD or Blu-Ray Disc below) for command line

instructions. Blu-Ray support is expected in Open Source graphical tools

soon, and NeroLinux3 (a proprietary burning tool) will also include HD DVD

and Blu-Ray disc support.

Burning a CD or DVD using Command Line tools

This section details the use of the command line(terminal) to burn either a

CD or DVD disk.

Creating an ISO image

A command called mkisofs can make an .ISO image to be burned or

mounted.

mkisofs -r -J -o cd_image.iso /directory

The -r and -J ensures long file names work for Unix (using Rock Ridge) and

Windows (using Joliet extensions) respectively.

Checking CD Images Before Burning

It's possible to check CD images before burning. The easiest way is to

simply double-click on it from the file browser, which will load the image

into Archive Manage (file-roller).

If you have sudo access, you can also mount the image, and explore

its contents

sudo modprobe loop

sudo mount -t iso9660 -o ro,loop=/dev/loop0 cd_image.iso

/media/cdrom


3 of 4 02/19/2008 11:25 AM

Remember to unmount an image after checking:

sudo umount /media/cdrom

Burning a CD on the Command Line with cdrecord

cdrecord can burn an ISO(.iso) disk image or other data onto a CD. To

burn a data CD (using image prepared earlier):

cdrecord dev=/dev/cdrom driveropts=burnfree -v -data cd_image.iso

To burn an audio cd from wav files:

cdrecord dev=/dev/cdrom driveropts=burnfree -v -audio [wav files...]

Replace /dev/cdrom as needed if this is not your CD-Writer

-v (verbose) lets you track the recording progress

driveropts=burnfree helps reduce the risk of a buffer under-run

(most drives should support this)

Blanking a CD/RW

To reuse a rewritable CD or DVD you first need to 'blank' the disk. This

erases the old data and prepares the disk for new data.

cdrecord -vv dev=1,0 blank=all

see http://lists.debian.org/cdwrite/2004/10/msg00031.html

Using cdrecord on "unsupported" drives

Sometimes Ubuntu fails to detect and configure your Burner. This results in

"no media found" if you use 'cdrecord dev=/dev/cdrom'. Even 'cdrecord

-scanbus' does not work - so you just don't know, how to address the drive.

You can work around this by looking into the boot messages with dmesg,

to identify the devicepath to your burner. F.e.

$ dmesg

hda: PIONEER DVD RW DVR-108, ATAPI CD/DVD-ROM drive


4 of 4 02/19/2008 11:25 AM

hdb: IDE DVD-ROM 16X, ATAPI CD/DVD-ROM drive

[...]

hda: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache

Ok so we know, it is hda. Now you can burn on this drive using:

cdrecord dev=ATAPI:/dev/hda -data -v -eject your_data.iso

Burning a DVD or Blu-Ray Disc

Install the dvd+rw-tools package. See [InstallingSoftware].

Use the packages growisofs application to burn a DVD or Blu-Ray

disc.

growisofs -Z /dev/scd0 -R -J /some/files

growisofs -speed=2 -dvd-compat -Z /dev/dvd=dvd_image.iso

Add additional sessions by using

growisofs -M /dev/dvdwriter additionaldata

Blanking DVD+RW discs

dvd+rw-format -blank /dev/cdrw

last edited 2007-12-05 07:46:20 by pradeep

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �

� � � � ! � � " � ! ! # � ! $ � � % � � �

� � � � � � � � � � � � � � � � � � � � � � � � � � � �� & ' ( & )

� � � � � � � � � � � � � �

� � & � & � * � & � � * � + � � � � � * � , � � - � & * & � � , � � � � � � . / � � � � & , � � 0 � � , & � � � � � � � � � �- � � * � � � � � � & � � � � � � � � � * � � � � � � � � � � � � � � � � � � � 1 � � � � � � � � 2 � + � � � * ' & � � 3 � 4 � 4 � * 5 5 0 � � & ' � - & � + � � � � � 4 � � & � � � , � � 0 � � + � 6 � & � � , � � � � . � . � 0 � 4 � � & � 2 � 4 � � � � � & � � 3 & � � & � 2 � � , & � 5 5 0& � � � * � � � 7 3 & � � & � � � � � � & � � � & � , - , � 8 � � . , � � � 3 & � � & � � � % 2 � + � � - * � � � , & � . � . � 0 � � � � & - � + 2 �4 � � � � 5 5 0 � & � � � * � � 2 � � + � � � & � & � � � � � � � � � � � � � � � & � � & ' � - & � , � & - � � � - * � � � � 9 & 6 , �* , , � � & 2 � � * � + � � � . � . � 0 � - � 4 � � & � � � , � � � � & � , & - � � � 0 � : � � � , � * , � * � � * , & � � � � � � , 2 � � � 4 � � �� * ' & � � � � � � � � � � � & ' � - & � � � � & � � � � � � , � � - � � & � 3 & � � & � � � * � + � � 4 * � � � � & * � � � * , � * � 5 5 0� & ' � - & 2 � * � � � � & � � � � 4 � � � � � � � & � � � � � � � � � � � � � �

� � � � � � � � � � � � � � � � � � � � � � � � �

. � , 2 � � � � + � � � 3 & � � & � � � & , � 6 � * � � * � - * � � + � � * � � � � & � , - , � � � � � � & 2 � * � � � � � � � � � � � � � � � � � �� + � � � � � � � � � � � 7 � � & ; � � ' * � & � 8 � � � � & � � � � - & � + � � � * ' & � � � � � � 4 � � & � � � & - � � � < & � � * , � *5 5 0 � � & ' � - & 2 � � � � � � � � � � � � � � � � � ! � � � � � � � � � � � 4 � * 6 , � � & � = � & ' = � � * � * � & & � � - � � & - � � � � � � � � + � , + , & � 2 � � & � � � � � � 3 , � � � 3 & � � & � � � � 4 � � � �

� � � � � � � � � � � � �� ! " # � � � � $ � % � & ' � � � � � ' � � " � � ( � ) � � � � � � * � +� � � � � � � � � � � � � � � � � , % � � � � - * � . � � � � / � 0 � � � � � � � 1 � � � � � ( � ) � � � � � � - * � ( �

5 2 � � & � � � � � � � � - � � * � � � � � � & � 4 � � � � - � * � � � � � " # $ % $ % & � � , � & - � � + � � & � � & ' � - & � � � & � & � � , � & � - � � � & & � - � � * � � � � � � + � , + , & � � �

� � � � � � � � � � � � � � � � � � � � � � � � � 2 � � � � � � � � � � & � � � � � � � � � � � 3 � 4 � �

. � � 2 � 4 � � � 3 & � � & � � � % �

� � � � � � � � � � � � � � � � � # 5 # % � � � � � � � � � � 2 � � � � � � � � � � & � � � � � � � � � � � 3 � 4 � �

' � � (

�

� � & � � � * � � * � � � � & � � � , � � & - - & , , * � + 2 � � & - * � , & � * � � � * � � � � � * - 3 , � � � � & � � � � � , � � &* � > � , & � � � � � � & � � � � & � � � * * � � & � � � 2 � 4 � � - � � � , � � � * � 4 * + , � � & � - * , & � 4 � � � � � � � � � � & , �

. � � & � � 4 * + 2 � 4 � � � � � & � � - � ' & � � � . / � � � � & , � 4 � � � � � � � � � � � ? � � � � * � � & � � & ��

� 6 � � � � 4 � � � � � � � � �

Ubuntu Forums - View Single Post - what is wrong with ... http://ubuntuforums.org/showpost.php?p=665753&post...

1 of 1 02/19/2008 09:24 PM

Thread: what is wrong with ubuntu and cdrecord?

#2 January 17th, 2006

View Single Post

mpvano

Gee! These Aren't Roasted!

Join Date: Oct 2005Beans: 200Thanks: 0 Thanked 0 Times in 0 Posts

Re: what is wrong with ubuntu and cdrecord?

The problem is not so much with ubuntu as it is with cdrecord. It's author is, as you can see, extremely hostile to the idea of modifying it to work with the changes made in going to kernel 2.6 - the current linux kernels.

Despite the messages he's built in to it, and the other tools he built. It seems to work fine. The problem is that to install it, the ubuntu team had to make a modification he apparently does NOT approve of - hence the nasty messages.

If the following command doesn't work directly with your drive:

cdrecord -checkdrive

(which should report information about your drive) try this one:

cdrecord dev=/dev/hdc -checkdrive

(or substitute for /dev/hdc, the actual device name of your drive).

If this works but the first command didn't you need to configure the file /etc/default/cdrecord properly. (or just always include dev=/dev/hdc in all your cdrecord commands).

If this doesn't work, make sure you are part of the "cdrom" group using the "Users and Groups" tool in the system menu. You must be part of this group (or use the sudo command) to burn cds. In some cases, you ALWAYS need to use the sudo command to burn certain types of CDs, however. Try it if you can't get anything else to work.

If none of these is your problem, your drive may not be installed correctly, or may not be supported for some reason. If your drive is not an ide or atapi drive, there could be problems with the USB, firewire, or scsi interface or drivers for it.

Try reading all the documentation in /usr/share/doc/cdrecord/README.ATAPI.setup.ubuntu (which contains the aboveinformation and more).

Despite the scary message cdrecord generally works just fine - ignore it! The author (who we all owe a lot to for doing much of the groundwork that allows cd burning on linux and other platforms today) is just "venting". Many of the issues he's complaining about are valid, but don't need to stop you from using the software....

hope this helps,

Mario__________________

Last edited by mpvano : January 17th, 2006 at 10:23 PM.

Cdrtools - why do Linux distributions create bad forks? http://cdrecord.berlios.de/private/linux-dist.html

1 of 5 02/19/2008 09:29 PM

FAQ Download latest Download recent Download old/stable Linux Packages

Linux controversy

In autumn 2005 and early spring 2006, a group of Debian maintainers started toattack the cdrtools project.

The attacks have been based on the fact that cdrtools was licensed under the GPL.As a result, on May 15th 2006 most projects from the cdrtools project bundle havebeen relicensed under CDDL (giving more freedom to users than the GPL does). Atthe same time, an important amount of additional code (DVD support code from JörgSchilling and a Reed Solomon decoder from Heiko Eißfeldt) has been added to thefreely published sources.

In summer 2006, the attacks from the group of Debian maintainers escalated and inSeptember 2006, these people created something they call a fork from cdrtools.They soon added a lot of bugs and this way turned the "fork" into a questionableexperiment. The last work on this "fork" has been done eight months later on May6th 2007, then the leader of the attacks stopped his efforts.

Although there is no "project" activity on the "fork" anymore since more than 9months (which is more than the speudo activity period), there are still people whospread incorrect claims on both the original project and the fork. Please help thefree original project by correcting these incorrect claims.

Strange license claims from some Debian maintainers

This is what the group of Debian maintainers used to attack the cdrtools project:

They claimed that the GPL requires the build system (used to compile GPL software)to be included and to be published under GPL if binaries from the compiled GPLsources are published.

They then took old cdrtools sources and replaced the original build system bysomething that is not under GPL (nor under a GPL compatible license) either. Theyeven omit parts of the build system they use (although GPL �3 is very explicit aboutthis).

Now you only need to become crazy to understand why they believe the Debian forkis "free" but the original cdrtools is not.

Many Linux distributions now come with broken variants of cdrtools

If you are on Debian, RedHat, SuSE and some other Linux distributions, you need totake extreme care as these distributions recently started to replace cdrtools by afork that is based on an outdated version of cdrtools. This fork did not fix bugs butrather introduced new bugs that never have been in the original software.

For other Linux distributions, I suggest to have a look at /usr/bin/cdrecord and checkwhether this is a link to another program or whether there is an original programfile. Also call "cdrecord -version" to check what version you are using. The


2 of 5 02/19/2008 09:29 PM

affected distributions replaced all programs from cdrtools (cdrecord, cdda2wav,readcd, mkisofs, ...) by programs from the fork.

How do I find out whether I am running a recent original version of cdrtools?

Call "cdrecord -version" and check the output. If you see something like:

Cdrecord-ProDVD-ProBD-Clone 2.01.01a32 (i386-pc-linux) Copyright (C)1995-2007 Jörg Schilling

If you are running the original software, also check the other programs to have thesame version number in order to be 100% sure. If you see version numbers below2.01.01a09 (including 2.01), you are running outdated software that needs anupdate if you are running Linux-2.6.8.1 or newer.

Starting with 2.01.01a32, all original programs contain the year 2007 and JörgSchilling in the first line of the -version output. As an Example, "mkisofs-version" outputs:

mkisofs 2.01.01a32 (i386-pc-linux) Copyright (C) 1993-1997 EricYoungdale (C) 1997-2007 Jörg Schilling

If you are not running the original software, get recent original software from the"Download recent" or from the "Download latest" location. Unpack, compile byrunning "make" and install. Make sure that all programs that send (SCSI) commandsto CD/DVD/Blu-Ray drives are installed to be suid root.

If you are running cdrtools frontends like k3b and others and do not like to replacethese programs with original versions, you should remove files like /usr/bin/wodim,/usr/bin/genisoimage, /usr/bin/icedax, /usr/bin/readom and replace them by links tothe original software.

Ask your Linux distributor to include recent originals instead of broken forks

Inform them that if they force you to use the defective fork instead ofallowing you to choose the correctly working original cdrtools, theypublish a non-free Linux distribution.

Tell them that you like to decide yourself which program you choose. Whether it isthe fork or whether it is the original program depends on which package worksbetter.

Some Linux distributions ship both and do not try to patronize their users, others donot give their users the freedom.

The following Linux distributions currently work against the freedom of their users:

Debian Fedora OpenSuse SuSE

If you know of other unfree distributions, please report.

The following Linux distributions currently grant their users the freedom to selectthe better CD/DVD/Blu-Ray writing software:

Gentoo


3 of 5 02/19/2008 09:29 PM

Gentoo cdrecord packet

The Ubuntu burning team is preparing a package for the original cdrtools.

Ubuntu cdrecord+mkisofs+cdd2wav packet Package archive of the ubuntu burning team with attitional hints (e.g. how to modify/etc/apt/sources.list to allow the installation).

What are the problems when running programs from the broken fork?

In all programs of the fork that send SCSI commands, you may be unable to accessany of the CD/DVD/Blu-Ray drives at all if you are on Linux-2.6.8.1 or later. This is dueto a missing workaround for the Linux kernel interface change that happened withLinux-2.6.8.1.

In the cdrecord clone from the fork, messages have been removed that would warnyou in case that you are not running cdrecord as root. As some of the SCSIcommands used by cdrecord need root privileges, cdrecord may fail later withstrange problems because of this hack. Note that cdrecord supports (and needs tosupport) many vendor unique features of drives (e.g. for optimized writing of CDs andDVDs). Linux filters away all vendor specific SCSI commands in case the program thatsends them does not have root privileges. There are other non vendor uniquecommands that are filtered also.

The mature DVD support from the original cdrecord has been ripped off and replacedby something of very poor quality. The replacement code misses key features (like-atip extraction and printout). As a result the DVD code in the fork is not correctlyparameterized.

All recent cdrecord enhancements like better CUE Sheet for CDs support and Blu-Raysupport are missing in the clone.

The mkisofs clone from the fork is the worst of all. The web is full of bug reports forthe clone.

The original mkisofs fixed dozens of bugs from the early days of mkisofs (1993-1997).These bugs are still present in the fork.

The original mkisofs added support for multi-extent files that may be > 4 GB (up to 8TB) while the fork does not support more than 4 GB.

The original mkisofs added find(1) command line support into mkisofs and thus givesa lot new features that are important for people who like to use mkisofs for simplebackups or like to avoid the need to create a copy of the tree that is going to beprocessed by mkisofs. This feature is missing in the fork.

The original mkisofs added support for Rock Ridge Version-1.12 and now supportscorrectly working hard links. This feature is missing in the fork.

The original mkisofs added support for correct link counts on all files and directories.This feature is missing in the fork.

The original mkisofs replaceed the GNU getlongopt based CLI interface by somethingwith much less bugs. The design for the mkisofs options from the early days


4 of 5 02/19/2008 09:29 PM

introduced a lot of similar named long options. The old GNU getlongopt based codedoes not detect typo's in the options but rather finds the option with the longestsubstring that does not have a typo and assigns it a string parameter that containsthe typo.

The original mkisofs added working support for UTF-8 based locales and support foriconv based translations. The clone claims to do the same but disabled key featuresfrom mkisofs with the attempt to support UTF-8 and may create images withincorrect file name lengths without even printing a warning.

The original mkisofs added much better UDF support (such as support for symlinks,userids/groupids and permissions as well as support for MacOS extensions). Thesefeatures are missing in the fork.

The mkisofs clone will create unusable filesystems in some cases when Joliet is used.This is a bug that never existed in the original.

What is the background for the forks?

When the Open Software movement has been started by people like Rich Salz andothers in the late 1970s, it was important for all authors of free software to writesoftware that runs best on all available platforms.

Later, when the Free Software Foundation was created by Richard Stallman in themid 1980s, it was still important to write software that runs best on all availableplatforms. This continued until the late 1990s. Linux did already exist but thesoftware that many people now call "linux software" was mainly developed on Sunsystems until the mid 1990s.

Then around y2000, more and more free software became non-portable because it'smaintainers moved to Linux and did not care about portability anymore.

At the same time, Linux distributions got into trouble because more and more Linuxusers did no longer buy Linux distributions but downloaded them from the network.This caused pressure on the commercial Linux distributors. RedHat and SuSe arewell known commercial Linux distributors, but even Debian needs to be called a"commercial Linux distributor". Key people from Debian are paid for their work onDebian (see here) and for this reason do no longer represent community interestsbut the commercial interests of their investors.

How is this all related to cdrtools?

As commercial Linux distributions are interested in revenue, they need "arguments"they can print on glossy paper...

In order to get these arguments, they are no longer interested in code quality.Instead they are interested in marketing "facts".

If they add UNICODE UTF-8 support to the list of key features of their distribution,they need to be able to tell their users that all available software supports UTF-8. Alot of Open Source software does not support UTF-8 yet and with many of the OSSprograms this problem is not obvious. With other software like mkisofs, theproblem is obvious.

Linux distributors could cooperate with the author and try to help with the


5 of 5 02/19/2008 09:29 PM

implementation of UTF-8 support.....

In fact, this happened around y2004. I received a patch that was intended to addUTF-8 support to mkisofs.

Unfortunately, the code quality of this patch was lousy. It tried to incorrectlyinitialize a structure and it handled only a few obvious cases. Many important issueswith UTF-8 support have been completely ignored. As a result, I rejected this patchbecause I do care about code quality (I still need to be able to maintain the code in afew years). The people in the Linux distribution could have fixed the problems andcreated a useful solution but they did not do this.

Now these people have been in trouble and needed an excuse for their behavior.They created the fairy tale that there is a license problem in cdrtools. They createda network of "cooperation" and supported some people which created a fork ofcdrtools based on the fairy tale.....

This fork created a lot of pseudo actions in the first few months. As (in contrary tothe original cdrtools) it is not based on code quality, this fork did experiment withLinux specific behavior but finally failed to create any new or better interface.

The results are a mess. The cdrecord fork on SuSe-10.2 (running on a well supportedIBM laptop) is completely unable to talk to the built in CD/DVD drive. The unmodifiedoriginal cdrecord is able to talk to the drive, even if the dev= parameter is omitted.The packet maintainer from SuSe still claims that he needs to patch the originalsoftware in order to add support for things that are supposed to be missing in theoriginal software. Well, the original cdrtools meanwhile do support UTF-8correctly....does he like to reduce the code quality to what SuSe users "expect"?

Despite all these interests, the fork died in May 2007.

What are the real interests of the Linux distributors?

Are the Linux distributors still interested in Free and Open Software?

Will Linux distributors reveal that they did make a mistake and go back to the realFROSS model?

I invite all Linux distributors to go back to support real Free and OpenSource Software and to show that they are able to correct a mistake fromthe past.

Last Change 08/02/06

Berlios Homepage Schily's Homepage

Cdrecord

Ubuntu Forums - View Single Post - what is wrong with ... http://ubuntuforums.org/showpost.php?p=676018&post...

1 of 1 02/19/2008 09:25 PM


#8 January 23rd, 2006

View Single Post

Enginerd

Just Give Me the Beans!

Join Date: Aug 2005Beans: 61Ubuntu 7.04 Feisty Fawn UserThanks: 0 Thanked 0 Times in 0 Posts


Open a terminal window (CLI)

~$ sudo adduser yourusername cdrom

that should do it.

You should be able to burn if you use sudo then your record command. If you are using gnomebaker or a graphical use gksudo.

Im a bit of a newb myself so i hope this helps. If not imsure some one more experienced than I will be along to help.

Enginerd__________________

Ubuntu Forums - View Single Post - what is wrong with ... http://ubuntuforums.org/showpost.php?p=1597006&pos...

1 of 1 02/19/2008 09:27 PM


#9 October 9th, 2006

View Single Post

jstaple

First Cup of Ubuntu

Join Date: Oct 2006Beans: 4Thanks: 0 Thanked 0 Times in 0 Posts


Try this...

1. Add yourself (Your user account) to the disk group (System->Administration->Users and Groups)2. Goto System->Preferences->Removable Drives and Media and untick everything in the storage tab3. Try and burn a CD again

You will have to put these ticks back when you want automount to work again.

This worked for me. Don't treat as a difintive answer give it a try and see if it works for you.__________________

Troubleshooting CD Burning

Technology

Transcript of Troubleshooting CD Burning