Bug 343810

Summary: Bluray burn fails always write with input output error using K3B or brasero/nautilus
Product: [Applications] k3b Reporter: Robertk <system-messages>
Component: Burning/HardwareAssignee: k3b developers <k3b>
Status: REPORTED ---    
Severity: major CC: michalm, sgies1963, trueg
Priority: NOR    
Version: 2.0.3   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Robertk 2015-02-05 11:31:48 UTC
Refer attached log issue appears in K3B and Brasero/Nautilus where gowisofs reports 
Executing 'builtin_dd if=/dev/fd/0 of=/dev/sr0 obs=32k seek=0'
/dev/sr0: pre-formatting blank BD-RE for 24.8GB...
/dev/sr0: "Current Write Speed" is 2.0x4390KBps.
          0/18498191360 ( 0.0%) @0x, remaining ??:?? RBU 100.0% UBU   0.0%
=== last message repeated 17 times. ===
:-[ WRITE@LBA=0h failed with SK=0h/ASC=00h/ACQ=03h]: Input/output error
:-( write failed: Input/output error

System Intel P4304CR2..... using dual E5-2650 v2 cpus and LG BH14NS40 drive using Verbatim BD-RE 25GB 180 disks.  Burner LG HL-DT-ST - BD-RE BH14NS40

1st try complete 55% of disk then io write error. Thereafter all other tries with new disks only reached 0.18%. After that it became to expensive to burn more disks. Gave up.

Reproducible: Always

Steps to Reproduce:
1. 19 GB tar file to be burned into data project
2. Insert disk
3. Burn disk
4. Except for first time ever when burned 55% thereafter stops at 0.18%
5. Repeatable

Actual Results:  
Per log files:

:-( write failed: Input/output error

Expected Results:  
COmpletion of Bluray burn.

BUrner and K3B works fine with any DVDs

Burner and K3B works fine with any DVDs.

FUrther noticed during 55 % burn, using dolphin, moved another file. This result in the buring file being copied to that location even though I selected a completely different file.
Comment 1 Justin Zobel 2021-03-09 06:28:26 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.