Can't burn CD's using any tool

[Jaka]

Binary package hint: cdrecord

I have this Dell Studio 1555 and Ubuntu 9.10 installed. I can't burn a CD from here and neither from Windows virtual machine.
The output from the terminal:

jaka@LaptopJaka:~/Desktop$ sudo cdrecord -v speed=16 dev='/dev/scd0' VinsekISOMaster.iso
wodim: No write mode specified.
wodim: Asuming -tao mode.
wodim: Future versions of wodim may have different drive dependent defaults.
TOC Type: 1 = CD-ROM
scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Wodim version: 1.1.9
SCSI buffer size: 64512
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)
Profile: 0x000A (CD-RW)
Profile: 0x0008 (CD-ROM) (current)
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
Beginning DMA speed test. Set CDR_NODMATEST environment variable if device
communication breaks or freezes immediately after that.
Drive DMA Speed: 14272 kB/s 81x CD 10x DVD
FIFO size : 12582912 = 12288 KB
Track 01: data 685 MB
Total size: 787 MB (78:00.00) = 351000 sectors
Lout start: 787 MB (78:02/00) = 351000 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: -11607 (97:27/18)
  ATIP start of lead out: 359849 (79:59/74)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 18
Manufacturer: Plasmon Data systems Ltd.
Blocks total: 359849 Blocks current: 359849 Blocks remaining: 8849
Speed set to 2822 KB/s
Starting to write CD/DVD at speed 16.0 in real TAO mode for single session.
Last chance to quit, starting real write in 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: 1 of 685 MB written (fifo 100%) [buf 99%] 0.5x.Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 00 02 0F 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0A 2A 30 02 80 21 02 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x21 Qual 0x02 (invalid address for write) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 40s

write track data: error after 1079296 bytes
wodim: The current problem looks like a buffer underrun.
wodim: It looks like 'driveropts=burnfree' does not work for this drive.
wodim: Please report.
wodim: Make sure that you are root, enable DMA and check your HW/OS set up.
Writing time: 23.015s
Average write speed 203.8x.
Min drive buffer fill was 99%
Fixating...
Fixating time: 27.450s
wodim: fifo had 208 puts and 18 gets.
wodim: fifo was 0 times empty and 7 times full, min fill was 97%.
jaka@LaptopJaka:~/Desktop$

[Schily (schilling-fokus)]

You are not using cdrecord but a buggy and illegal form from a very outdated
version of cdrecord.

I recommend you to get a recent version of the original software from:

ftp://ftp.berlios.de/pub/cdrecord/alpha/

http://cdrecord.berlios.de/

Make sure to install cdrecord, readcd, cdda2wav suid root.

If this is not sufficient, kill hald as it is known for interrupting the write process.

[Jaka (jaka-luthar)]

I think I successfully installed "cdrtools-2.01.01" using just the 'make' command. Burning still doesn't work. This is the log from Brasero: http://pastebin.com/GXgYJhrF
and the output from the terminal: http://pastebin.com/bB4Y85xa

"If this is not sufficient, kill hald as it is known for interrupting the write process." ... can you tell me how to do this in newbie language please ... :)

[Schily (schilling-fokus)]

You did still not use cdrecord but the fork wodim.

You may need to remove the wodim binary and to manually create a
link to the original software.

See http://cdrecord.berlios.de/private/linux-dist.html for information
on how to identify the original software.

[Jaka (jaka-luthar)]

I removed wodim from synaptic. Than I created links for cdrecord, readcd and cdda2wav in the /opt/schily/bin directory. I pasted links into /usr/bin folder. I think the output is the same:

jaka@LaptopJaka:~$ sudo cdrecord -v speed=16 dev='/dev/scd0' Desktop/VinsekISOMaster.iso
cdrecord: No write mode specified.
cdrecord: Assuming -sao mode.
cdrecord: If your drive does not accept -sao, try -tao.
cdrecord: Future versions of cdrecord may have different drive dependent defaults.
Cdrecord-ProDVD-ProBD-Clone 2.01.01a77 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2010 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: '/dev/scd0'
devname: '/dev/scd0'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.9'.
SCSI buffer size: 64512
atapi: 1
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'HL-DT-ST'
Identifikation : 'DVD+-RW GA11N '
Revision : 'A101'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: DVD-RAM
Profile: DVD-R sequential recording
Profile: DVD-R/DL sequential recording
Profile: DVD-RW sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD+RW
Profile: DVD+R
Profile: DVD+R/DL
Profile: DVD-ROM
Profile: CD-R (current)
Profile: CD-RW
Profile: CD-ROM (current)
Profile: 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 pbuf size: 1966080 = 1920 KB
cdrecord: Warning: DMA resid 0 for 'read buffer', actual data is too short.
cdrecord: Warning: The DMA speed test has been skipped.
FIFO size : 4194304 = 4096 KB
Track 01: data 685 MB
Total size: 787 MB (77:59.97) = 350998 sectors
Lout start: 787 MB (78:01/73) = 350998 sectors
Current Secsize: 2048
ATIP info from disk:
  Indicated writing power: 5
