From owner-freebsd-stable Tue Feb 18 5:15:29 2003 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 F26E437B401 for ; Tue, 18 Feb 2003 05:15:27 -0800 (PST) Received: from HAL9000.homeunix.com (12-233-57-224.client.attbi.com [12.233.57.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24F9443FA3 for ; Tue, 18 Feb 2003 05:15:27 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id h1IDFGQb078057; Tue, 18 Feb 2003 05:15:16 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id h1IDFFqn078056; Tue, 18 Feb 2003 05:15:15 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 18 Feb 2003 05:15:15 -0800 From: David Schultz To: Tim Bishop Cc: freebsd-stable@FreeBSD.ORG, T.D.Bishop@ukc.ac.uk Subject: Re: FreeBSD Boot Manager rendering disk un-bootable Message-ID: <20030218131515.GA77992@HAL9000.homeunix.com> Mail-Followup-To: Tim Bishop , freebsd-stable@FreeBSD.ORG, T.D.Bishop@ukc.ac.uk References: <20030218105616.GA569@raq15.uk2net.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030218105616.GA569@raq15.uk2net.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Tim Bishop : > I'm testing vinum on FreeBSD 4.7 in preparation for building a > server. However, I seem to have come across a problem with the Boot > Manager. > > During installation I selected both disks to be entirely FreeBSD, and > both to have the FreeBSD Boot Manager. This all worked fine. > > At boot time I got presented with two options; "FreeBSD" and "Drive > 1". Selecting "FreeBSD" booted fine. Next time round I selected "Drive > 1" and got presented with "FreeBSD" and "Drive 0". I selected "FreeBSD" > and again it booted fine. All going well so far. > > Then I tried to boot up normally off the first drive and got told "Not > found any [active partition] in HDD", followed by "DISK BOOT FAILURE, > INSERT SYSTEM DISK AND PRESS ENTER". At this point I figured maybe it > was a disk failure, and this gave me an opportunity to test vinum. BootEasy is a very simple 512-byte boot manager. It expects to be loaded from the BIOS boot device; there's no room to add sanity checks in case someone installs it on something else. What you apparently managed to do is use your boot loader on your first disk to load BootEasy on your second disk. BootEasy then wrote itself, including the partition table for the second disk, back to the first disk. If you rewrite the partition table your disk should be fine. There's already an old PR open about this. I don't think there's much that can be done, other than documenting the caveat better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message