From owner-freebsd-stable Tue Feb 18 2:56:21 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 3215F37B401 for ; Tue, 18 Feb 2003 02:56:20 -0800 (PST) Received: from raq15.uk2net.com (raq15.uk2net.com [212.4.208.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6025243F75 for ; Tue, 18 Feb 2003 02:56:19 -0800 (PST) (envelope-from bshnt-tim-ml@raq15.uk2net.com) Received: (from bshnt-tim-ml@localhost) by raq15.uk2net.com (8.9.3/8.9.3) id KAA04666; Tue, 18 Feb 2003 10:56:16 GMT Date: Tue, 18 Feb 2003 10:56:16 +0000 From: Tim Bishop To: freebsd-stable@freebsd.org Cc: T.D.Bishop@ukc.ac.uk Subject: FreeBSD Boot Manager rendering disk un-bootable Message-ID: <20030218105616.GA569@raq15.uk2net.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i 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 Hi, 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. So I swapped the two disks over inside the machine. This booted up fine on what was now Drive 0 (the old Drive 1). A while later and after a few more attempts to boot the dead disk I noticed that the Boot Manager would let me select the supposedly dead "Drive 1". So I did, and then picked "FreeBSD". The dead disk booted fine, which seemed a little odd. It then came as a slight shock that the current Drive 0 was rendered unbootable just like the current Drive 1 was before they were swapped over. So, I swapped them back to how they originally were and Drive 0 (the original Drive 0) booted. Follow the same procedure again and we're back in the same state with Drive 0 not booting. So, to summarise. Boot from Drive 0, select Drive 1 and pick FreeBSD off Drive 1. This renders Drive 0 unbootable, and seemingly fixes Drive 1 if it was previously unbootable. Have I found a bug? Or is there something else going wrong here? I couldn't see anything obviously related in the PR database. Cheers, Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message