Disk Is not unrestricted
Disk Is not erasable
  Disk sub type: Medium Type A, high Beta category (A+) (3)
  ATIP start of lead in: -11634 (97:26/66)
  ATIP start of lead out: 359846 (79:59/71)
Disk type: Short strategy type (Phthalocyanine or similar)
Manuf. index: 3
Manufacturer: CMC Magnetics Corporation

    Capacity Blklen/Sparesz. Format-type Type
           0 2048 0x00 No Media Present or Unknown Capacity
cdrecord: Cannot get next writable address for 'invisible' track.
cdrecord: This means that we are checking recorded media.
cdrecord: This media cannot be written in streaming mode anymore.
cdrecord: If you like to write to 'preformatted' RW media, try to blank the media first.
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 8848
Starting to write CD/DVD/BD at speed 16 in real SAO mode for single session.
Last chance to quit, starting real write 0 seconds. Operation starts.
Waiting for reader process to fill input buffer ... input buffer ready.
BURN-Free is OFF.
Performing OPC...
Sending CUE sheet...
cdrecord: CUE sheet not accepted. Retrying with minimum pregapsize = 1.
cdrecord: Input...

[Schily (schilling-fokus)]

OK, you did now call cdrecord.

Please call:

ps -efc | grep hald

and later call

kill -STOP PID

where PID is the pid you see from the ps command.

Then try to write again.

After you did write, you may call kill -CONT PID

[Jaka (jaka-luthar)]

So which number is pid?

jaka@LaptopJaka:~$ ps -efc | grep hald
107 979 1 TS 19 19:01 ? 00:00:00 hald --daemon=yes
root 1086 979 TS 19 19:01 ? 00:00:00 hald-runner
root 1180 1086 TS 19 19:01 ? 00:00:00 /usr/lib/hal/hald-addon-rfkill-killswitch
root 1184 1086 TS 19 19:01 ? 00:00:00 /usr/lib/hal/hald-addon-leds
root 1245 1086 TS 19 19:01 ? 00:00:00 hald-addon-input: Listening on /dev/input/event5 /dev/input/event6 /dev/input/event0 /dev/input/event10 /dev/input/event9 /dev/input/event8 /dev/input/event7 /dev/input/event1 /dev/input/event2 /dev/input/event11 /dev/input/event3 /dev/input/event15 /dev/input/event16
root 1247 1086 TS 19 19:01 ? 00:00:00 /usr/lib/hal/hald-addon-cpufreq
107 1250 1086 TS 19 19:01 ? 00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root 1265 1086 TS 19 19:01 ? 00:00:00 hald-addon-storage: polling /dev/sr0 (every 2 sec)
jaka 4391 4371 TS 19 19:05 pts/0 00:00:00 grep --color=auto hald
jaka@LaptopJaka:~$

[Schily (schilling-fokus)]

It is usually the first number.

BTW: if you have something like "pgrep", just call:

kill -STOP `pgrep hald`

[Jaka (jaka-luthar)]

Here's what I did: http://pastebin.com/Dq9Up5SY
I think it destroyed the CD now.

[Schily (schilling-fokus)]

I am not sure whether you killed the right hald process.

Please note that every media that is written to and interrupted by hald
will turn unusable.

If you don't know which hald process to kill, I recommend to just add the option -raw96r
to cdrecord.

[Jaka (jaka-luthar)]

Ok... I think it works now. I successfully burned that iso image using -raw96r option. Now I want to fix this, so I will be able to burn from Brasero or other software.

[Schily (schilling-fokus)]

This verifies that the problem was caused by a bug in hald.

You should open a bug against hald....

[Jaka (jaka-luthar)]

I'm not sure what to do now...

[Schily (schilling-fokus)]

We just verified that your problem is not caused by cdrecord but by hald.

I reassigned this bug to hald.....

[dino99 (9d9)]

http://www.freedesktop.org/wiki/Software/hal/

[Jaka (jaka-luthar)]

Oh this is from a very long time ago... For me this problem was gone when I replaced that Ubuntu installation with newer Ubuntu or whatever. At that time I still didn't know I should close the bug or something...

It's been fun reading through this again btw.. :)