K3b messages vs. ISO quality

[ebvt]

If I look at the results after burning of ISO I seem to have problems on more than one computer.  The typical result starting at the line below writing speed: fatal error during recording: input/output error

Writing data   96%
Overall progress   96%

1299 MiB of 1351 MiB

md5sum is ok on one burner  brand new lite -on
md5sum is "way off"  on another  brand new VAIO

Both ISOs pass media check  -  ok to install from this media
Both ISOs boot up w/o problem and work

I do get a "KDE closed unexpectedly" message.

Has anybody else seen this kind of behavior? Is there anything I can do about it?

ebvt

[DeBaas]

"KDE closed unexpectedly"
It seems to be a timing error somewhere.
Till now I always had a working DE after this message and could install the LivCD without any errors, so I ignored this message.

Ed

[ebvt]

Thanks DeBaas, I should have mentioned that I had no problems after that message. I just included it for completeness. But what I still can't understand is all the "fatal errors" and incomplete writings messages that clash with the fact that the ISOs work. Even the one with the wrong md5sum!

ebvt

[µT6]

i can't help with k3b since i haven't used it in years

when it began giving me weird messages and problems i installed brasero, it works well for me and others had good experiences with it

it doesn't have as much tools and options as k3b but it does work well

[ebvt]

@mT6

Thanks, but I don't think that works with KDE?

ebvt

[µT6]

yes it works

brasero works in my netbook and desktop, both running kde4

i wpuldn't recomend it if i didn't tested it first

[ebvt]

I don't know why I let myself be discouraged when I did not see brasero in the right-click window! Anyway, I'm typing this from the new LiveCD via brasero accompanied by the Tijuana Brass!
md5sum right on the button.

Thanks,
ebvt

[Crow]

I'm using K3B without problems, this week burnt 6 CD's and all worked fine.

[µT6]

yes, k3b is working well for some users but others can't do much with it

same is happening for some with brasero, specially with external drives, my external drive works well with brasero

not sure what causes this situation

[taelti]

Also I have bad memories with k3B. I use simpleburn instead sometimes brasero.

[wedgetail]

I have just written two DVD-R using K3b, which I have been using for years, I have once had some bigger trouble with K3b, there is a thread on Forum, but else it just seem to work. I have however just received very similar message as posted here.  When the second DVD failed I discarded them both without testing but I have just re-covered them from the trash after having read the postings here.

The two DVDs were an attempt to write KDE 2012.12 as a backup copy. Unusual for me I actually checked the md5sum before write exercise, no problem. I have been lax with md5sum checking as they always seem to match. The first DVD write reads ok  in optical drive, I assume the second also do, that is drying on the clothesline at the moment.


I did make a copy of K3B log for the first write:

-----------------------------------------------  log -----------------------------------
Burned media
-----------------------
DVD-R Sequential

Devices
-----------------------
PIONEER DVD-RW  DVR-218L 1.02 (/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]

System
-----------------------
K3b Version: 2.0.2
KDE Version: 4.9.2
QT Version:  4.8.2
Kernel:      3.2.18-pclos2.bfs

Used versions
-----------------------
growisofs: 7.1

growisofs
-----------------------
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: engaging DVD-R DAO upon user request...
/dev/sr0: reserving 691999 blocks
/dev/sr0: "Current Write Speed" is 8.2x1352KBps.
     622592/1417213952 ( 0.0%) @0.0x, remaining 189:36 RBU 100.0% UBU   0.0%
     622592/1417213952 ( 0.0%) @0.0x, remaining 303:22 RBU 100.0% UBU 100.0%
     622592/1417213952 ( 0.0%) @0.0x, remaining 455:03 RBU 100.0% UBU 100.0%
     622592/1417213952 ( 0.0%) @0.0x, remaining 568:49 RBU 100.0% UBU 100.0%
...
...
...
 1296826368/1417213952 (91.5%) @6.6x, remaining 0:18 RBU 100.0% UBU  98.6%
 1327398912/1417213952 (93.7%) @6.6x, remaining 0:13 RBU 100.0% UBU  98.6%
 1358135296/1417213952 (95.8%) @6.7x, remaining 0:08 RBU 100.0% UBU  98.6%

growisofs command:
-----------------------
/usr/bin/growisofs -Z /dev/sr0=/dev/fd/0 -use-the-force-luke=notray -use-the-force-luke=tty -use-the-force-luke=4gms -use-the-force-luke=tracksize:691999 -use-the-force-luke=dao:691999 -dvd-compat -speed=8 -use-the-force-luke=bufsize:32m
 
-----------------------------------------------  log -----------------------------------

Perhaps this is a clue for somebody.  Not for me as I normally don't look at the log so I don't know what it should look like.  I will check if it can run.  

Edit:
Well it booted fine and runs as I am using the LiveCD to post this addition. In that case I expect the drying version will be ok, one of the grand kids were told to scrible all over the second write to make sure I knew it was a dud.  fortunately he did it on the top side so I have washed it off again as the artwork did not stick well.  

[Crow]

I've just finished burning an audio cd for my son and is plying right now. I used K3B, excellent.

[Nok]

K3b seems to have a habit of reporting false errors. It doesn't do it every time, just often enough to be disconcerting. The thing is, it has yet to produce a coaster for me. I've learned to ignore errors. Ymmv.

[ebvt]

@Crow
I did not say the isos did not work. I was just surprised about the amount of apparently false negatives I received!

@nok
That's exactly my point. Same here: no coasters. So in the future, as long as the md5sum is ok and I get the pass confirmation in media check, I will stop worrying.

Thanks a lot

ebvt

EDIT:
Thanks, wedgetail, for yor confirmation

[horusfalcon]

If I look at the results after burning of ISO I seem to have problems on more than one computer.  The typical result starting at the line below writing speed: fatal error during recording: input/output error

Writing data   96%
Overall progress   96%

1299 MiB of 1351 MiB

md5sum is ok on one burner  brand new lite -on
md5sum is "way off"  on another  brand new VAIO

Both ISOs pass media check  -  ok to install from this media
Both ISOs boot up w/o problem and work

I do get a "KDE closed unexpectedly" message.

Has anybody else seen this kind of behavior? Is there anything I can do about it?

ebvt

Seeing "1299 MiB of 1351 MiB"  makes me wonder what's being left out?

It would help to know which ISOs were burned (presumably some form of PCLinuxOS KDE after 2012.08, or some form of Full Monty?)

I've seen the "KDE closed unexpectedly", too.  Just as you describe, though, it seems the system recovers gracefully.

I've been using K3B since my OpenS__e 10.0 days with no problems on a wide variety of hardware.  I still use it on my KDE4/LXDE system from within LXDE, and it works fine.  I'm curious what examining the burned disks with K3B's Device --> Media Info menu option might reveal?

Do you know if you are using DMA on your optical drives?  (I find generally better results with it enabled.)

Later On,
D