Ubuntu

Can't burn a CD

Asked by Jack Jowett

Burning a CD:
Prior to my installation of Ubuntu 7.04 (Feisty Fawn ) a month ago, devices worked with Windows (don't want to use) and Fedora 6 (problems).
 When I try to burn a CD with C/D / DVD creator, the following messages appeared:
(1) Reload a rewritable or blank disk (it can read size of file) and (2) says writing files to disk.
When I right click on CD-RW/DVD RW Drive:
 This message appears: Cannot mount volume. Invalid mount option when attempting to mount the volume 'UDF Volume'.
Also, when I try to mount the floppy, this message appears; cannot mount volume. mount: /dev/fdo is not a valid block device.

Cd-RW/DVD RW Drive Properties
Volume:
 Label: Volume
 Size: 644.0 KB
 Media: CD-R Disc
 UUID:
 File System: udf
 Mount point: not mounted
 File system: not mounted
 Mount options: not mounted

jack@jack-desktop:~$ /usr/lib/nautilus-cd-burner/list_cddrives
Drive:
  name: DVD+-RW TS-H653A
  device: /dev/scd0
  door: closed
  type: CD-R, CD-RW, DVD-R, DVD-RW, DVD+R, DVD+R DL, DVD+RW, CD, DVD
  is mounted: FALSE
  max read speed: 8468 KiB/s (CD 56.4x, DVD 6.2x)
  max write speed: 8468 KiB/s (CD 56.4x, DVD 6.2x)
  write speeds: 8468 KiB/s (CD 56.4x, DVD 6.2x)
                        7056 KiB/s (CD 47.0x, DVD 5.2x)
                        5645 KiB/s (CD 37.6x, DVD 4.1x)
                        4234 KiB/s (CD 28.2x, DVD 3.1x)
                        2823 KiB/s (CD 18.8x, DVD 2.0x)
                        1412 KiB/s (CD 9.4x, DVD 1.0x)

Media:
  label: 'UDF Volume'
  type: CD-R (has-data)
  is writable: FALSE
  is appendable: TRUE
  capacity: 701.00 MiB approx. or 80 mins 0 secs
  size: 0.63 MiB approx. or 0 mins 0 secs

jack@jack-desktop:~$ uname -a
Linux jack-desktop 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

jack@jack-desktop:~$ mount
/dev/sdb1 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.20-16-generic/volatile type tmpfs (rw)
/dev/sda2 on /media/windows type fuseblk (rw,nosuid,nodev,noatime,allow_other,blksize=4096)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

End of DMESG

[ 47.544000] Unable to identify CD-ROM format.
[22866.180000] Unable to identify CD-ROM format.
[23156.092000] Unable to identify CD-ROM format.
[23253.824000] end_request: I/O error, dev fd0, sector 0
[23253.848000] end_request: I/O error, dev fd0, sector 0
[23257.664000] end_request: I/O error, dev fd0, sector 0
[23257.688000] end_request: I/O error, dev fd0, sector 0
[23267.016000] end_request: I/O error, dev fd0, sector 0
[23267.040000] end_request: I/O error, dev fd0, sector 0
[23327.592000] Unable to identify CD-ROM format.
[24460.608000] Unable to identify CD-ROM format.
[24666.344000] Unable to identify CD-ROM format.
[24666.344000] Unable to identify CD-ROM format.
[30979.064000] Unable to identify CD-ROM format.

Your help would be greatly appreciated.

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Cesare Tirabassi (norsetto) said : 		#1

I don't think that udf is supported by any graphical frontend (hope somebody proves me wrong).
If that is true you should install the udftools package and use the CLI.

Revision history for this message
Jack Jowett (jjjiom) said : 		#2

More Information

I don't know if this problem has anything to do with NTFS-3g but ls /media shows: cdrom, cdrom0, floppy, floppy0 and windows.
cdrom & floppy are shown in light green and the other three in purple.
cdrom0 is empty and cdrom & floppy do not show up on the disk user analysis.
I removed cdrom & floppy but can't remove windows even though it is empty (unmounted windows).

# /etc/fstab: static file system information.
# -- This file has been automaticly generated by ntfs-config --
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sdb1 :
UUID=b528580b-d06d-456e-bde6-487db2aab9d4 / ext3 defaults,errors=remount-ro 0 1
# Entry for /dev/sdb5 :
UUID=331cb40a-87e0-4450-85be-2b93b2b00897 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
/dev/sda2 /media/windows ntfs umask=222,utf8 0 0

Error Report from K3b

System
-----------------------
K3b Version: 1.0

KDE Version: 3.5.6
QT Version: 3.3.7
Kernel: 2.6.20-16-generic
Devices
-----------------------
TSSTcorp DVD+-RW TS-H653A D300 (/dev/scd0, ) [CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD+R, DVD+RW, DVD+R DL] [DVD-ROM, DVD-R Sequential, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite]

K3bIsoImager
-----------------------
mkisofs print size result: 0 (0 bytes)

Used versions
-----------------------
mkisofs: 1.1.2

mkisofs
-----------------------
/usr/bin/genisoimage:
Unable to find previous session PVD '/dev/scd0'.
/usr/bin/genisoimage: Unable to find previous session PVD '/dev/scd0'.

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -cdrecord-params 0,11722 -prev-session /dev/scd0 -gui -graft-points -print-size -quiet -volid CONVERSION -volset -appid K3B THE CD KREATOR (C) 1998-2006 SEBASTIAN TRUEG AND THE K3B TEAM -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-jack/k3bTdLI7a.tmp -rational-rock -hide-list /tmp/kde-jack/k3bVDjzFa.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-jack/k3bPhaPFb.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 2 -path-list /tmp/kde-jack/k3bmwzDRb.tmp

msinfo

Revision history for this message
Jack Jowett (jjjiom) said : 		#3

See Above

Revision history for this message
Jack Jowett (jjjiom) said : 		#4

I don't think that udf is supported by any graphical frontend (hope somebody proves me wrong).
If that is true you should install the udftools package and use the CLI.

Being new to this game, I need a more direction.

Thank you for your reply.

Revision history for this message
Cesare Tirabassi (norsetto) said : 		#5

In a terminal:

sudo apt-get install udftools

This package contains a number of user-space tools related to creating filesystems in the UDF (Universal Disk Format), which is primarily used for DVDs, but sometimes also CD-ROMs:

mkudffs - Format a device, creating an empty UDF filesystem
cdrwtool - Low-level drive management (e.g. set writing speed, format)
pktsetup - Set up a packet writing device (/dev/pktcdvd0) for a drive
wrudf - Maintains a UDF filesystem

This link here provides some detailed information on the subject:

http://www.g-loaded.eu/2005/11/10/packet-writing-on-cdrw-and-dvdrw-media/

You can also refer to the relative man pages.

If you simply want to burn a CD, I think it would be easier for you to use a normal (iso9660) CD.

Revision history for this message
Jack Jowett (jjjiom) said : 		#6

Cesare
Thank you for the comments.
I looked at these comments and will try to implement them.
If you have the time could you look a bug report #94119 and will your suggestions correct these problems.

Revision history for this message
Cesare Tirabassi (norsetto) said : 		#7

Let me understand better, are you using an udf formatted CD/DVD or not?
This:

Media:
   label: 'UDF Volume'
   type: CD-R (has-data)
   is writable: FALSE
   is appendable: TRUE
   capacity: 701.00 MiB approx. or 80 mins 0 secs
   size: 0.63 MiB approx. or 0 mins 0 secs

Is telling me that you probably are. If you are not, than there is a bug (probably in the kernel).
As of today and to my knowledge k3b is not able to burn UDF disks.

Revision history for this message
Launchpad Janitor (janitor) said : 		#8

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.