From owner-freebsd-current@FreeBSD.ORG Tue Jun 1 09:13:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0964A16A4CE; Tue, 1 Jun 2004 09:13:58 -0700 (PDT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.12.11/8.12.11) with ESMTP id i51GDvvk028175; Tue, 1 Jun 2004 12:13:57 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.12.11/8.12.11/Submit) id i51GDrgt028166; Tue, 1 Jun 2004 12:13:53 -0400 (EDT) (envelope-from green) Date: Tue, 1 Jun 2004 12:13:52 -0400 From: Brian Feldman To: Tim Daneliuk Message-ID: <20040601161352.GD26589@green.homeunix.org> References: <40B908E5.5080407@tundraware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40B908E5.5080407@tundraware.com> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Cannot Boot After Buildword X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2004 16:13:58 -0000 On Sat, May 29, 2004 at 05:04:21PM -0500, Tim Daneliuk wrote: > I have installed 5.2.1 on a couple of different machines - a PIII 1Ghz > on a Tyan MB and a Dell PowerEdge 1300 w/Dual PIII 600Mhz - and have > noted the following problem: > > The initial installation is fine. > > A subsequent custom kernel build works fine. > > However, cvsuping the -current sources and the doing a build/installworld > causes the machine to no longer boot. The loader reports that it cannnot > find / and thus cannot find kernel or kernel.old. The uniprocessor > machine is running a vanilla IDE disk. The Dell is running a Mylex 960 > SCSI system configured as RAID 3. The Dell is known to work properly with > 4.10 and the uniprocessor machine runs Win2K, FreeBSD 4.10, Darwin, and > Mandrake 9 just fine ... so I don't think this is a hardware thing. > > Anyone have any ideas on what might be causing this? It sounds like it would probably be a bug in either /etc/fstab, Mylex, or GEOM. When you get the prompt that / could not be found, can you list what devices it was able to find, and hopefully include the working/broken dmesg? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\