dd won't burn iso image

English Install/Boot/Login
1

I downloaded a live cd iso image from factory but can’t get it to burn.

laptop:/downloads # dd if=./openSUSE-KDE-LiveCD-x86_64-Build0416-Media.iso of=/dev/sr0 bs=4K
dd: opening `/dev/sr0': Read-only file system
laptop:/downloads # ls -l /dev/sr0
brw-rw----+ 1 root cdrom 11, 0 2010-01-29 22:38 /dev/sr0

I tried with three blank CDs making sure they were all 700MB first.

Finally copies the image to windoze where it burned fine. This is the first time dd hasn’t worked for me. Made sure the OS was updated but no changes.
uname -a:

tom@laptop:~/Documents> uname -a
Linux laptop 2.6.31.8-0.1-desktop #1 SMP PREEMPT 2009-12-15 23:55:40 +0100 x86_64 x86_64 x86_64 GNU/Linux
2

Wrong tool. dd is not a optical media burner. Linux GUI burner tools include k3b, brasero, and a whole heap of others. Also the command tools behind the GUI tools like wodim, cdrecord, growisofs, etc. also work.

3

dd is not for burning
I think you are confusing it - perhaps you used dd for writing a .iso to a usb flash drive? Like making a bootable usb flash drive.
k3b or gnomebaker or brasero are UI tools

4

on the CLI, for a CD, use :

cdrecord -v dev=/dev/scd0 openSUSE-KDE-LiveCD-x86_64-Build0416-Media.iso

For a dvd, use :

growisofs -dvd-compat -Z /dev/scd0=openSUSE-11.2-DVD-x86_64.iso

Change /dev/scd0 to match your CD/DVD writer device

5

Thanks to all for the responses. The GUIs are not working for me, the old problem of cdrecord can’t open device. I’ve followed the advice in threads on this subject but no luck. I’m in the cdrom group, have the codecs from packman, the device is set to all rw, but it won’t work.

Any suggestions on what to look at next?

6

Either do it as root or add yourself to the group cdrom :

group -A you cdrom

where you = your login name

7

As I said in my previous post, I am in cdrom group. I also tried k3b as root but it came back with the error “cdrecord has no permission to open the device”.

Further, I tried you’re cli command (for cd). No errors were returned while burning but when I try to boot it the screen flashes once with the bootloader message and then reboots. Maybe a bad download. This came from factory repo and doesn’t seem to have a checksum file so couldn’t check. Will try downloading it again to see what happens. Will post again after that.

8

There was a strange bug reported by other users in another thread where if you go into k3b’s configuration settings and change the backend program from /usr/bin/cdrecord to /usr/bin/X11/cdrecord (or the other way, I don’t remember), it would work, even though both programs are identical. Try that.

9

I’ll try that in the morning. I tried again as root with a newly downloaded file which burned partially then had an error

laptop:/downloads # cdrecord -v dev=/dev/scd0 ./openSUSE-KDE-LiveCD-x86_64-Build0416-Media.iso | tee cdrecord-error
TOC Type: 1 = CD-ROM
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'HL-DT-ST'
Identification : 'DVD+-RW GA11N   '
Revision       : 'A101'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
Current: 0x0009 (CD-R)
Profile: 0x0012 (DVD-RAM) 
Profile: 0x0011 (DVD-R sequential recording) 
Profile: 0x0015 (DVD-R/DL sequential recording) 
Profile: 0x0014 (DVD-RW sequential recording) 
Profile: 0x0013 (DVD-RW restricted overwrite) 
Profile: 0x001A (DVD+RW) 
Profile: 0x001B (DVD+R) 
Profile: 0x002B (DVD+R/DL) 
Profile: 0x0010 (DVD-ROM) 
Profile: 0x0009 (CD-R) (current)
Profile: 0x000A (CD-RW) 
Profile: 0x0008 (CD-ROM) 
Profile: 0x0002 (Removable disk) 
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE 
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Drive buf size : 1053696 = 1029 KB
Drive DMA Speed: 14898 kB/s 84x CD 10x DVD
FIFO size      : 4194304 = 4096 KB
Track 01: data   662 MB        
Total size:      760 MB (75:19.28) = 338946 sectors
Lout start:      760 MB (75:21/21) = 338946 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
  Is not unrestricted
  Is not erasable
  Disk sub type: Medium Type B, low Beta category (B-) (4)
  ATIP start of lead in:  -12369 (97:17/06)
  ATIP start of lead out: 359849 (79:59/74)
Disk type:    Short strategy type (Phthalocyanine or similar)
Manuf. index: 69
Manufacturer: Moser Baer India Limited
Manufacturer is guessed because of the orange forum embargo.
The orange forum likes to get money for recent information.
The information for this media may not be correct.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 20903
Starting to write CD/DVD at speed  24.0 in real TAO mode for single session.
Last chance to quit, starting real write in    4 seconds.   3 seconds.   2 seconds.   1 seconds.   0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Starting new track at sector: 0

Track 01:    0 of  662 MB written.
Track 01:    1 of  662 MB written (fifo 100%) [buf  99%]   0.5x.
write track data: error after 1079296 bytes
Writing  time:   20.904s
Average write speed 216.7x.
Min drive buffer fill was 99%
Fixating...
Fixating time:   28.135s
laptop:/downloads #

No appropriate messages within /var/log/*. During three trials, one showed a buffer-underrun error but I failed to save that one:shame:

I’ll get back tommorrow after I try your suggestion.

Thanks

10

Mmm, I wouldn’t try to burn a CD at 24x on CD-Rs made in India. Even with a good brand of media I stick to a slower speed like 10 or 12x. Try it with a lower speed, using the speed= option of cdrecord/wodim.

11

Both versions are same in openSUSE. Also, cdrecord is softlinked to wodium. wodium (the new program) is actually a derivative of the original cdrecord that is still maintained by its author with his own new features such as support for blueray disk etc.

12

Yes, that’s the puzzling thing, as I already said, the binaries are identical, only the path is different. I thought it might be something to do with apparmor, but I haven’t experienced this myself so I can’t make a bug report.

13

I have used Imgburn under Windwos Brasero under GNOme and can’t burn a bootable DVD. However the image itself is OK as I can install 121.4 Mlestone 5 under VMware. I have 11.4 Milestone 4 - should I download the image there and try to use K3b. I’ve made enough platters so I think I’ll burn R/W DVD.

Marty Felker

14

You can set a larger buffer as well and burn with a higher priority:

# nice -n -19 cdrecord -v dev=$MEDIA speed=$SPEED fs=32m driveropts=burnproof -eject $ISOFILE

Fill in the correct values for all variables. The example is from a script I wrote for this HOWTO: How to burn your installation DVD. For a CD 12x speed is about right. For a DVD I use 4x.

15

Just a small comment because the groups have been mentioned here: it is not necessary to be in ‘cdrom’ to be able to burn. Just the opposite even: it should not be recommended, as it touches security issues.

16

On 12/17/2010 07:36 AM, gropiuskalle wrote:
>
> Just a small comment because the groups have been mentioned here: it is
> not necessary to be in ‘cdrom’ to be able to burn. Just the opposite
> even: it should not be recommended, as it touches security issues.

If you run k3b in user mode in 11.4, you need to be in the cdrom group,
otherwise the application does not find the hardware. I guess you get to choose
which security breach you want.

Incidentally, what security issue is there with being in the cdrom group?

17

On 2010-12-17 14:36, vodoo wrote:
>
> You can set a larger buffer as well and burn with a higher priority:

Perhaps with ionice (-c 1).

–
Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)