From owner-freebsd-current@FreeBSD.ORG Tue Aug 3 18:47:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A74E016A4CE for ; Tue, 3 Aug 2004 18:47:20 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79A8243D62 for ; Tue, 3 Aug 2004 18:47:20 +0000 (GMT) (envelope-from jdc@pentarou.parodius.com) Received: from pentarou.parodius.com (jdc@localhost [127.0.0.1]) by mail.parodius.com (8.12.11/8.12.11) with ESMTP id i73IlJR9009501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 3 Aug 2004 11:47:20 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i73IlJXu009500 for current@freebsd.org; Tue, 3 Aug 2004 11:47:19 -0700 (PDT) (envelope-from jdc) Date: Tue, 3 Aug 2004 11:47:19 -0700 From: Jeremy Chadwick To: current@freebsd.org Message-ID: <20040803184719.GA8970@parodius.com> Mail-Followup-To: current@freebsd.org References: <20040803180307.85535.qmail@web50707.mail.yahoo.com> <20040803112008.Q15648@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040803112008.Q15648@carver.gumbysoft.com> User-Agent: Mutt/1.5.6i Subject: Re: fyi: snap from 080304 will not boot 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, 03 Aug 2004 18:47:20 -0000 Applicable threads about this problem: http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032802.html http://lists.freebsd.org/pipermail/freebsd-current/2004-July/032889.html http://lists.freebsd.org/pipermail/freebsd-current/2004-August/033007.html I believe there to still be a problem with boot1/2 which *wasn't* taken care of in the committed fix. Seems to depend on the system though... A workaround is to pull the bootstraps off of a 5.2.1-RELEASE machine and use those. For those who don't have access to older straps, I've put 5.2.1-RELEASE's /boot/boot up here: http://jdc.parodius.com/freebsd_bootstraps/ You'll want to download the applicable strap and apply it such (assuming disk ad0 and slice s1): # disklabel -B -b /tmp/5.2.1-RELEASE__boot ad0s1 The boot0 strap seems to work; boot1 or boot2 seems to be the problem. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. | On Tue, Aug 03, 2004 at 11:21:54AM -0700, Doug White wrote: > On Tue, 3 Aug 2004, Kim Culhan wrote: > > > > > Greetings- > > > > Just an fyi here.. The latest snap, 080304, from > > snapshots.se.FreeBSD.org did not install a bootable system here. > > This looks like the boot2 breakage. I think a fix was committed not too > long ago and its possible the snapshot server hadn't picked it up in time. > You might try tomorrow's. > > > Hitting enter or letting it time-out at: > > > > F1 FreeBSD > > > > returns > > > > invalid partition > > no /boot/loader > > > > FreeBSD/i386 boot > > default: 0:ad(0,c)/kernel > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"