I am running a brand new install of openSUSE 13.1 (KDE). I have run the 1-click update script that adds the packman repository, and updates and codecs for K3B. I am attempting to copy a commercial CD (that I own) using K3B. So far, I have made multiple attempts that have all failed during during the operation of writing to the blank target disc. In each instance, the first several tracks are written, then a failure occurs. The K3B on-screen error display referred to a problem with permissions to write to the device. I’ve tweaked the configuration to use the “burning” group, added my user identity to that group, but it still failed. I re-attempted the operation logged in as root so as to test the validity of the permissions error. The operation failed again, at about the same point, though the error reported on the display was different - it suggested that trying TAO instead of DAO might resolve the problem. In a subsequent try, it didn’t.
I am using disc media from a supply that has worked fine in this (internal) writer for a long time (under different OS’s on this same system).
Any advice for other configuration or update steps I can apply to enable smooth K3B operation copying commercial CD’s would be appreciated. I intend to create copies of CD’s and DVD’s that I own to create primary use media, and to preserve my original purchased discs.
Thank you,
John
PS. Tail end of error log from first burn failure (before I started my own ineffective troubleshooting efforts) is shown below.
Track 08: Total bytes read/written: 26490576/26490576 (11263 sectors).
Starting new track at sector: 90505
Track 09: 0 of 30 MB written.
Track 09: 1 of 30 MB written (fifo 100%) [buf 98%] 11.9x.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 01 64 62 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F1 00 03 00 01 61 E8 0A 00 2B 00 00 0C 00 00 00
Sense Key: 0x3 Medium Error, deferred error, Segment 0
Sense Code: 0x0C Qual 0x00 (write error) Fru 0x0
Sense flags: Blk 90600 (valid)
cmd finished after 5.651s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 1714608 bytes
Writing time: 151.502s
Average write speed 33.8x.
Min drive buffer fill was 97%
Fixating…
Fixating time: 0.001s
/usr/bin/wodim: fifo had 3574 puts and 3384 gets.
/usr/bin/wodim: fifo was 0 times empty and 3314 times full, min fill was 98%.
BURN-Free was never needed.
On 2014-04-11 18:06, Rulls wrote:
>
> I am running a brand new install of openSUSE 13.1 (KDE). I have run the
> 1-click update script that adds the packman repository, and updates and
> codecs for K3B. I am attempting to copy a commercial CD (that I own)
> using K3B. So far, I have made multiple attempts that have all failed
> during during the operation of writing to the blank target disc.
In order to find out if that commercial CD is related to the problem,
you should try to create a plain CD.
> The K3B on-screen error display referred to a problem with
> permissions to write to the device.
…
> PS. Tail end of error log from first burn failure (before I started my
> own ineffective troubleshooting efforts) is shown below.
When pasting computer commands and such, please use a CODE BLOCK, so
that the forum software doesn’t do silly things like converting URLS to
tiny urls or otherwise hide or alter the commands you entered. You get
them by clicking on the ‘#’ button in the forum editor. See photo
> Track 08: Total bytes read/written: 26490576/26490576 (11263 sectors).
> Starting new track at sector: 90505
> Track 09: 0 of 30 MB written.
> Track 09: 1 of 30 MB written (fifo 100%) [buf 98%] 11.9x.
> Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
> CDB: 2A 00 00 01 64 62 00 00 1B 00
I see no evidence of permission error :-?
You could try to use “cdrtools” instead of “wodim”. It is available on
the “multimedia:apps” repo.
If that fails, then perhaps your burner is out of commission. They fail
silently, eventually.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-04-12 00:56, HighBloodSugar wrote:
>
> I don’t know if this helps, but I use growisofs for burning DVDs. You
> may need to install it first, I’m not sure.
growisofs is actually a frontend. It uses mkisofs and cdrtools; the
later is often replaced with wodim (in openSUSE, the current default is
“wodim”).
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I the past, when I burned a dual layer video DVD, wodim burned all of one layer and part of the other layer. When played in my stand-alone DVD player, it took over 1 minute to load the disc. Then I tried growisofs, and it split the layers evenly, and that disc only took 10 seconds to load. I’ve always set K3B to use growisofs for burning video DVDs since then. No idea if this is still an issue with wodim.
On 2014-04-12 07:36, HighBloodSugar wrote:
>
> robin_listas;2636482 Wrote:
>>
>> growisofs is actually a frontend. It uses mkisofs and cdrtools; the
>> later is often replaced with wodim (in openSUSE, the current default is
>> “wodim”).
>>
>
> I the past, when I burned a dual layer video DVD, wodim burned all of
> one layer and part of the other layer. When played in my stand-alone DVD
> player, it took over 1 minute to load the disc. Then I tried growisofs,
> and it split the layers evenly, and that disc only took 10 seconds to
> load. I’ve always set K3B to use growisofs for burning video DVDs since
> then. No idea if this is still an issue with wodim.
All those tools use wodim to do the actual writing. What changes are the
options used.
You can check for yourself when you burn something with “growisofs”: do
a full process listing, with “ps afxu”, for instance, and you should see
what it uses for the writing.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I see nothing there referring to wodim. For genisoimage it says “<defunct>”… this is burning a previously created ISO image of a concert DVD, so I’m not sure what genisoimage is for. I thought that only generated the ISO image. Am I right about that? Either way, it works for me, that’s all that really matters.
On 2014-04-15 09:46, HighBloodSugar wrote:
>
> I just realized the OP is trying to burn CDs, not DVDs - my bad…
> growisofs only does DVDs, so I withdraw my suggestion.
I have used growisofs in the past to burn both CDs and DVDs, IIRC.
For some reason I don’t remember groisofs stopped working on my
computer, and I switched to wodim. Then I also have a note that wodim
failed with rewriteable media…
Thus my suggestion to replace wodim with cdrecord.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)