From owner-freebsd-stable@FreeBSD.ORG Sun Jan 11 20:21:40 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A28916A4CE; Sun, 11 Jan 2004 20:21:40 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31E8943D1F; Sun, 11 Jan 2004 20:21:38 -0800 (PST) (envelope-from kblists@comcast.net) Received: from [192.168.50.54] (h00045a2a945a.ne.client2.attbi.com[66.31.245.154]) by comcast.net (sccrmhc12) with SMTP id <20040112042137012006hdbie>; Mon, 12 Jan 2004 04:21:37 +0000 From: Kevin Berrien To: freebsd-stable@freebsd.org Content-Type: text/plain Organization: Message-Id: <1523970523.1062.6.camel@linuxppc> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-1b) Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Install bug - 4.9 stable - post install circular reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kblists@comcast.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Mon, 12 Jan 2004 04:21:40 -0000 X-Original-Date: 17 Apr 2018 09:10:14 -0400 X-List-Received-Date: Mon, 12 Jan 2004 04:21:40 -0000 I can confirm an issue posted Dec 3rd, freebsd-stable maillist, titled "4.9 install buglet". I experience this bug running the install (various configurations) 100% of the time. After install, after system reboot, the boot loader comes up with F1: FreeBSD, and reboots continually forever. To test, I made 3 installs without issue using 4.8. So first, I'd like to confirm the bug report, and ask the following. In his "buglet" post, Ian noted the following work around. > Work around. Force write in label screen (or rewrite MBR > and label post reboot) Looking at fdisk, and the label utility I see nothing option along these lines. Could someone explain to me what/how to do this? Has anyone else seen this apparently prevalent issue? Is a fix likely, or do these kind of things just slip by? I did not expect this from a 'stable' release. Unfortunately, I'm making my second attempt at evaluating FreeBSD (last time I used an active box - and got frustrated with bad ports, MySQL/BSD issues, and needed to get the box online, so I installed something that worked). I'm interested in BSD's lean-ness, and other aspects, as opposed to other "nix'es". Needless to say, testing again using 4.9 this time hasn't been very impressive.