[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: faulty drive?



On Wed, Aug 06, 2003 at 03:50:47AM -0400, Roy Katz wrote:
> Hello,
> 
> I've been having some difficulty reading audio cd's with cdrdao and
> writing them with cdrecord. I have a TDK VeloCD 40x??x48 burner[2] with
> firmware revision "lt00" (2000 maybe?) and set in lilo.conf to
> "hda=ide-scsi", tweaked with hdparm at startup[1].
> 
> With cdrdao, it causes my drive to make a buzzing or grinding sound (as if
> the spindle motor is scraping against something).  This happened on one
> disc (but not on another);  furthermore, I tried reading the disc with
> cdparanoia -B and it didn't cause those noises.  I used the generic-mmc
> driver.  BTW, cdrdao reads *very very very* slowly.
Try another reading driver, such as plextor or plextor-scan.

...
> BURN-Free is OFF.
> Performing OPC...
> Sending CUE sheet...
> Writing pregap for track 1 at -150
> cdrecord.mmap: Input/output error. write_g1: scsi sendcmd: no error
> CDB:  2A 00 FF FF FF 6A 00 00 1B 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.218s timeout 200s
> write track pad data: error after 0 bytes
> BFree: 3720 K BSize: 3720 K
> Starting new track at sector: 0
> Track 01:    0 of  294 MB written.cdrecord.mmap: Input/output error. write_g1: scsi sendcmd: no error
> CDB:  2A 00 00 00 00 00 00 00 1B 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
> Sense Key: 0x3 Medium Error, Segment 0
> Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.015s timeout 200s
Try another CDR brand.

-- 
        Giuseppe "Cowo" Corbelli ~\/~ My software: http://cowo.yoda2000.net
-<! Le donne e le salsicce sono la stessa cosa: pelle fuori e maiale dentro !>-



Reply to: