public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99%
Date: Sun, 7 Jul 2013 17:19:30 -0500	[thread overview]
Message-ID: <CAEH5T2NjSt1aCsr6k_OVdf13ex5B-pAhDH=UzB4HggdHD6Vr2g@mail.gmail.com> (raw)
In-Reply-To: <1750135.6IRHZHqc9Q@zeus>

On Sat, Jul 6, 2013 at 11:33 AM, Alexander Puchmayr
<alexander.puchmayr@linznet.at> wrote:
> I just burned all my pictures from my last vacation on a blueray-disk using
> k3b, and for no apparent reason it stoped at 99.8% and complained an error
> (I/O error). I checked the logs (see attached file), but could not find a hint.
> I compared each and every file on the disk with its original, but yould not find
> any problem.

Maybe it is same as described in this bug:

https://bugs.kde.org/show_bug.cgi?id=255483

I don't use k3b but I know when I burn a 25GB disc image using
growisofs, I have to disable the spare sectors otherwise it won't fit
on the disc, and it burns all the way until the end where it fails,
rather than "knowing" ahead of time that it won't fit.


  parent reply	other threads:[~2013-07-07 22:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06 16:33 [gentoo-user] k3b burning BD-Disk pretends to fail at 99.99% Alexander Puchmayr
2013-07-06 21:55 ` Joerg Schilling
2013-07-07 12:06   ` Alexander Puchmayr
2013-07-07 16:31     ` Joerg Schilling
2013-07-08  6:53     ` Paul Colquhoun
2013-07-09  7:57       ` Mick
2013-07-10  5:29         ` Thomas Schmitt
2013-07-10  6:26           ` Dale
2013-07-10  7:23             ` Thomas Schmitt
2013-07-10  7:29               ` Dale
2013-07-10  7:46                 ` Thomas Schmitt
2013-07-10  8:36                   ` Joerg Schilling
2013-07-10  9:30                     ` Thomas Schmitt
2013-07-10  9:46                       ` Joerg Schilling
2013-07-13  6:16                     ` Alexander Puchmayr
2013-07-13 10:18                       ` Thomas Schmitt
2013-07-10  8:34                 ` Joerg Schilling
2013-07-10  8:33               ` Joerg Schilling
2013-07-10  8:16             ` Joerg Schilling
2013-07-13  6:30             ` Alexander Puchmayr
2013-07-13 10:08               ` Thomas Schmitt
2013-07-13 11:43                 ` Mick
2013-07-13 12:35                   ` Thomas Schmitt
2013-07-13 13:03                 ` Bruce Hill
2013-07-13 13:38                   ` Thomas Schmitt
2013-07-13 16:38                     ` Bruce Hill
2013-07-13 17:03                   ` Thomas Schmitt
2013-07-13 17:30                     ` Bruce Hill
2013-07-13 18:15                       ` Thomas Schmitt
2013-07-13 21:25                         ` Bruce Hill
2013-07-13 22:01                           ` Thomas Schmitt
2013-07-14 14:20                             ` Joerg Schilling
2013-07-14 14:08                         ` Joerg Schilling
2013-07-14 13:52                     ` Joerg Schilling
2013-07-14 11:32               ` Joerg Schilling
2013-07-10  7:57         ` Joerg Schilling
2013-07-10  8:42           ` Mick
2013-07-07 22:19 ` Paul Hartman [this message]
2013-07-08  7:40   ` Alexander Puchmayr
2013-07-08 10:51     ` Joerg Schilling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEH5T2NjSt1aCsr6k_OVdf13ex5B-pAhDH=UzB4HggdHD6Vr2g@mail.gmail.com' \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox