From owner-freebsd-scsi Wed Feb 6 11:50:10 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 3B34F37B41A for ; Wed, 6 Feb 2002 11:50:06 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA04594 for freebsd-scsi@freebsd.org; Wed, 6 Feb 2002 20:50:05 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g16JhS424008; Wed, 6 Feb 2002 20:43:28 +0100 (MET) (envelope-from j) Date: Wed, 6 Feb 2002 20:43:28 +0100 (MET) Message-Id: <200202061943.g16JhS424008@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Problem reading (and writing ...) Rewriteable CDs X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org arno@heho.snv.jussieu.fr wrote: > su-2.05a# mount_cd9660 -v /dev/cd1c /cdrom > could not determine starting sector, using very first session > mount_cd9660: /dev/cd1c: Device not configured Hmm, are there any syslog messages about this? > cdrecord: Input/output error. test unit ready: scsi sendcmd: retryable error > CDB: 00 00 00 00 00 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Sense Key: 0x2 Not Ready, Segment 0 > Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 The drive probably "went off for lunch" after some other command. You need a full traceback of the SCSI commands sent to the drive, plus a SCSI reference manual for it. I once had a similar problem with my old Plasmon writer, which then needed a patch (patch-ai in cdrtools) in order to prevent cdrecord from issuing something to the drive the drive didn't understand. The other option is that whatever already caused the above read error, has also caused the cdrecord "not ready" problem later. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message