[k3b] [Bug 380067] [MATSHITA BD-MLT UJ240AS] :-( unable to WRITE at LBA=6d9a00h: Input/output error

Thomas Schmitt bugzilla_noreply at kde.org
Tue Jun 6 07:19:13 UTC 2017


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

--- Comment #3 from Thomas Schmitt <scdbackup at gmx.net> ---
Hi,

the end of the log looks like drive and medium had problems with
Defect Management. Up to 70.7 % the run had a normal speed for
2x BD media under Defect Management. Then effective speed drops
to values which indicate re-location of blocks.
The medium seems to have degrading quality towards its end.

The final error happens after 209 MB of hobbling. It is not a medium
error but rather a problem of the drive firmware.
The drive issued a status code which indicates that it had experienced
a medium change or a similar problem, but now is ready for work again.
Such an event is not normal. I'd blame it on the firmware's efforts
with Defect Management, if i had to guess.

It might be that the problem is about the indivual medium and that
the next try will succeed.
If it is systematic among all media of a particular brand, then you
could try BD-R from other brands.

If it is just about the internal pitfalls of Defect Management (one
can see it fail quite often), then one could try whether the media work
if Defect Management is disabled.
Using cdrskin as backend would avoid automatic formatting of the BD-R
and thus not enable Defect Management.
With growisofs one would have to use option

  -use-the-force-luke=spare=none

to avoid formatting.

If you burn without Defect Management on possibly poor media, then it
is important to checkread the media after burning.

(If it is about BD-RE media, then formatting is inavoidable. With cdrskin
 it is possible to nevertheless disable Defect Management by option

   stream_recording=off

)


At this point i have to hand over to Leslie or others who know how
to let K3B use extra options of cdrskin and/or growisofs.


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