Reply to topic

Takes forever to close

steveveltkamp
Registered Member
Posts
1
Karma
0

Takes forever to close

Sat Nov 09, 2013 6:59 pm
OK, not forever, but 221 seconds. Only 144 seconds to write the data, 221 to fixate/close the disk. I'm burning a data CD, and this behavior has been universal through many burns. It complains about being unable to flush cache. Any ideas on how to fix or where this cache is? After the wait, K3B reports success and ejects the disk, so the CD appears to burn successfully .

Here is k3b log:

[cdrecord] Writing time: 144.225s
[cdrecord] Average write speed 12.3x.
[cdrecord] Min drive buffer fill was 100%
[cdrecord] Fixating...
[cdrecord] Errno: 5 (Input/output error), flush cache scsi sendcmd: no error
[cdrecord] CDB: 35 00 00 00 00 00 00 00 00 00
[cdrecord] status: 0x2 (CHECK CONDITION)
[cdrecord] Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
[cdrecord] Sense Key: 0x0 No Additional Sense, Segment 11
[cdrecord] Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
[cdrecord] Sense flags: Blk 0 (not valid)
[cdrecord] cmd finished after 201.635s timeout 200s
[cdrecord] Trouble flushing the cache
[cdrecord] Fixating time: 221.935s
[cdrecord] /usr/bin/wodim: fifo had 4079 puts and 4079 gets.
[cdrecord] /usr/bin/wodim: fifo was 0 times empty and 3865 times full, min fill was 93%.
[cdrecord] BURN-Free was never needed.
User avatar bcooksley
Administrator
Posts
18607
Karma
83
OS

Re: Takes forever to close

Sun Nov 10, 2013 7:46 am
Code: Select all
[cdrecord] Fixating...
[cdrecord] Errno: 5 (Input/output error), flush cache scsi sendcmd: no error
[cdrecord] CDB: 35 00 00 00 00 00 00 00 00 00
[cdrecord] status: 0x2 (CHECK CONDITION)
[cdrecord] Sense Bytes: 72 0B 00 00 00 00 00 0E 09 0C 00 00 00 03 00 00
[cdrecord] Sense Key: 0x0 No Additional Sense, Segment 11
[cdrecord] Sense Code: 0x00 Qual 0x03 (setmark detected) Fru 0x0
[cdrecord] Sense flags: Blk 0 (not valid)
[cdrecord] cmd finished after 201.635s timeout 200s


This indicates that your optical drive is failing to perform a command given by cdrecord - at which point it stalls completely, until a timeout forces it to continue. There is nothing K3b can do about this i'm afraid - you'll need to update to a newer version of cdrecord, or report the bug upstream to them so they can investigate / fix the issue.


System Settings and Device Actions KCM maintainer
Image

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Exabot [Bot], Google [Bot], google01103, Hans, koriun, La Ninje, MSNbot Media, north, odysseus-art, pesto, SecretCode, Sentynel, Yahoo [Bot], z-uo