Christian Herzyk wrote: > Am Dienstag 21 Juni 2005 21:30 schrieb Zac Medico: > >>Christian Herzyk wrote: >> >>>Hello all, >>> >>>I cannot write CDs anymore. >>>The only thing i changed lately was an upgrade to cdrtools-2.01-r3 from >>>r2 some days ago. Now nearly all attempts to burn an audio CD end with an >>>error. After some of the mistakes (using k3b) I searched the forum and >>>found some postings on problems writing CDs as normal user. >>>So I tried the ck-sources (2.6.11_p10) as these were said to have a >>>patch, no change. The last thing I tried was using cdrecord as root (both >>>with the ck-sources and the gentoo-sources-2.6.11), but I still get >>>errors like the following: >>> >>>Track 01: Total bytes read/written: 45236016/45236016 (19233 sectors). >>>Track 02: Total bytes read/written: 57692208/57692208 (24529 sectors). >>>cdrecord: Success. write_g1: scsi sendcmd: no error >>>CDB: 2A 00 00 00 DD CF 00 00 1B 00 >>>status: 0x2 (CHECK CONDITION) >>>Sense Bytes: 70 00 03 00 00 00 00 10 20 31 00 80 02 00 00 00 >>>Sense Key: 0x3 Medium Error, Segment 0 >>>Sense Code: 0x02 Qual 0x00 (no seek complete) Fru 0x0 >>>Sense flags: Blk 0 (not valid) >>>resid: 63504 >>>cmd finished after 5.457s timeout 40s >>>write track data: error after 29910384 bytes >>>cdrecord: A write error occured. >>>cdrecord: Please properly read the error message above. >>>cdrecord: Success. close track/session: scsi sendcmd: no error >>>CDB: 5B 00 02 00 00 00 00 00 00 00 >>>status: 0x2 (CHECK CONDITION) >>>Sense Bytes: 70 00 03 00 00 00 00 10 20 3B 00 80 02 00 00 00 >>>Sense Key: 0x3 Medium Error, Segment 0 >>>Sense Code: 0x02 Qual 0x00 (no seek complete) Fru 0x0 >>>Sense flags: Blk 0 (not valid) >>>cmd finished after 4.906s timeout 480s >>>cmd finished after 4.906s timeout 480s >>>cdrecord: Cannot fixate disk. >>> >>>I even tried different media types, all of them were used before without >>>any problems (I think I lost only 2 CD-Rs in over 2 years) so I would say >>>it is not any bad media. >>>What makes me wonder is that once I could finish writing a CD-R and once >>>with an CD-RW (using k3b as user) the other ~8 tries were failures. >>> >>>Any hints what could be the problems? >>> >>>Thanks a lot >>> >>>Christian >> >>Have you reverted back to cdrtools-2.01-r2? I'm currently using >>cdrtools-2.01.01_alpha01-r2 with no problems. >> >>Zac > > > Hi Zac, > > as cdrtools-2.01-r2 is no longer in portage I tried upgrading to > 2.01.01_alpha01-r2. > I still get the same error: > Track 08: 1 of 50 MB written (fifo 100%) [buf 89%] 24.5x.cdrecord: > Success. write_g1: scsi sendcmd: no error > CDB: 2A 00 00 02 4C 7F 00 00 1B 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 03 00 00 00 00 10 20 3B 00 80 02 00 00 00 > Sense Key: 0x3 Medium Error, Segment 0 > Sense Code: 0x02 Qual 0x00 (no seek complete) Fru 0x0 > Sense flags: Blk 0 (not valid) > resid: 63504 > cmd finished after 5.316s timeout 40s > write track data: error after 1143072 bytes > cdrecord: A write error occured. > > I get the same error after downgrading to 2.01-r1. > > Any other hints? > > Christian
Have you reverted back to the old kernel? If you have FEATURES=buildpkg set in make.conf then you may have a backup cdrtools binary package. Otherwise, I recommend to make a backup with quickpkg before your upgrade something. I would experiment with cdrw discs until this is resolved. I recall getting a similar error when I attempted to overburn a 650MB cdrw. Sometimes a full blank is necessary with cdrw/dvdrw discs. Zac Zac -- gentoo-user@gentoo.org mailing list
