| Author |
Message |
|
|
Post subject: [k3b]: can't burn CDR's
 Posted: May 04, 2008 - 06:27 AM
|
|
Joined: Nov 17, 2007
Posts: 68
Location: http://www.kronberg.de/
Status: Offline
|
|
Hi,
strange thing:
I can't burn CDR's with k3b anymore.
I don't burn that much.
Month ago I haven't had any problems.
Some days ago I've tried to copy a CD.
No success.
In google I've found that cdrecord might be the problem.
And I've installed it.
Today I burned an ISO to DVD with no problems.
But ISO to CD doesn't work.
Thanks in advance.
Here's the error message (last part of it):
Code:
...
Waiting for reader process to fill input buffer ... input buffer ready.
Performing OPC...
Sending CUE sheet...
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 FF FF FF 6A 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 00 00 00 0E 00 00 00 00 09 00 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x09 Qual 0x00 (track following error) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 19.108s timeout 200s
Writing pregap for track 1 at -150
write track pad data: error after 0 bytes
BFree: 1088 K BSize: 1088 K
Starting new track at sector: 0
Track 01: 0 of 597 MB written.
Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error
CDB: 2A 00 00 00 00 00 00 00 1F 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 05 00 00 00 00 0E 00 00 00 00 24 00 00 00
Sense Key: 0x5 Illegal Request, Segment 0
Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.002s timeout 200s
/usr/bin/wodim: A write error occured.
/usr/bin/wodim: Please properly read the error message above.
write track data: error after 0 bytes
Writing time: 24.140s
Average write speed 169.1x.
Fixating...
Fixating time: 0.002s
/usr/bin/wodim: fifo had 192 puts and 1 gets.
/usr/bin/wodim: fifo was 0 times empty and 0 times full, min fill was 100%.
cdrecord command:
-----------------------
/usr/bin/wodim -v gracetime=2 dev=/dev/scd0 speed=16 -dao driveropts=burnfree -eject -data -tsize=305918s -
|
|
|
| |
|
|
|
 |
|
|
|
Post subject: [k3b]: can
Posted: May 04, 2008 - 06:32 AM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 2866
Location: berlin
Status: Offline
|
|
|
|
|
|
|
|
|
Post subject:
Posted: May 04, 2008 - 07:44 AM
|
|
Joined: Nov 17, 2007
Posts: 68
Location: http://www.kronberg.de/
Status: Offline
|
|
Thnx for the help.
cdrdao also stops with an error message.
ATM I think installing "zattoo" (not an official package) has broken my system.
[edit]
"zattoo" seems not to be the reason.
I've just installed "nyx" but the problem is still there.
Will try to install "eros" again.
[/edit]
[edit]
No chance.
seems to be really a hardware error.
The drive is only 6 months old.
And I've only burned less than 10 CD's / DVD's.
[/edit] |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: May 04, 2008 - 05:04 PM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 2866
Location: berlin
Status: Offline
|
|
return it to the store.
greetz
devil |
_________________
>>we are sidux - resistance is futile - you will be assimilated<<
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: May 04, 2008 - 05:25 PM
|
|
Joined: Dec 06, 2007
Posts: 309
Location: New Delhi
Status: Offline
|
|
I had read somewhere (in some forum maybe) that most CD burning problems arise out of the GUI, it is best to use text based commands.
I also feel that with dropping prices of drives, the burning is getting poorer. My 3 year old CD writer, after burning so many CDs, burns without problems while the sparingly used DVD writer on laptop failed to burn a single sidux iso properly from Windows, sidux, or Ubuntu to CD or DVD. had to install using "fromiso".
Maybe the media to getting worse day by day. |
_________________
http://linux.ixcodes.com
In a lunatic asylum, everyone thinks that he is the doctor.
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: May 05, 2008 - 12:03 AM
|
|
Joined: Dec 01, 2007
Posts: 203
Location: Enschede NL
Status: Offline
|
|
| My burner, an Asus, is a bit picky when it comes to brand of disks. Imation and Philips are allright, Maxwell burned but didn't "close" or "fix". Of course, the names on the outside say nothing about the actual manufacturer of the disk but if you switched brands recently then maybe that's the issue. |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: May 05, 2008 - 04:35 AM
|
|
Team Member
Joined: Nov 24, 2006
Posts: 2866
Location: berlin
Status: Offline
|
|
|
|
|
|
|
|
