From owner-freebsd-stable@FreeBSD.ORG Tue Feb 2 22:09:40 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 8914D106568B for ; Tue, 2 Feb 2010 22:09:40 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta05.emeryville.ca.mail.comcast.net (qmta05.emeryville.ca.mail.comcast.net [76.96.30.48]) by mx1.freebsd.org (Postfix) with ESMTP id 7132C8FC12 for ; Tue, 2 Feb 2010 22:09:40 +0000 (UTC) Received: from omta01.emeryville.ca.mail.comcast.net ([76.96.30.11]) by qmta05.emeryville.ca.mail.comcast.net with comcast id d4Ey1d0080EPchoA5A9h6W; Tue, 02 Feb 2010 22:09:41 +0000 Received: from koitsu.dyndns.org ([98.248.46.159]) by omta01.emeryville.ca.mail.comcast.net with comcast id dA9g1d0033S48mS8MA9gRi; Tue, 02 Feb 2010 22:09:40 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E96E21E3033; Tue, 2 Feb 2010 14:09:38 -0800 (PST) Date: Tue, 2 Feb 2010 14:09:38 -0800 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Message-ID: <20100202220938.GA81464@icarus.home.lan> References: <20100202213148.9A87B1CC3F@ptavv.es.net> <4B689FF3.5080104@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B689FF3.5080104@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: 8.0 install fails to create filesystem ("unable to find device node") 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, 02 Feb 2010 22:09:40 -0000 On Tue, Feb 02, 2010 at 11:58:11PM +0200, Vitaly Magerya wrote: > Kevin Oberman wrote: > >> The setup tries to create filesystem and fails with this message: > >> > >> Unable to find device node for /dev/ad0s1b in /dev! > > > > Are you doing a 'W'rite in the labeling tools? I'm guess that you are > > not, but I wanted to be sure. You don't want to. > > Nope, no write. > > > You say that you are doing the default partitions. If so, the 'b' > > partition should be swap. It should not get 'newfs'ed. No file system > > needed (or wanted) there. This tells me that something was wrong in the > > partition setup if it THINKS that there is a need to newfs partition > > 'b'. > > Yes, ad0s1b is the swap, but I think it fails before doing newfs. > "Writing partition information to ad0" is the last message I see before > the error occurs, no newfs popups occur. > > >> Aside from debug messages, there's this on second VT: > >> > >> GEOM: ad0: geometry does not match label (255h,63s != 16h,63s). > > > > This is a known issue, but cosmetic in almost all cases. > > OK, good. > > > I suspect that you are doing something wrong, but it's hard to figure > > out just what it might be. > > Anything I can do to see what's the problem? Can you get this disk into a system (or the same system if booting off CD, etc.) where you can do the following to it and then retry the installation? dd if=/dev/zero of=/dev/ad0 bs=64k count=1 No, this isn't a joke. This should also clear up the GEOM label error/warning you see. -- | 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 |