Bug 656502 - K3b input/output error burning bluray BD-R
K3b input/output error burning bluray BD-R
Status: RESOLVED NORESPONSE
Classification: openSUSE
Product: openSUSE 11.3
Classification: openSUSE
Component: KDE4 Applications
Final
x86-64 openSUSE 11.3
: P5 - None : Critical with 5 votes (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-30 08:54 UTC by Vladimir Psenicka
Modified: 2012-03-19 20:10 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
K3b error log burning BD-R (75.25 KB, text/plain)
2010-11-30 08:56 UTC, Vladimir Psenicka
Details
K3b error burning BD-R (80.07 KB, image/png)
2010-11-30 08:57 UTC, Vladimir Psenicka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Psenicka 2010-11-30 08:54:30 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7

I have problem writing files with k3b on BD-R discs. Everytime it ends with error. Once with disk is full although k3b tell I have still 100MB free. Second with input/ouput error. I have external bluray writer HL-DT-ST BD-RE  BE08LU20 connected via esata.

Reproducible: Always

Steps to Reproduce:
1. launch k3b
2. burn BD-R disc
3. ended with error
Actual Results:  
won't work

Expected Results:  
it should work
Comment 1 Vladimir Psenicka 2010-11-30 08:56:07 UTC
Created attachment 402656 [details]
K3b error log burning BD-R
Comment 2 Vladimir Psenicka 2010-11-30 08:57:25 UTC
Created attachment 402657 [details]
K3b error burning BD-R
Comment 3 Eugen Neuber 2010-12-04 23:37:31 UTC
(In reply to comment #0)

> I have external bluray writer HL-DT-ST BD-RE  BE08LU20
> connected via esata.

Maybe it helps that my config does work:

internal Bluray burner from LG type BH10LS30 (SATA)
connected via SATA-to-USB2

burnt and verified correctly 46 GB (to BD-RE 50 GB) in almost 4 hours with k3b (from k3b-2.0.0-1.1.1.x86_64 )
Comment 4 Vladimir Psenicka 2010-12-06 09:42:36 UTC
What version of genisoimage and wodim do you have?
Comment 5 Vladimir Psenicka 2010-12-06 11:04:25 UTC
Other error with continuing multisession project on BD-R:

Fatal error at startup: invalid argument 


Debug log:

Burned media
-----------------------
BD-R Sequential Pseudo Overwrite (SRM+POW)

Devices
-----------------------
HL-DT-ST BD-RE  BE08LU20 2.00 (/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]
HL-DT-ST DVD-RAM GSA-H50L 1.03 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, 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] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 44255 (90634240 bytes)

System
-----------------------
K3b Version: 2.0.1
KDE Version: 4.4.4 (KDE 4.4.4) "release 3"
QT Version:  4.6.3
Kernel:      2.6.34.7-0.5-desktop

Used versions
-----------------------
mkisofs: 1.1.11
growisofs: 7.1

growisofs
-----------------------
/usr/bin/growisofs: -C argument is insane.

growisofs command:
-----------------------
/usr/bin/growisofs -C 0,0 -M /dev/sr1=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:44255 -speed=4 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
Rock Ridge signatures found
44255

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -cdrecord-params 0,0 -prev-session /dev/sr1 -gui -graft-points -print-size -quiet -volid Alex_zaloha2 -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-PAVOUK\psenicka/k3bC19897.tmp -rational-rock -hide-list /tmp/kde-PAVOUK\psenicka/k3bk19897.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-PAVOUK\psenicka/k3bG19897.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-PAVOUK\psenicka/k3bq19897.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -cdrecord-params 0,0 -prev-session /dev/sr1 -gui -graft-points -volid Alex_zaloha2 -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-PAVOUK\psenicka/k3bt19897.tmp -rational-rock -hide-list /tmp/kde-PAVOUK\psenicka/k3bA19897.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-PAVOUK\psenicka/k3bw19897.tmp -no-cache-inodes -full-iso9660-filenames -iso-level 3 -path-list /tmp/kde-PAVOUK\psenicka/k3bO19897.tmp


Something bad with growisofs?
Comment 6 Vladimir Psenicka 2010-12-06 12:00:58 UTC
I found similar bug on ubuntu:
https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/600770
Comment 7 Vladimir Psenicka 2010-12-06 12:32:21 UTC
I found disk full problem in this bug:
https://bugs.kde.org/show_bug.cgi?id=246170

Seems BD-R writing is broken for now...
Comment 8 Eugen Neuber 2010-12-06 12:41:42 UTC
(In reply to comment #4)
> What version of genisoimage and wodim do you have?

$ genisoimage
genisoimage 1.1.9 (Linux)

$ rpm -qf `which genisoimage `
genisoimage-1.1.9-8.2.x86_64

$ wodim --version
Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd 
Wodim 1.1.9

$ rpm -qf `which wodim `
wodim-1.1.9-8.2.x86_64
Comment 9 Vladimir Psenicka 2010-12-06 12:53:08 UTC
(In reply to comment #8)
> (In reply to comment #4)
> > What version of genisoimage and wodim do you have?
> 
> $ genisoimage
> genisoimage 1.1.9 (Linux)
> 
> $ rpm -qf `which genisoimage `
> genisoimage-1.1.9-8.2.x86_64
> 
> $ wodim --version
> Cdrecord-yelling-line-to-tell-frontends-to-use-it-like-version 2.01.01a03-dvd 
> Wodim 1.1.9
> 
> $ rpm -qf `which wodim `
> wodim-1.1.9-8.2.x86_64

I have updated cdrkit to 1.1.11 and same problems persists...
Comment 10 Eugen Neuber 2010-12-06 16:21:03 UTC
Although I can burn DB-RE I also can not burn BD-R !

First k3b showed for a 25 GB disc only 8 GB but changed to 25 GB at the next repaint event of the window.

K3b error ("not enough space on disc availlable") log is:
--8<--
Burned media
-----------------------
BD-R sequenziell (SRM)

Devices
-----------------------
HL-DT-ST BD-RE  BH10LS30 1.00 (/dev/sr1, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R doppelschichtig, BD-CD-ROM, BD-CD-R, BD-RE, DVD+R, DVD+RW, DVD+R doppelschichtig) [DVD-ROM, DVD-R sequenziell, Zweischichtige DVD-R sequenziell, Zweischicht-DVD-R-Sprung, DVD-RAM, DVD-RW Eingeschränktes Überbrennen, DVD-RW sequenziell, DVD+RW, DVD+R, Zweischichtige DVD+R, CD-ROM, CD-R, CD-RW, BD-CD-ROM, BD-R sequenziell (SRM), BD-R Zufällig (RRM), BD-RE] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Eingeschränktes Überschreiben, Sprung zwischen DVD-Schichten, Zufällige Aufnahme, Sequenzielle Aufnahme, Sequenzielle Aufnahme + POW] [%7]
MATSHITA DVD-RAM UJ-842 RB01 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R doppelschichtig, DVD+R, DVD+RW, DVD+R doppelschichtig) [DVD-ROM, DVD-R sequenziell, Zweischichtige DVD-R sequenziell, Zweischicht-DVD-R-Sprung, DVD-RAM, DVD-RW Eingeschränktes Überbrennen, DVD-RW sequenziell, DVD+RW, DVD+R, Zweischichtige DVD+R, CD-ROM, CD-R, CD-RW] [SAO, TAO, Eingeschränktes Überschreiben, Sprung zwischen DVD-Schichten] [%7]

K3b::IsoImager
-----------------------
mkisofs print size result: 12981620 (26586357760 bytes)

System
-----------------------
K3b Version: 2.0.0
KDE Version: 4.4.4 (KDE 4.4.4) "release 3"
QT Version:  4.6.3
Kernel:      2.6.34.7-0.5-desktop

Used versions
-----------------------
mkisofs: 1.1.9
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr1 obs=32k seek=0'
:-( /dev/sr1: 12219392 blocks are free, 12981620 to be written!

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr1=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:12981620 -speed=9 -use-the-force-luke=bufsize:32m

mkisofs
-----------------------
12981620
I: -input-charset not specified, using utf-8 (detected in locale settings)

mkisofs calculate size command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -print-size -quiet -volid Backup-20101206 -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-eugen/k3bG14890.tmp -rational-rock -hide-list /tmp/kde-eugen/k3bU14890.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-eugen/k3bf14890.tmp -no-cache-inodes -full-iso9660-filenames -disable-deep-relocation -iso-level 3 -path-list /tmp/kde-eugen/k3bT14890.tmp

mkisofs command:
-----------------------
/usr/bin/genisoimage -gui -graft-points -volid Backup-20101206 -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-eugen/k3bY14890.tmp -rational-rock -hide-list /tmp/kde-eugen/k3bL14890.tmp -joliet -joliet-long -hide-joliet-list /tmp/kde-eugen/k3bM14890.tmp -no-cache-inodes -full-iso9660-filenames -disable-deep-relocation -iso-level 3 -path-list /tmp/kde-eugen/k3bz14890.tmp
--8<--
Comment 11 Jörg Schiling 2010-12-07 17:54:05 UTC
First, genisoimage and wodim are both unmaintained and buggy forks from a 6 year old version of cdrtools.

In special genisoimage creates filesystems with plenty of hidden problems that can cause problems in the future.

Second: I see no problem in the logs......

In any case, it makes sense to try to use crecord to write the BluRay medium.
Make sure to use cdrtools-3.00 or better 3.01a01.
Comment 12 Eugen Neuber 2010-12-08 18:19:47 UTC
(In reply to comment #11)
> In any case, it makes sense to try to use crecord to write the BluRay medium.
> Make sure to use cdrtools-3.00 or better 3.01a01.

I can confirm cdrtools-3.01a01 did the job on a 25 GB BD-R (no errors and all files I checked with md5sum where identical).
Comment 13 Vladimir Psenicka 2010-12-08 20:06:15 UTC
Any chance to include cdrtools instead of buggy cdrkit/genisoimage in opensuse?
Comment 14 Vladimir Psenicka 2010-12-08 20:07:34 UTC
(In reply to comment #12)
> (In reply to comment #11)
> > In any case, it makes sense to try to use crecord to write the BluRay medium.
> > Make sure to use cdrtools-3.00 or better 3.01a01.
> 
> I can confirm cdrtools-3.01a01 did the job on a 25 GB BD-R (no errors and all
> files I checked with md5sum where identical).

Where did you get cdrecord binaries or did you compile it yourself?
Comment 15 Eugen Neuber 2010-12-08 20:25:06 UTC
(In reply to comment #14)
> (In reply to comment #12)
> > (In reply to comment #11)
> > > In any case, it makes sense to try to use crecord to write the BluRay medium.
> > > Make sure to use cdrtools-3.00 or better 3.01a01.
> > 
> > I can confirm cdrtools-3.01a01 did the job on a 25 GB BD-R (no errors and all
> > files I checked with md5sum where identical).
> 
> Where did you get cdrecord binaries or did you compile it yourself?

I downloaded the source from:
ftp://ftp.berlios.de/pub/cdrecord/alpha/

and compiled it myself. I didn't need to deinstall wodim/genisoimage from opensuse because it installs into /opt/schily and k3b will find it automatically at startup.
Comment 16 Christian Trippe 2012-01-30 20:38:43 UTC
openSUSE 11.3 is out of maintenance. Is this bug still valid with openSUSE
12.1?
Comment 17 Christian Trippe 2012-03-19 20:10:37 UTC
No reply in more than 4 weeks. Please reopen if you are able to provide the requested information.