[Bug 1356528] Re: k3b dvd burning crashes with growisofs and -use-the-force-luke=dao: option

Jantaegert 1356528 at bugs.launchpad.net
Thu Aug 14 10:27:37 UTC 2014


Hi,

thanks for your detailed answer. And yes, you're right, I should wait 
until the burning process has finished ;-)

Here are the last few lines output:

197656576/197683200 (100.0%) @0.0x, remaining 0:00 RBU   0.1% UBU 100.0%
   197656576/197683200 (100.0%) @0.0x, remaining 0:00 RBU   0.1% UBU 100.0%
   197656576/197683200 (100.0%) @0.0x, remaining 0:00 RBU   0.1% UBU 100.0%
   197656576/197683200 (100.0%) @0.0x, remaining 0:00 RBU   0.1% UBU 100.0%
   197656576/197683200 (100.0%) @0.0x, remaining 0:00 RBU   0.1% UBU 100.0%
:-[ WRITE at LBA=17900h failed with SK=0h/ASC=00h/ACQ=03h]: Input/output error
:-( write failed: Input/output error
/dev/sr0: flushing cache


What do you think, is this a drive issue like you mentioned before or 
something else? I found some bug reports with similar errors.

btw, I found a dvd+r double layer disc in my working desk and tried this 
one. Besides dummy write has not worked and I've wasted a double layer 
disc for about 200 MByte of data, everything went fine.

The not working disc is a dvd-r type.

Thanks,

Jan.



Am 14.08.2014 um 08:58 schrieb Thomas Schmitt:
> Hi,
>
> did you wait the time necessary to write a full gigabyte
> when  -use-the-force-luke=dao  was in effect ?
>
> Why i ask:
>
> -use-the-force-luke=dao:96525 tells growisofs to use
> write type DAO rather than Incremental. Further it predicts
> the track size as 96525 blocks of 2048 bytes.
>
> The number has to match exactly the size of the input ISO image.
> I.e. show-musikprojekt.iso must have 197,683,200 bytes.
> Since you did not have to remove option
> -use-the-force-luke=tracksize:96525, i assume that ISO size
> and number do match.
>
> You already noticed a difference between DAO and Incremental
> at the start of a burn session. DAO knows the size of the track
> in advance and thus writes the table-of-content first.
> Incremental does not know how many blocks will be written and
> thus writes the table-of-content after the track was written.
>
> Another difference is that DAO results in a medium state that
> complies with the DVD-ROM standard ECMA-267. Its section 10.6
> demands that the medium gets burned a ring of at least 70
> millimeters. This is the width of a session of about 1 GB.
>
> So any DAO session lasts at least as long as a 1 GB session.
>
> If your drive does not end a DAO session after a due waiting time,
> then it is probably at the edge of failure. In this case you
> should be mistrusting towards its allegedly successful runs.
> Do checkread.
>
>
> Have a nice day :)
>
> Thomas
>

-- 
You received this bug notification because you are a member of Ubuntu
Burning Team, which is subscribed to k3b in Ubuntu.
https://bugs.launchpad.net/bugs/1356528

Title:
  k3b dvd burning crashes with growisofs and -use-the-force-luke=dao:
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/1356528/+subscriptions



More information about the Ubuntu-burning mailing list