Michael,
RedHat distributions have a horrible little daemon called
"magicdev" that periodically polls CDROMs with a TEST UNIT
READY command. I have a Yamaha 4416S and if it receives
a poll while it is trying to write a CDR it locks up. My machine
needs to be power cycled to clear that lockup.

Now if that cdwriter had a half decent SCSI target implementation
then it wouldn't lock up like that. However ...

IMO your solution is to either:
  - run cdrecord from the command line
  - kill magicdev ["rpm -e magicdev" is a permanent solution]

The downside of not having magicdev is that CDROMs will no 
longer be auto-mounted when you insert them in the drive.

YMMV.


All upper level drivers in the Linux SCSI subsystem now
correctly increment a per device "access_count" on open()
calls [and decrement on close()]. So a program like
magicdev could check if there was an existing open() on
a SCSI cdwriter (e.g. by cdrecord) and if so leave the 
!@#$ thing alone.

Doug Gilbert

Michael White wrote:
> 
> Hi all,
> 
> I have a problem with cdrecord.  Specifically, it will not let me write or
> erase CDs (CD RW, actually).  My system:
> 
> Redhat 7.1
> cdrecord 1.11-a12 (latest that I could find - earlier versions also don't
>                                work on my system)
> HP Omnibook 800 CT (built in SCSI - Symbios logic 53C810 SCSI controller)
> 166 MHz Pentium MMX
> Yamaha 6416 CD RW (SCSI ID 0/0)
> 
> Here's the output.  The output is the same whether I'm trying to blank or
> trying to write.
> ------------------------------------------------
> [root@localhost bin]# cdrecord blank=all dev=0,0,0
> Cdrecord 1.11a12 (i586-pc-linux-gnu) Copyright (C) 1995-2001 J�rg Schilling
> scsidev: '0,0,0'
> scsibus: 0 target: 0 lun: 0
> Linux sg driver version: 3.1.17
> Using libscg version 'schily-0.5'
> Device type    : Removable CD-ROM
> Version        : 2
> Response Format: 2
> Capabilities   : SYNC
> Vendor_info    : 'YAMAHA  '
> Identifikation : 'CRW6416S        '
> Revision       : '1.0c'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R driver (mmc_cdr).
> Driver flags   : SWABAUDIO
> Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R96R
> Starting to write CD/DVD at speed 2 in write mode for single session.
> Last chance to quit, starting real write in 0 seconds. Operation starts.
> cdrecord: OPC failed.
> cdrecord: Input/output error. blank unit: scsi sendcmd: no error
> CDB:  A1 00 00 00 00 00 00 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
> Sense Key: 0x2 Not Ready, Segment 0
> Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru
> 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 13.374s timeout 9600s
> cdrecord: Cannot blank disk, aborting.
> cdrecord: Input/output error. prevent/allow medium removal: scsi sendcmd: no
> error
> CDB:  1E 00 00 00 00 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 04 01 00 00
> Sense Key: 0x2 Not Ready, Segment 0
> Sense Code: 0x04 Qual 0x01 (logical unit is in process of becoming ready) Fru
> 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.011s timeout 40s
> [root@localhost bin]#
> ------------------------------------------------
> 
> >From an LED and device perspective, it looks like someone has yanked
> the reset line on the SCSI bus several seconds after "Operation starts".
> All devices seem to reset.  I have a SCSI tape drive on the same SCSI bus,
> and it also acts like it has just been reset whenever this failure occurs
> (i.e. stops what it's doing and re-positions the tape).
> 
> Note that I can read from the CD recorder fine, and I have recorded using
> this CD recorder on a different system/OS (CD Writer on my old Atari Falcon).
> In addition, I have no problem accessing (reading and writing) the tape drive,
> so I don't think it's the SCSI bus or cables (which have all worked fine
> before).
> 
> Any help would be appreciated.  Thanks in advance.
> --
> Michael White
> [EMAIL PROTECTED]
> 
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to