LinuxQuestions.org - Why k3b is corrupting my CDs in Slackware 10.2?

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Why k3b is corrupting my CDs in Slackware 10.2? (https://www.linuxquestions.org/questions/linux-software-2/why-k3b-is-corrupting-my-cds-in-slackware-10-2-a-458518/)

Why k3b is corrupting my CDs in Slackware 10.2?

Hello friends,
I am having a problem with K3b because, whenever I try to burn a CD using auto mode it shows some messages like the following and finally my CD becomes unusable. It has corrupted 2 Moserbaer 52x CDs and the output I am showing here is for my Moserbaer 4x-12x Re-writable CD (thanks, it can't be corrupted this way)

Code:

Staring SAO writing at 12x speed

Enabled Burnfree

Performing Optimum Power Calibration

Sending CUE sheet

Starting writing

input/output error. Not necessarily serious

A write error occured

Sometimes using TAO mode solves this issue.

However, when I use TAO mode manually, it works fine. I have used k3b many times with no problems on many distributions. This is the first time it has corrupted my CDs. Can you suggest what could be the problem here?

This is the output of the k3b debugging window

Code:

System

-----------------------

K3b Version: 0.12.16



KDE Version: 3.4.2

QT Version:  3.3.4

Kernel:      2.4.31

Devices

-----------------------

HL-DT-ST CD-RW GCE-8526B 1.04 (/dev/hdc, ) at /mnt/cdrom [CD-R; CD-RW; CD-ROM] [CD-ROM; CD-R; CD-RW] [SAO; TAO; RAW; SAO/R96P; SAO/R96R; RAW/R16; RAW/R96P; RAW/R96R]



Used versions

-----------------------

cdrecord: 2.1.1a10



cdrecord

-----------------------

scsidev: 'ATAPI:/dev/hdc'

devname: 'ATAPI:/dev/hdc'

scsibus: -2 target: -2 lun: -2

Warning: Using ATA Packet interface.

Warning: The related Linux kernel interface code seems to be unmaintained.

Warning: There is absolutely NO DMA, operations thus are slow.

SCSI buffer size: 64512

Cdrecord-ProDVD-Clone 2.01.01a10 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling

TOC Type: 1 = CD-ROM

Using libscg version 'schily-0.8'.

Driveropts: 'burnfree'

atapi: 1

Device type    : Removable CD-ROM

Version        : 0

Response Format: 2

Capabilities  : 

Vendor_info    : 'HL-DT-ST'

Identifikation : 'CD-RW GCE-8526B '

Revision      : '1.04'

Device seems to be: Generic mmc CD-RW.

Current: CD-RW

Profile: CD-RW (current)

Profile: CD-R 

Profile: CD-ROM 

Profile: Removable Disk (current)

Using generic SCSI-3/mmc  CD-R/CD-RW driver (mmc_cdr).

Driver flags  : MMC-2 SWABAUDIO BURNFREE 

Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R

Drive buf size : 1951488 = 1905 KB

FIFO size      : 4194304 = 4096 KB

Track 01: data  637 MB        

Total size:      732 MB (72:33.25) = 326494 sectors

Lout start:      732 MB (72:35/19) = 326494 sectors

Current Secsize: 2048

ATIP info from disk:

  Indicated writing power: 6

  Reference speed: 6

  Is not unrestricted

  Is erasable

  Disk sub type: High speed Rewritable (CAV) media (1)

  ATIP start of lead in:  -12374 (97:17/01)

  ATIP start of lead out: 359849 (79:59/74)

  1T speed low:  4 1T speed high: 10

  2T speed low:  0 (reserved val  6) 2T speed high:  0 (reserved val 12)

  power mult factor: 2 6

  recommended erase/write power: 2

  A1 values: 24 2C AC

  A2 values: 6C A4 34

  A3 values: 04 D1 80

Disk type:    Phase change

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: 33355

Starting to write CD/DVD at speed 12 in real SAO mode for single session.

Last chance to quit, starting real write in 3 seconds.

  2 seconds.

  1 seconds.

  0 seconds. Operation starts.

Waiting for reader process to fill input buffer ... input buffer ready.

BURN-Free is ON.

Performing OPC...

Sending CUE sheet...

/usr/bin/cdrecord: WARNING: Drive returns wrong startsec (0) using -150

Writing pregap for track 1 at -150

Starting new track at sector: 0

Track 01:    0 of  637 MB written.

Track 01:    1 of  637 MB written (fifo  95%) [buf  97%]  13.2x.

/usr/bin/cdrecord: Input/output error. write_g1: scsi sendcmd: no error

CDB:  2A 00 00 00 02 0F 00 00 1F 00

status: 0x0 (GOOD STATUS)

cmd finished after 10.054s timeout 200s

/usr/bin/cdrecord: A write error occured.

/usr/bin/cdrecord: Please properly read the error message above.

write track data: error after 1079296 bytes

Writing  time:  19.729s

Average write speed 277.9x.

Fixating...

Fixating time:    0.001s

BURN-Free was never needed.

/usr/bin/cdrecord: fifo had 81 puts and 18 gets.

/usr/bin/cdrecord: fifo was 0 times empty and 2 times full, min fill was 89%.



cdrecord command:

-----------------------

/usr/bin/cdrecord -v gracetime=2 dev=ATAPI:/dev/hdc speed=12 -dao driveropts=burnfree -eject -data /mnt/hda5/linux iso/slackware-10.2-install-d1.iso

And is the output of cdrecord command

Code:

mann@Manish:~$ cdrecord -scanbus

Cdrecord-ProDVD-Clone 2.01.01a10 (i686-pc-linux-gnu) Copyright (C) 1995-2006 Jörg Schilling

cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.

cdrecord: For possible targets try 'cdrecord -scanbus'.

cdrecord: For possible transport specifiers try 'cdrecord dev=help'.

mann@Manish:~$

I have tried and reinstalled 3 differnet packages of k3b, cdrtools and cdrdao and still no luck. Any suggestions?

If you are using kernel 2.4.x you could try to enable ide-scsi in lilo (on expert setup it will suggest this option).

Quote:

Originally Posted by vbisis

If you are using kernel 2.4.x you could try to enable ide-scsi in lilo (on expert setup it will suggest this option).

Thanks. I will try it tonight when I reach home. Is this something wrong with CDRECORD?

No, but with kernel 2.4.x it is necessary to use scsi emulation with cdroms to burn.
If you upgrade to kernel 2.6.x you won't need that anaymore, I'm not really sure why though.

Code:

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/hda1

  label = hd0

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

  append="hdc=ide-scsi"

I added the line indicated in red color to the /etc/lilo.conf file. But, still when I try to write a CD in auto mode, it corrupts my CD. That's not a problem right now as I am testing this only on my Re-writable CD, but, why is not working?

You need to change your fstab entry for hdc as well since it is now sr0 ( I think - just check your /var/log/messages ) .
Try to change entry to the right scsi device and test it by mounting a cd.

You should see something like this in v/var/log/messages:

hdc: attached ide-scsi driver.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: PLEXTOR Model: CD-R PX-W1610A Rev: 1.04
Type: CD-ROM ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0

Sorry for responding late. This is what I see in /var/log/messages

Code:

mann@Manish:~$ sudo cat /var/log/messages | grep hdc

Jul  3 21:54:43 Manish kernel:    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio

Jul  3 21:54:43 Manish kernel: hdc: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)

mann@Manish:~$

Code:

mann@Manish:~$ sudo cat /var/log/messages | grep scsi

Jul  3 21:54:43 Manish kernel: scsi0 : SCSI host adapter emulation for IDE ATAPI devices

mann@Manish:~$

And here's what I have in /etc/fstab.

Code:

/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0

But, I don't think making changes in this file would change anything as it is used for mounting purpose only whereas k3b doesn't even mount them as far as I know.
PLease tell me what I should do now?

Thats the problem: /dev/cdrom is a symlink to /dev/hdc and it should go to some scsi device where emulation runs on. Find out how the device is named ( like I said something like sr0 ) and either change the symlink on /dev/cdrom to that device or change your fstab .

Easiest way to test is to save your current fstab-file and change entry for cdrom to:

/dev/sr0 /mnt/cdrom auto noauto,owner,ro 0 0

Then just put a cd in it and mount it to see if it works. If it does so far you can try to brun some cd.

Quote:

Originally Posted by vbisis

If you are using kernel 2.4.x you could try to enable ide-scsi in lilo (on expert setup it will suggest this option).

Hello vbisis,
You were 100% correct. Today I reinstalled Slackware 10.2 on my machine and this time I entered hdc=ide-scsi option to lilo at the time of installation. Now, it's burning my CDs without any problems.
Thank you very much. :)