| Summary: | K3b reports failure on BluRay burn, disc appranetly usable - LG BH10LS30 | ||
|---|---|---|---|
| Product: | [Applications] k3b | Reporter: | Victor T <vttrumper> |
| Component: | Data Project | Assignee: | k3b developers <k3b> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | cory.gugler, goplayer4, gregor.rosenauer, Kicer86, mfraz74+kde, ml-kdebugs, regi.hops, rjwgnr27, rtguille, trueg |
| Priority: | NOR | ||
| Version: | 2.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Bzip'd log file saved on "unsuccessful" burn
Debug output of burn kDebug console output k3b debug output (growisofs output) k3b snapshot of a previous bd-r "failure" k3b snapshot of another bd-r "failure" |
||
|
Description
Victor T
2010-11-22 23:58:45 UTC
Created attachment 53645 [details]
Bzip'd log file saved on "unsuccessful" burn
Same error here with an LG burner (WH10LS30). Data on bd-r is readable and seems to be complete. Also noticed after inserting K3b reads this as the medium: Appendable Data Error Appendable Error medium Medium Type: BD-R Sequential Pseudo Overwrite (SRM+POW) Capacity: 317718:35:11 min (2.7 TiB) Used Capacity: 317718:35:11 min (2.7 TiB) Remaining: 00:00:00 min (0 B) Rewritable: no Appendable: yes Empty: no Layers: 1 Sessions: 0 Supported writing speeds: 2.0x (8991 KB/s) 4.0x (17982 KB/s) 6.0x (26973 KB/s) 8.0x (35964 KB/s) Capacity seems to vary, the above disc has 21.9 GB written to it. can confirm, same here with k3b 2.0.2, Linux (x86_64) release 2.6.38-CHAKRA, LG GGW-H20L (SATA). Burnt 2 discs (25GB BD-RE, one Sony, one Verbatim), one even overburned (though the option was *not* activated and k3b didn't ask for confirmation), both discs are OK, compared contents to original files OK. Media info: Typ: BD-R sequenziell Pseudo-Überschreiben (SRM+POW) Kapazität: 2686:17:45 Minuten (23,1 GiB) Verwendete Kapazität: 2493:02:06 Minuten (21,4 GiB) Verbleibend: 193:15:39 Minuten (1,7 GiB) Wiederbeschreibbar: nein Fortsetzbar: ja Leer: nein Schichten: 1 Sitzungen: 0 Unterstützte Brenngeschwindigkeiten: 2.0x (8991 KB/s) 4.0x (17982 KB/s) 6.0x (26973 KB/s) ISO-9660-Dateisysteminformationen System-ID: LINUX Datenträger-ID: Pix200907_201005 Datenträgersatz-ID: - Veröffentlicher-ID: - Vorbereiter-ID: - Programm-ID: K3B THE CD KREATOR (C) 1998-2010 SEBASTIAN TRUEG AND MICHAL MALEK Datenträgergröße: 21,4 GiB (2 048 B * 11 218 635 Blöcke = 22 975 764 480 B) Same here with on different, the disc is corrupt! DEMSG always return that K3B is trying to access beyond the limit of the disc, no matter if I try to burn 10GB, 20 GB or the maximum. MD5SUM report that the last file on the disc is corrupt. System: openSUSE 11.4 64 bit, KDE4.6.3, K3B 2.0.2 BluRay: LG BH08LS Are there any news to this bug? Tried on this config: Distribution: openSUSE 12.1 (x86_64) KDE: 4.8.00 (4.8.0 "release 2") K3B: 2.0.2-13.8 BD-Disks are still corrupt. Cheers Regi I see this on V2.0.2 with Liteon iHBS112 BD writer. Gets thorough 100% of write. So far only tried Verbatim 25GB 4x media. Seems to be while closing the session, it then reports "Write Error". The media is readable, and doing a sha1sum between sources and BD copy, sums match, so it appears the burn was successful. So seems to be something in the close session, or transition to verify (I have very enabled in the burn options). Saved the debug log, which I'll attach. Created attachment 68966 [details]
Debug output of burn
Log file from the burn operation "Save" from show debug dialog.
Created attachment 68972 [details]
kDebug console output
Enabled k3b debugs (kdebugdialog) and ran k3b from shell. Captured output and filtered out KDirListerCache; they overwhelmed the log file, and are likely unrelated.
After some digging and experimenting I have found the following which I hope may of help to other people in a similar predicament... Problem caused by cdrecord (http://cdrecord.berlios.de/) licensing issues and past feuds which result in cdrkit (http://www.cdrkit.org/) being installed on system (Debian, Ubuntu, Suse, etc) and used in place of actual cdrecord binaries. cdrkit binaries based on old and buggy code. k3b patched to detect cdrkit installation and use growisofs instead - https://git.reviewboard.kde.org/r/101208/. In referenced bugs growisofs seems to have an issue closing the BD-R session resulting in the last file burnt to the disc being faulty and the disc left open ("Appendable: yes" in k3b after burning). Solution is to install cdrecord. Removal of cdrkit isn't required as k3b will detect cdrecord from default install path of /opt/schily/. For installation instructions on Debian-based O/S see: http://ubuntuforums.org/showpost.php?p=5552555&postcount=5 Note that you can stop at 'sudo make install' in the above and k3b will find cdrecord, no adjusting with symlinks in /usr/bin is required. Apparently as detailed in http://forum.kde.org/viewtopic.php?f=153&t=85895&start=15#p165603 - setting k3b to "No Multisession" will cause it to use cdrecord instead of growisofs. Have tested the above on Debian Wheezy. Good luck - Ben Whorwood (mube.co.uk) === Issue referenced in bugs... http://forum.kde.org/viewtopic.php?f=153&t=85895&sid=f3d37339bce3fcc5d907daea285e98a6&start=15 https://bugs.kde.org/show_bug.cgi?id=281818 https://bugs.kde.org/show_bug.cgi?id=244549 https://bugs.kde.org/show_bug.cgi?id=257652 === Solution based on... https://bugzilla.novell.com/show_bug.cgi?id=656502 https://git.reviewboard.kde.org/r/101208/ http://ubuntuforums.org/showthread.php?t=851707 I burned some BD-R, and K3b says the burn failed. I don't see any error in the debug output. Also, i burned a big file (17gb) to a BD-R. It failed (at least to K3b) as usual. Then i compared the sha256sum of the written file to the one on my hard disk and they do mach. So the file was correctly written. Is growisofs actually failing or it is K3b that does not handle something and just reports a false failure? Fedora 17, writer: iHBS112 K3b: 2.0.2, KDE: 4.8.5 Created attachment 73966 [details]
k3b debug output (growisofs output)
Created attachment 73967 [details]
k3b snapshot of a previous bd-r "failure"
Created attachment 73968 [details]
k3b snapshot of another bd-r "failure"
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! 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! 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! 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! 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! |