K3B crashing during burn on input/output error

I can no long burn media with K3b. It worked fine until the last update. I have removed a reloaded the application but no joy. Thanks for the help in advance. Here is the Debug Output…

Devices


PIONEER BD-RW BDR-209M 1.20 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] %7]
HL-DT-ST BD-RE BE12LU30 4261 (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, BD-ROM, BD-R, BD-RE, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW, BD-ROM, BD-R Sequential (SRM), BD-R Random (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump, Random Recording, Sequential Recording, Sequential Recording + POW] %7]

K3b::IsoImager

mkisofs print size result: 117286 (240201728 bytes)

System

K3b Version: 2.0.3
KDE Version: 4.14.9
QT Version: 4.8.6
Kernel: 3.16.7-53-desktop

Used versions

mkisofs: 3.1a25
cdrecord: 3.1a25

cdrecord

cdrecord: Insufficient ‘file read’ privileges. You will not be able to open all needed devices.
cdrecord: Insufficient ‘file write’ privileges. You will not be able to open all needed devices.
cdrecord: Insufficient ‘device’ privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient ‘network’ privileges. You will not be able to do remote SCSI.
scsidev: ‘/dev/sr0’
devname: ‘/dev/sr0’
scsibus: -2 target: -2 lun: -2
Warning: Open by ‘devname’ is unintentional and not supported.
Linux sg driver version: 3.5.27
SCSI buffer size: 64512
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
Cdrecord-ProDVD-ProBD-Clone 3.01a25 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2014 Joerg Schilling
TOC Type: 3 = CD-ROM XA mode 2
Using libscg version ‘schily-0.9’.
Driveropts: ‘burnfree’
atapi: 1
Device type : Removable CD-ROM
Version : 5
Response Format: 2
Capabilities :
Vendor_info : 'PIONEER ’
Identifikation : ‘BD-RW BDR-209M’
Revision : ‘1.20’
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: CD-R
Profile: BD-RE
Profile: BD-R random recording
Profile: BD-R sequential recording
Profile: BD-ROM
Profile: DVD+R/DL
Profile: DVD+RW
Profile: DVD+R
Profile: DVD-R/DL layer jump recording
Profile: DVD-R/DL sequential recording
Profile: DVD-RW restricted overwrite
Profile: DVD-RW sequential recording
Profile: DVD-R sequential recording
Profile: DVD-RAM
Profile: Removable Disk
Profile: DVD-ROM
Profile: CD-RW
Profile: CD-R (current)
Profile: CD-ROM
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 LAYER_JUMP
Drive buf size : 1206272 = 1178 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 229 MB
Total size: 263 MB (26:03.84) = 117288 sectors
Lout start: 263 MB (26:05/63) = 117288 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
359846 2048 0x00 Unformated or Blank Media
Blocks total: 359846 Blocks current: 359846 Blocks remaining: 242558
Starting to write CD/DVD/BD at speed 40 in real TAO mode for multi 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 OFF.
Turning BURN-Free on
Performing OPC…
Starting new track at sector: 0
Track 01: 0 of 229 MB written.

Track 01: 85 of 229 MB written (fifo 100%) [buf 97%] 23.8x.
cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 AB B6 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.477s timeout 40s
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
write track data: error after 90025984 bytes
Writing time: 45.687s (00:00:45.687)
Average write speed 41.0x.
Min drive buffer fill was 91%
Fixating…
Fixating time: 17.783s (00:00:17.783)
cdrecord: fifo had 1482 puts and 1419 gets.
cdrecord: fifo was 0 times empty and 1260 times full, min fill was 82%.

cdrecord command:

/usr/bin/cdrecord -v gracetime=2 dev=/dev/sr0 speed=40 -tao driveropts=burnfree -multi -xa -tsize=117286s -

mkisofs

mkisofs: Warning: Cannot add inode hints with -no-cache-inodes.
117286
mkisofs: Warning: Cannot add inode hints with -no-cache-inodes.
Setting input-charset to ‘UTF-8’ from locale.
0.45% done, estimate finish Tue Jan 31 03:42:05 2017

38.80% done, estimate finish Tue Jan 31 03:40:14 2017

mkisofs calculate size command:

/usr/bin/mkisofs -gui -graft-points -print-size -quiet -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-vance/k3bSy6417.tmp -rational-rock -hide-list /tmp/kde-vance/k3bal6417.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-vance/k3bJN6417.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-vance/k3baL6417.tmp

mkisofs command:

/usr/bin/mkisofs -gui -graft-points -volid K3b data project -volset -appid K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK -publisher -preparer -sysid LINUX -volset-size 1 -volset-seqno 1 -sort /tmp/kde-vance/k3bsR6417.tmp -rational-rock -hide-list /tmp/kde-vance/k3bqR6417.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-vance/k3bHQ6417.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-vance/k3bmz6417.tmp

