From owner-freebsd-questions@FreeBSD.ORG Thu Jun 17 06:01:24 2010 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 A59A9106566B for ; Thu, 17 Jun 2010 06:01:24 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id 65E8C8FC0C for ; Thu, 17 Jun 2010 06:01:24 +0000 (UTC) Received: from r55.edvax.de (port-92-195-117-232.dynamic.qsc.de [92.195.117.232]) by mx02.qsc.de (Postfix) with ESMTP id D30AA1EB8F; Thu, 17 Jun 2010 08:01:22 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id o5H61ME8002581; Thu, 17 Jun 2010 08:01:22 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 17 Jun 2010 08:01:21 +0200 From: Polytropon To: Mark Terribile Message-Id: <20100617080121.699a9d7c.freebsd@edvax.de> In-Reply-To: <978150.69326.qm@web110311.mail.gq1.yahoo.com> References: <20100615223304.CB69610656ED@hub.freebsd.org> <978150.69326.qm@web110311.mail.gq1.yahoo.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Burning CDs on FreeBSD 7.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 06:01:24 -0000 On Wed, 16 Jun 2010 03:03:02 -0700 (PDT), Mark Terribile wrote: > > Thanks to Jerrymc and Polyoptron. Things are working, sort of. > I'm using the atapicam/cdrecord solution. But when I do a dd > read to verify the write, the read ends on an I/O error rather > than an EOF. (I'm not sure that this problem is new.) There > is a very long delay between dd's report and the program end > (delay on close?) And sometimes the eject command after the > dd locks up and eventually fails. There are plenty of console > messages, including READ_BIG retrying, READ_BIG timed out, > TEST_UNIT_READY freeing zombie taskqueue request, and PREVENT_ALLOW > taskqueue timeout - compiing request directly . I start wondering if this may be due to a defective drive, or wrong cable, or even through DMA incompatibilites... Instead of using dd (have you made sure to use the correct block size?) try using readcd (comes with cdrecord); see "man cdrecord" for details and examples. > This is definitely NOT reliable enough to put into a script > (which would make handling the many file names more reliable). True. > cdrecord reports > ----------------------------------- > scsidev: '4,0,0' > scsibus: 4 target: 0 lun: 0 > SCSI buffer size: 64512 > Track 01: Total bytes read/written: 103874560/103874560 (50720 sectors). > Writing time: 41.290s > Average write speed 20.8x. Try to force a lower value, maybe drive and discs are not compatible. With -speed 8 it should be "slow enough" and "fast enough" for a test. You can use -prcap to find out what the drive tells cdrecord about itself. > I would be grateful for any clues about what is still wrong here. I'd slowly expect a defective drive... -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...