did you try to reconfigure k3b with the new drive... that is the configuration option when is asks for the root password, not the user settings? also check dma/udma settings for the new drive maybe they are set wrong, that is they are on and the drive does not support them. in which case i will consider returning the drive and getting a descent one that supports udma ...
cheers Szemir On December 20, 2009 01:00:49 am Shawn wrote: > I'm on my second new CD drive in a month. The first was failing to burn > useful CDs - could not do bootable CDs, data-cds were hit and miss if > they worked, etc. > > Now that I have a brand new drive, K3B is having nothing but problems > writing. As near as I can tell it is getting a hardware error when > writing. But this is a BRAND NEW drive just bought today, which seems > to function fine other than burning. > > I had problems with permissions initally - K3B complained that it didn't > have permission to run cdrecord (which is now 'wodim' in *buntu due to > some licensing issues). I ripped out K3B, and the related tools, then > reinstalled them until I was able to at least start K3B without > warnings/errors. But I think the original problem may be that the > system now has two different drives set up, maybe.... > > When I try to burn a CD (with Brasero or K3B) the cue sheet is "sent", > but then when it tries to write the data it fails immediately and the > debug logs give me this: > > Errno: 5 (Input/output error), write_g1 scsi sendcmd: no error > CDB: 2A 00 00 00 2C AF 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 04 00 00 00 00 0A 00 00 00 00 08 03 00 80 > Sense Key: 0x4 Hardware Error, Segment 0 > Sense Code: 0x08 Qual 0x03 (logical unit communication crc error > (ultra-dma/32)) Fru 0x0 > Sense flags: Blk 0 (not valid) actual retry count 0 > cmd finished after 0.959s timeout 200s > /usr/bin/wodim: A write error occured. > /usr/bin/wodim: Please properly read the error message above. > write track data: error after 23427072 bytes > > Is this something worth trying to fix? Or should I return the drive and > go with a different brand (new drive is a Samsung) > > Shawn > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
