From owner-freebsd-questions@FreeBSD.ORG Thu Mar 18 08:20:07 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7393616A4CF for ; Thu, 18 Mar 2004 08:20:07 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6273E43D2F for ; Thu, 18 Mar 2004 08:20:07 -0800 (PST) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc13) with ESMTP id <20040318162005015006212ge>; Thu, 18 Mar 2004 16:20:05 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 2B2ACF; Thu, 18 Mar 2004 11:20:05 -0500 (EST) Sender: lowell@be-well.ilk.org To: "Chris" References: <200403180935440470.461A17AA@coolarrow.com> From: Lowell Gilbert Date: 18 Mar 2004 11:20:04 -0500 In-Reply-To: <200403180935440470.461A17AA@coolarrow.com> Message-ID: <44fzc66saz.fsf@be-well.ilk.org> Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org Subject: Re: cdrom mount problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 16:20:07 -0000 "Chris" writes: > *This message was transferred with a trial version of CommuniGate(tm) Pro* > > > > > In summary: the only way to mount my cdrom after burning an ISO is to reboot first. > > > Prior to 5.2.1-RC1, I was able to burn ISO imaged onto a CDRW using burncd, then later mount /cdrom to access the files I burned. With RC1 and now with 5.2.1-RELEASE, a strange thing happens: > > After a reboot, I can mount /cdrom and access files on the disc. But if I re-burn the ISO file, then try to mount /cdrom, I get this: > > cd9660: /dev/acd0: Input/output error > > BUT... if I reboot THEN try to access that same disk, it works fine. Try ejecting and re-loading the disk. I've seen some firmware that gets confused easily in these cases...