[Bug 1458230] Re: libburn imposing 0.2x BD-R burn (5-6 hours)

[Thomas Schmitt]

Hi,

> I hope I'd followed your recommendation correctly.

The xorriso command looks ok. If you do not plan to produce and
burn add-on ISO sessions you may omit option -multi.

> I burnt a second copy of each ISO, which should
> give me a high probability of full recovery using gddrescue, if the time
> comes.

You should record own checksums additionally to those of the media
which decide over read succes versus i/o error. After some rescue tool 
pieced together an alleged repaired version of the ISO you need means
to verify this.

xorrisofs offers option --md5, xoriso offers command -md5 "on".
Both will put MD5 sums into the ISO which can at any time later
checked by xorriso commands -check_media and -check_md5_r.


> during the formatting stage, each successive status line reported 
> progress as 1%.

It depends much on the willingness of the drive to indicate progress.
libburn sends a SCSI command to which the drive is supposed to reply
a number between 0 and 65535. This number represents a range of 0 to
100 percent. For reasons of plausibility i rather map it to 1 to 99
percent.
So probably your drive returned 0 all the time.


Have a nice day :)

Thomas

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

Title:
  libburn imposing 0.2x BD-R burn (5-6 hours)

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