From owner-freebsd-questions@FreeBSD.ORG Fri Dec 7 20:28:15 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87BF316A418 for ; Fri, 7 Dec 2007 20:28:15 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp3.utdallas.edu (smtp3.utdallas.edu [129.110.10.49]) by mx1.freebsd.org (Postfix) with ESMTP id 69C6213C46E for ; Fri, 7 Dec 2007 20:28:15 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTP id E03D865505 for ; Fri, 7 Dec 2007 14:28:14 -0600 (CST) Date: Fri, 07 Dec 2007 14:28:14 -0600 From: Paul Schmehl To: FreeBSD Questions Message-ID: <8F7529877F79C5AA816F106A@utd59514.utdallas.edu> In-Reply-To: <20071206191359.S2276@wojtek.tensor.gdynia.pl> References: <00F787E8C720E8E8327BD5A1@utd59514.utdallas.edu> <20071206191359.S2276@wojtek.tensor.gdynia.pl> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: CD/DVD writer no longer works X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2007 20:28:15 -0000 --On Thursday, December 06, 2007 19:14:51 +0100 Wojciech Puchar wrote: >> /home/pauls/Downloads/FreeBSD/6.2-RELEASE-amd64-disc1.iso fixate >> burncd: ioctl(CDRIOCWRITESPEED): Input/output error >> root@utd59514# mount /dev/acd >> acd0 acd1 >> root@utd59514# mount /dev/acd1 /mnt/cdrom/ >> mount: /dev/acd1: Input/output error > > mount_cd9660 - unless you use FFS on CD/DVD. >> 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 >> Sense flags: Blk 0 (not valid) >> cmd finished after 0.000s timeout 40s >> cdrecord: No disk / Wrong disk! >> > > looks like your device is broken - reports no disk Looks like this is it. To verify I booted into Windows (which I almost never do), and the drive doesn't work - it can't even read a disk. So it's an apparent hardware failure. -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/