https://bugs.kde.org/show_bug.cgi?id=380067
--- Comment #19 from Thomas Schmitt <scdbac...@gmx.net> --- Hi, > :-[ WRITE@LBA=596780h failed with SK=4h/ASC=03h/ACQ=01h]: Input/output error This is not good news. SK=4h means "Hardware error". SPC-3 table 27: "Indicates that the device server detected a non-recoverable hardware failure (e.g., controller failure, device failure, or parity error) while performing the command or during a self test. ASC=03h/ACQ=01h is listed in SPC-3 as "NO WRITE CURRENT". No idea what this shall mean. According to http://www.t10.org/lists/asc-num.htm#ASC_03 it is supposed to be emitted by SSC tapes, not by MMC optical drives. I'd say it indicates a period of drive unconsciousness. This would be a situation after which one could get the wake-up message from the first failure in this bug report: > > :-[ FLUSH CACHE failed with SK=6h/NOT READY TO READY CHANGE, MEDIUM MAY > > HAVE CHANGED]: Input/output error This is surely not K3B's fault and very probably not the fault of growisofs. It rather looks like the drive hates the medium and gets into strange states while gnawing on it. It does not happen always. I assume that the shorter burn runs without Defect Management improve the chance to get done before madness strikes. But the situation is clearly unstable. The only proposal i have is to try other media or a different drive. Have a nice day :) Thomas -- You are receiving this mail because: You are watching all bug changes.