Date: Mon, 12 Jul 1999 15:05:17 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) Subject: cdrecord Problems Message-ID: <199907121905.PAA24759@cc942873-a.ewndsr1.nj.home.com>
next in thread | raw e-mail | index | archive | help
I think I just trashed two blank CDs. This system when it was 3.1 used to write CDROMs w/o a hitch. I went to 3.2, had a temporary problem solved by upgrading cdrecord, and then wrote CDs again. Now, things just do not make sense. The SCSI CD-R/W seems to be hanging up alot. I started this burn and it _looked_ like all the data was written, but then the process kvetched when it got to fixating. Here is what I got for console output during the process, starting with the command line uesd, pc222# cdrecord -speed=2 -v -data dev=/dev/cd0:0,2,0 /cdimage/goes_cd.19990712 cdrecord: No such file or directory. WARNING: RR-scheduler not available, disabling. Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '/dev/cd0:0,2,0' devname: '/dev/cd0' scsibus: 0 target: 2 lun: 0 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : Vendor_info : 'HP ' Identifikation : 'CD-Writer 6020 ' Revision : '1.07' Device seems to be: Philips CDD-2600. Using driver for Philips CDD-522 (philips_cdd522). Driver flags : FIFO size : 4194304 = 4096 KB cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, disabling. Track 01: data 544 MB Total size: 625 MB (61:56.44) = 278733 sectors Lout start: 625 MB (61:58/33) = 278733 sectors Current Secsize: 2048 ATIP info from disk: Is not unrestricted Disk application code: 0 ATIP start of lead in: -11080 (97:34/20) ATIP start of lead out: 335100 (74:30/00) Disk type: Cyanine, AZO or similar Manuf. index: 11 Manufacturer: Mitsubishi Chemical Corporation Blocks total: 335100 Blocks current: 335100 Blocks remaining: 56367 RBlocks total: 342460 RBlocks current: 342460 RBlocks remaining: 63727 Starting to write CD/DVD at speed 2 in write mode for single session. Last chance to quit, starting real write in 1 seconds. Waiting for reader process to fill input-buffer ... input-buffer ready. Starting new track at sector: 0 Track 01: 544 of 544 MB written (fifo 100%).cdrecord: Input/output error. flush cache: scsi sendcmd: retryable error status: 0x8 (BUSY) Track 01: Total bytes read/written: 570841088/570841088 (278731 sectors). CDB: 35 00 00 00 00 00 00 00 00 00 cmd finished after 120.004s timeout 120s Writing time: 1989.327s Fixating... cdrecord: Input/output error. fixation: scsi sendcmd: retryable error status: 0x8 (BUSY) CDB: E9 00 00 00 00 00 00 00 01 00 cmd finished after 0.000s timeout 480s cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: retryable error status: 0x8 (BUSY) cdrecord: fifo had 8992 puts and 8992 gets. cdrecord: fifo was 0 times empty and 8927 times full, min fill was 98%. Fixating time: 0.000s CDB: 1E 00 00 00 00 00 cmd finished after 0.000s timeout 40s A -dummy write seems to go fine, but a real write might die before it really gets going or way into the burn like this one did. Afterwards, the CD-R/W is completely hung up. If I try another cdrecord command, the output suggests I powercycle the CDD. However, sending a reset with camcontrol seems to clear it up... until the next failed command. Can anyone interpret that output? I wonder if my CDD might be sick, or is it a software issue? Thanks for any help. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907121905.PAA24759>