From owner-freebsd-current Wed Nov 14 8:12:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id C64F537B418 for ; Wed, 14 Nov 2001 08:12:53 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id fAEGCkD33115; Wed, 14 Nov 2001 08:12:46 -0800 (PST) (envelope-from david) Date: Wed, 14 Nov 2001 08:12:46 -0800 (PST) From: David Wolfskill Message-Id: <200111141612.fAEGCkD33115@bunrab.catwhisker.org> To: stephanb@whacky.net Subject: Re: bootloader / assert() failed Cc: current@freebsd.org In-Reply-To: <20011114162600.A75716@enigma.whacky.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Wed, 14 Nov 2001 16:26:00 +0100 >From: Stephan van Beerschoten >I just recently did a `make world` with the cvs source as of 8:00 CET and I tried to boot from it. > .. unfortunately this update rendered my machine unbootable. >I have a multiboot machine with Windows98, and as soon as I choose to boot FreeBSD (F3 for me) it starts the loader and then it fails with an assert error. For the system that you used to build -CURRENT, what was the date of the sources? (For example, when was the *previous* (successful) build of -CURRENT?) I suspect it's yet another manifestation of the awk problems that have been popping up on -current since near the end of October. >I haven't yet been able to write down the exact errormessage, but I wanted to warn people upfront for this possible break in current. I wonder by the way what the correct recovery procedure is for a corrupted loader. * Mount the file system from which you intend to boot on some machine, read/write. * cd to the boot directory of that file system. * [optional] rename "loader" to something else [in case you want to analyze it, for example]. * Rename "loader.old" to "loader". Put the hardware back in order as necessary, then re-boot. Since you built the system recently, GNU awk is back in /usr/bin/awk, so you should not have a recurrence of this particular problem next time you build the system. Cheers, david -- David H. Wolfskill david@catwhisker.org As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message