[k3b] [Bug 381074] [MATSHITA BD-MLT UJ240AS] Does not write image "debian-8.8.0-amd64-BD-1.iso"
Thomas Schmitt
bugzilla_noreply at kde.org
Sat Aug 26 16:50:48 UTC 2017
https://bugs.kde.org/show_bug.cgi?id=381074
--- Comment #20 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,
the given BD-R medium is not blank but rather seems to have been
used already with growisofs. Only growisofs formats BD-R to state SRM+POW:
Mounted Media: 41h, BD-R SRM+POW
The first track is completely written:
READ TRACK INFORMATION[#1]:
Track State: partial incremental
Track Start Address: 0*2KB
Free Blocks: 0*2KB
Track Size: 11560096*2KB
The remaining space is about 1 GIB:
READ TRACK INFORMATION[#2]:
Track State: invisible incremental
Track Start Address: 11560096*2KB
Next Writable Address: 11560096*2KB
Free Blocks: 528224*2KB
Track Size: 528224*2KB
The peculiar formatting causes an optimistic reply about the number of
readable blocks. It includes written and unwritten capacity:
READ CAPACITY: 12088320*2048=24756879360
-------------------------------------------------------------------------
This medium is indeed not suitable for a burn run of 21.4 GiB.
You need to insert a new one that was never burnt.
dvd+rw-mediinfo should report something like
...
READ DISC INFORMATION:
Disc status: blank
Number of Sessions: 1
State of Last Session: empty
"Next" Track: 1
Number of Tracks: 1
...
READ TRACK INFORMATION[#1]:
Track State: invisible incremental
Track Start Address: 0*2KB
Next Writable Address: 0*2KB
Free Blocks: 12219392*2KB
Track Size: 12219392*2KB
READ CAPACITY: 0*2048=0
-------------------------------------------------------------------------
If this is the medium that caused this bug report, then there remains
the riddle why
https://bugsfiles.kde.org/attachment.cgi?id=106037
shows the text
"Empty BD-R medium"
It should say something like "Appendable BD-R medium".
(And can it be that the english text "size 21,4 GiB" in the image bears
a german decimal comma ? Pinching eyes ...)
Have a nice day :)
Thomas
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the k3b
mailing list