[k3b] [Bug 356434] Cannot Burn Multisession DVD's on Linux Mint System

[Leslie Zhai via KDE Bugzilla]

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

Leslie Zhai <xiangzhai83 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |---
     Ever confirmed|0                           |1

--- Comment #2 from Leslie Zhai <xiangzhai83 at gmail.com> ---
quote from Thomas Schmitt,

looks like a problem with cdrecord and multi-session on DVD-R.
Possible reasons are:

1) The first cdrecord run was not done with option -multi.
   I.e. the DVD-R is closed when the second run is attempted.

2) Option -sao of the second run spoiled the attempt to add a session.
   -sao could trigger write type Disk-At-Once which is not appropriate
   for media which already contain data.

3) cdrecord could be unwilling to do multi-session on DVD-R.
   I deem this unlikely, because i have seen reports that it works
   with DVD-R.

Investigations and tries:

1) One should inspect the DVD-R after the first run by runs like
     cdrecord dev=/dev/sr0 -minfo
     dvd+rw-mediainfo /dev/sr0
     xorriso -outdev /dev/sr0 -toc
     cdrskin dev=/dev/sr0 -toc
   xorriso would report for a DVD-R which capable of taking more data:
     Media status : is written , is appendable
   and for a DVD-R which cannot take more data
     Media status : is written , is closed

2) If the medium is reported to be "appendable", then leave out options
   -sao and -tsize. I.e.
     cdrecord -v gracetime=2 dev=/dev/sr0 speed=16 driveropts=burnfree -multi
-waiti -data ./some_image_file

3) Try whether cdrecord does multi-session when run by command line
     cdrecord -v -multi dev=/dev/sr0 ./first_image_file
     cdrecord -v -multi dev=/dev/sr0 ./second_image_file
   Above inspection commands should afterwards report 2 sessions.

-- 
You are receiving this mail because:
You are the assignee for the bug.