From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 21:28:55 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 01A8816A4CF for ; Fri, 30 Jul 2004 21:28:55 +0000 (GMT) Received: from mail.parodius.com (mail.parodius.com [64.62.145.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFF9C43D6B for ; Fri, 30 Jul 2004 21:28:54 +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 i6ULShCs034103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 30 Jul 2004 14:28:43 -0700 (PDT) (envelope-from jdc@pentarou.parodius.com) Received: (from jdc@localhost) by pentarou.parodius.com (8.12.11/8.12.11/Submit) id i6ULShjr034102 for freebsd-current@freebsd.org; Fri, 30 Jul 2004 14:28:43 -0700 (PDT) (envelope-from jdc) Date: Fri, 30 Jul 2004 14:28:43 -0700 From: Jeremy Chadwick To: freebsd-current@freebsd.org Message-ID: <20040730212843.GA33955@parodius.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: boot2 -- Round 2 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: Fri, 30 Jul 2004 21:28:55 -0000 So, in regards to the commited fix: This seemed to fix the issue on one of my boxes (the one which was flat-out panic'ing, not the one which was reporting 0:ad(0,`) as the default slice to load /boot/loader from). I'll refer to the one which panic'd as "Box A" while the one which is doing the backtick as "Box B". After pulling cvs down last night and rebuilding world+kernel+boot blocks, running disklabel -B ad0s1, all on Box B, I found the machine once again spitting out "Invalid partition", trying to load loader(8) off of 0:ad(0,`) instead of 0:ad(0,a). I double-checked boot2/Makefile to see if -fno-unit-at-a-time was in place -- and it was. I've tried using /boot/boot off of Box A and applying it to Box B using disklabel -B -b /boot/box_b/boot ad0s1 to no avail. It seems almost as if the boot2 code is broken in such a way that it resembles an "off-by-one" error (ASCII 0x60 == `, ASCII 0x61 == a). Why it's picking ` is beyond me... Can someone shed some light as to how I can go about debugging this, as well as mention how I can temporarily work around this? Box B happens to run mysqld, and is suffering from some issues mentioned on freebsd-threads (re: machine randomly hard-locking), so it definitely needs to be able to boot back up on it's own without my intervention. Thanks! -- | 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. |