What update?

13.2 is out of support since 2 weeks and doesn’t get any updates any more.

Your output may suggest that it is a hardware problem though, e.g. a bad medium:

cdrecord: Input/output error. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 00 AB B6 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
Sense Key: 0x0 No Additional Sense, Segment 11
Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
Sense flags: Blk 0 (not valid) 
cmd finished after 0.477s timeout 40s
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.

OTOH, I also see this:

cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.

So maybe try to add your user to the “cdrom” group.
Although that shouldn’t be necessary normally, as logind should give you the necessary privileges on login. (maybe that’s where your problem lies?)

Actually, both 13.2 and 13.1 are still getting Packman updates.:wink:

That’s irrelevant here though (cdrecord is not available from Packman), and the last updates were just rebuilds anyway, no “real” updates.

Also, the Packman repos for 13.1 and 13.2 are going to be disabled now:
http://lists.links2linux.de/pipermail/packman/2017-January/014909.html
http://lists.links2linux.de/pipermail/packman/2017-January/014908.html

Okay.

Thought the OP was referring to K3B, which on my system is from Packman.:slight_smile:

Yes, but k3b is just a frontend and uses other programs to do the actual work.

Also, k3b has not been updated either since quite a while. Packman’s package is just a link to openSUSE’s (built with additional mp3 support).

The CDROM drive works fine under windows 7, so I believe it is software related. It looks like OpenSUSE 13.2 is no longer being supported. Several of the registries I have been using are gone. How do I make the move over to Tumble Weed with out re-installing the entire OS?

I found the instructions here: https://en.opensuse.org/openSUSE:Tumbleweed_upgrade
Sorry for the dumb question. I will let you know if this fixes K3B.

Well, it could be a driver issue, or it could be a single bad disc.

But probably more likely a permission problem as I mentioned later.

It looks like OpenSUSE 13.2 is no longer being supported. Several of the registries I have been using are gone.

I suppose you mean “repositories”… :wink:

But yes, 13.2 is out of support since 3 weeks, see https://en.opensuse.org/Lifetime#Discontinued_distributions .

How do I make the move over to Tumble Weed with out re-installing the entire OS?

Note though that Tumbleweed is a rolling distribution, i.e. it changes all the time and always gets the latest versions of software (including the kernel).

If you prefer a “stable”/fixed distribution like 13.2 and earlier, better upgrade to Leap.

Well, I tried to do an update to Tumbleweed, that did not work. So far I have never had any success trying to update an OS in OpenSUSE. So, I did an install of Tumbleweed which was a 98% successful. K3B works fine burning CD’s in Tumbleweed. Apparently the new AMD drivers for the Radeon HD6000 series chip set is not stable in Tumbleweed. I get flickering when I run programs in WINE and then it crashes the application. I cannot find a fix for this. I have tried Leap 42 and many of the programs I like, such as picture of the day, are not part of the KDE desktop. Overall I think Leap 42 was a step backwards from 13.2. I wish the people running SUSE 13.2 would not have remove the repositories I was using. SUSE 13.2 was very stable and I really hate being forced to change my preferred Linux OS flavor simply because it is not the latest and greatest revision. After looking around Ubuntu has better AMD driver support so It looks like I will be leaving SUSE. I was not as happy with the options in the KDE desktop on Ubuntu but stability is more important then eye candy. Maybe Leap 43 will include all the flexibility and stability of 13.2 and I will come back. Until then, Thank You everyone for all the great support and help through the years.

What programs are you missing?
“picture of the day” is not a “program”, but a desktop applet/widget.
And I think it has been re-added in the latest Plasma 5.9.0 (released last week), you could install that on 42.2 too by adding additional repos.

Plasma5 has been a major rework from the KDE4 version, not everything has been ported (yet) and may reappear in future versions, and some things were dropped on purpose.

Though “many of the programs” are missing is a bit overexaggerated though I suppose.

Some (3rd party) widgets are also available in the “KDE store”, which you can reach via the “Get New” buttons (in the Add Widgets dialog in this case), the “discover” application, or just a web browser (https://store.kde.org/)…

I wish the people running SUSE 13.2 would not have remove the repositories I was using.

The “people running SUSE 13.2” have not removed the repositories you were using.
The people that created/maintained those additional repositories in the first place have.

Note that there is no “SUSE 13.2”, you are talking about openSUSE and 3rd party repos, which is/are created and maintained by the community (and to a large part by volunteers in their spare time) and is available for free.

And this is open source anyway.
You can always build stuff you need yourself (you can even create your own repos on OBS), also for no longer supported openSUSE versions.