On Wed, Jan 23, 2002 at 23:24:16 +0100, Thierry Herbelot wrote: > Hello, > > I've got an SCSI CD-Writer, which only gives errors when I try to use > cd-record (see full log at the end of the message) > > As the problem is identical on a fresh 4.4-Rel (with cd-record installed > from the CD as a binary package) and a recently updated 4.5-RC, there is > strong suspicion the drive itself is dying. > > can anyone decode the ASCII dump of the SCSI error message ? > > (I've also cleaned the optics, in case there was too much dust, but no > joy) > > time to buy a new Yamaha 2100S ? > > TfH > > # cdrecord -v dev=0,2,0 speed=1 blank=fast
The error below is an illegal/invalid opcode. It doesn't really indicate a failing drive, as far as I can tell. > cdrecord: Drive needs to reload the media to return to proper status. > ATIP start of lead out: 1166730 (03:18/30) > Blocks total: 1166730 Blocks current: 1166730 Blocks remaining: 1166880 > Starting to write CD/DVD at speed 1 in write mode for single session. > Last chance to quit, starting real write in 0 seconds. Operation starts. > Blanking PMA, TOC, pregap > cdrecord: Input/output error. blank unit: scsi sendcmd: retryable error > CDB: A1 01 00 00 00 00 00 00 00 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: F0 00 05 00 00 00 00 28 00 00 04 D8 20 00 00 80 00 00 01 19 > 04 00 00 00 80 01 00 00 00 00 00 00 > Sense Key: 0x5 Illegal Request, Segment 0 > Sense Code: 0x20 Qual 0x00 (invalid command operation code) Fru 0x0 > Sense flags: Blk 0 (valid) error refers to data part, bit ptr 0 (not > valid) field ptr 0 > cmd finished after 5.618s timeout 9600s > cdrecord: Cannot blank disk, aborting. I would suggest either not specifying the speed, or specify a speed that both the media and the drive can handle. Some media have a minimum speed. If that doesn't fix it, send mail describing the problem to [EMAIL PROTECTED], or Joerg Schilling directly -- [EMAIL PROTECTED] Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
