From owner-freebsd-stable@FreeBSD.ORG Tue Dec 7 00:40:37 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 964F2106566B for ; Tue, 7 Dec 2010 00:40:37 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 76C6F8FC16 for ; Tue, 7 Dec 2010 00:40:36 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta10.emeryville.ca.mail.comcast.net with comcast id fpQn1f0011vN32cAA0gc79; Tue, 07 Dec 2010 00:40:36 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta22.emeryville.ca.mail.comcast.net with comcast id g0gb1f0063LrwQ28i0gbmA; Tue, 07 Dec 2010 00:40:36 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 2C8D89B422; Mon, 6 Dec 2010 16:40:35 -0800 (PST) Date: Mon, 6 Dec 2010 16:40:35 -0800 From: Jeremy Chadwick To: Pete French Message-ID: <20101207004035.GA9419@icarus.home.lan> References: <20101206232529.GA8235@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7 installs where FreeBSD 8 wont due to CD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2010 00:40:37 -0000 On Mon, Dec 06, 2010 at 11:52:25PM +0000, Pete French wrote: > > This problem has been reported many times in the past and almost > > certainly has nothing to do with 8.x. Here's a thread about the matter > > where a user states the same as you but about 7.1: > > > > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-10/msg00307.html > > I found that - it appears to be a different problem because.... > > > I would question 1) the burning software you used, and 2) the physical > > media you used. Also try burning the ISO to another disc (even if of > > ....I am not burning a CD or using any physical media. I am booting > directly off the image file using iLO. Hence the stuff in that thread > doesnt apply. It's defintely 8 specific - I can boot an mage > from 7 it works fine, but 8 doesn't. > > I think this is to do with USB now - the machine has a physical > drive as well (acd0) - is it possible that the installer sees > that, but not the USB connected drive ? So it tries that drive > instead, which would produce the error message in question, just > as if there was corrupt physical media [Indeed, the physical drive > may well contain an Audio CD - I have no idea what the guys in the > data centre might have put in it] > > I can't really do this physically - I'm in London and the server is > somewhere in Louisiana, USA. Makes it hard to diagnose things. Oh, I see. Yes, there have been discussions about problems with the iLO stuff and the USB "stuff" on FreeBSD. acd0 = ATA-based ATAPI, e.g. a CD drive connected to an ATA port cd0 = SCSI-based CD via CAM, e.g. a CD drive connected to a SCSI port USB on FreeBSD makes use of CAM, not ATA, which means a USB-based CD should be showing up as cd0 not acd0. If there is a physical CD-ROM drive which is upsetting sysinstall, I wouldn't be surprised (sysinstall is depressing, please don't get me started on it. :-) ). I'm willing to bet it makes the assumption there's only one CD device in the system. My recommendation? At the loader prompt, try disabling the ATA port that acd0 is associated with. E.g. if acd0 is tied to ata1-slave, then at loader do: set hint.ata.1.disabled="1" boot If the system in question has an IDE/ATA disk as ataX-master and the CD-ROM drive as ataX-slave, then your best choice would be to disable the Slave portion in your system BIOS and see if that improves things. (I do not know if you can do something like hint.acd.0.disabled="1"; so I'm assuming you can't). I know you can change the BIOS settings remotely via iLO. Hope this gives you some ideas or things to try. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |