Re: misleading error messages

[Thomas Schmitt]

Hi,

i was able to reproduce the messages by a not-so-useful sequence of
xorriso commands. The cause could be a missing -commit command before
the post-burn commands -check_md5 and -eject.
Like:

  xorriso -for_backup -abort_on FATAL -outdev /dev/sr4 -map ./100gb /100gb \
          -check_md5 FAILURE -- -eject all

The messages are

  Media summary: 0 sessions, 0 data blocks, 0 data, 23.1g free
  xorriso : UPDATE :       1 files added in 1 seconds
  Added to ISO image: file '/100gb'='/daten/dvdbuffer/100gb'
  xorriso : WARNING : No session MD5 is recorded with the loaded session
  MD5 MISMATCH WITH DATA OF LOADED SESSION !
  xorriso : FAILURE : Event triggered by MD5 comparison mismatch
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : FAILURE : -eject: Image changes pending. -commit or -rollback first
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : FAILURE : Image size 52428992s exceeds free space on media 12088288s
  libisofs: MISHAP : Image write cancelled
  xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE

------------------------------------------------------------------------

A more appropriate run would be

  xorriso -for_backup -abort_on FATAL -outdev /dev/sr4 -map ./100gb /100gb \
          -commit \
          -check_md5 FAILURE -- -eject all

The messages are then

  xorriso : UPDATE :       1 files added in 1 seconds
  Added to ISO image: file '/100gb'='/daten/dvdbuffer/100gb'
  xorriso : FAILURE : Image size 52428992s exceeds free space on media 12088288s
  libisofs: MISHAP : Image write cancelled
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : WARNING : No session MD5 is recorded with the loaded session
  MD5 MISMATCH WITH DATA OF LOADED SESSION !
  xorriso : FAILURE : Event triggered by MD5 comparison mismatch
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : FAILURE : -eject: Image changes pending. -commit or -rollback first
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE

------------------------------------------------------------------------

With a smaller payload which fits on the medium i get

  Media summary: 0 sessions, 0 data blocks, 0 data, 23.1g free
  xorriso : UPDATE :       1 files added in 1 seconds
  Added to ISO image: file 
'/debian-11.0.0-amd64-netinst.iso'='/...path.../debian-11.0.0-amd64-netinst.iso'
  xorriso : UPDATE : Writing:         32s    0.0%   fifo 100%  buf   0%
  libburn : NOTE : Write start address is  32 * 2048
  ...
  xorriso : UPDATE : Writing:     192544s   99.7%   fifo  24%  buf 100%    0.9xB
  ISO image produced: 193051 sectors
  Written to medium : 193216 sectors at LBA 32
  Writing to '/dev/sr4' completed successfully.

  xorriso : NOTE : Re-assessing -outdev '/dev/sr4'  ('/dev/sg6')
  xorriso : NOTE : Loading ISO image tree from LBA 0
  xorriso : UPDATE :       1 nodes read in 1 seconds
  Drive current: -dev '/dev/sr4'
  Media current: BD-RE
  Media status : is written , is appendable
  Media summary: 1 session, 193051 data blocks,  377m data, 22.7g free
  Volume id    : 'ISOIMAGE'
  Checking loaded session by its recorded MD5.
  Session MD5 30e42c75d0a58dc262659e5440837bb1 , LBA 32 , 193049 blocks
  xorriso : UPDATE :  14976k content bytes read in 5 seconds , 0.7xB
  ...
  xorriso : UPDATE :  377.0m content bytes read in 29 seconds = 3.1xB
  Ok, session data match recorded md5.

------------------------------------------------------------------------

Without the -commit command before -check_md5 i get error messages because
no session was written and then loaded yet:

  xorriso : WARNING : No session MD5 is recorded with the loaded session
  MD5 MISMATCH WITH DATA OF LOADED SESSION !
  xorriso : FAILURE : Event triggered by MD5 comparison mismatch
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : FAILURE : -eject: Image changes pending. -commit or -rollback first
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'
  xorriso : NOTE : Tolerated problem event of severity 'FAILURE'

At program end a normal write run is performed because the session is
pending for being written:

  xorriso : UPDATE : Writing:         32s    0.0%   fifo 100%  buf   0%
  libburn : NOTE : Write start address is  32 * 2048
  ...
  xorriso : UPDATE : Writing:     193216s  100.0%   fifo   0%  buf 100%    0.8xB
  ISO image produced: 193051 sectors
  Written to medium : 193216 sectors at LBA 32
  Writing to '/dev/sr4' completed successfully.

  xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE

No MD5 check happens because -check_md5 was given before the session
gets burnt. No eject happens because the session is still pending for
being burnt, when the -eject command was given.

But a subsequent check run confirms the integrity of the burnt session
and ejects the medium:

  xorriso -for_backup -indev /dev/sr4 -check_md5 failure -- -eject all

------------------------------------------------------------------------


Have a nice day :)

Thomas