Bug 316384

Summary:	k3b cannot verify BD-R due to i/o error but logs shows none
Product:	[Applications] k3b	Reporter:	Reartes Guillermo <rtguille>
Component:	Burning/Hardware	Assignee:	k3b developers <k3b>
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	bob, trueg
Priority:	NOR
Version:	2.0.2
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screenshot of K3b error output K3b debug output from the previous screenshot dvd+rw-mediainfo of the disc after the "failed" burn session Screenshot of k3b and "write" window messages k3b debugging data for prior png image attachment

Description Reartes Guillermo 2013-03-08 19:51:09 UTC

I burned a BD-R with 3 big files. 
K3b says that there was a fatal I/O error during burning.

Checking the debug output shows none, as if growisofs had finished ok.

This impedes K3b from doing a verification of the burned stuff. 

should i discard the disc or not? (BD-R are not cheap). And since it happens always, it seems like BR-R support is currently below DVDs or CDs. 

Reproducible: Always

Steps to Reproduce:
1. create a bd-r data project
2. select files
3. burn
Actual Results:  
It is not possible to very the burning content automatically.

One can do it manually (in case there are few files) and sha256sum will reveal that the burned files are ok. In case of many files it is impractical to use sha256sum by hand.

BD-R burning is heavily degraded, since one cannot automatically verify that the burn is ok.
Being able to verify what was burned is important.

Expected Results:  
if there is an error, then a more meaningful description, otherwise, i do expect to be able to do an automatic verification of the burned files by k3b, just like CDs or DVDs. 

# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.7.9-104.fc17.x86_64 root=UUID=7397103e-0f3c-4baf-88b2-b78b9ebd46e5 ro rd.lvm=0 rd.dm=0 SYSFONT=True rd.luks=0 rd.md.uuid=ac77fae7:76d15e01:01514632:90362bee KEYTABLE=es rd.md.uuid=d5c73c12:bd42892e:e7dec3f4:514ffebd LANG=en_US.UTF-8 rhgb quiet radeon.pcie_gen2=1 iommu=pt iommu=1 amd_iommu_dump r8169.debug=16 readeon.audio=0 libata.atapi_passthru16=0

The paramater "libata.atapi_passthru16=0" is due to: https://bugzilla.redhat.com/show_bug.cgi?id=906532 ->> "Hard freezes with ASMedia SATA (1b21:0612) (PCIe) and Optical Drive (iHBS112) (WORKAROUND = 'libata.atapi_passthru16=0')"

I don't know if this is related also to:  https://bugzilla.redhat.com/show_bug.cgi?id=858029 --> "growisofs fails to close the FIRST session with SK=5h/INVALID FIELD IN CDB when burning blu-ray BD-R SL"

I filled that  some time ago, i recently tried again to burn BD-R and it is still not possible to trust it to store lots of files since i cannot verify them (and thus delete them from the hdd).

Comment 1 Reartes Guillermo 2013-03-08 19:51:56 UTC

Created attachment 77872 [details]
screenshot of K3b error output

Comment 2 Reartes Guillermo 2013-03-08 19:52:55 UTC

Created attachment 77873 [details]
K3b debug output from the previous screenshot

Comment 3 Reartes Guillermo 2013-03-08 19:54:15 UTC

Created attachment 77874 [details]
dvd+rw-mediainfo of the disc after the "failed" burn session

Comment 4 Bob McGowan 2013-04-07 06:48:07 UTC

I am having a similar, though not quite identical, problem.  All I'm seeing is the message "Write error", at the very end of processing, when k3b is trying to close the session.

Using 'find' on the BlueRay Disk, I can verify that all the files copied without any issues.

I'm attaching the full debug output, and a png image of the "Writing ..." dialog box.

Comment 5 Bob McGowan 2013-04-07 06:50:49 UTC

Created attachment 78697 [details]
Screenshot of k3b and "write" window messages

Comment 6 Bob McGowan 2013-04-07 06:53:35 UTC

Created attachment 78698 [details]
k3b debugging data for prior png image attachment

Comment 7 Andrew Crouthamel 2018-11-12 02:47:01 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Andrew Crouthamel 2018-11-21 04:47:16 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 9 Justin Zobel 2023-01-13 01:36:40 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 10 Bug Janitor Service 2023-01-28 05:08:25 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 11 Bug Janitor Service 2023-02-12 03:50:23 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!