From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 26 22:46:50 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D343106564A for ; Wed, 26 Nov 2008 22:46:50 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from arcturus.maxiscale.com (arcturus.maxiscale.com [76.231.178.136]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD658FC16 for ; Wed, 26 Nov 2008 22:46:50 +0000 (UTC) (envelope-from psteele@maxiscale.com) X-ASG-Debug-ID: 1227739606-30b500000000-P5m3U7 X-Barracuda-URL: http://10.100.1.25:8000/cgi-bin/mark.cgi Received: from polaris.maxiscale.com (localhost [127.0.0.1]) by arcturus.maxiscale.com (Spam Firewall) with ESMTP id 8AB45310B4 for ; Wed, 26 Nov 2008 14:46:46 -0800 (PST) Received: from polaris.maxiscale.com (polaris.maxiscale.com [10.100.1.24]) by arcturus.maxiscale.com with ESMTP id SP84DjIE4Oe2TKIU for ; Wed, 26 Nov 2008 14:46:46 -0800 (PST) X-ASG-Whitelist: Client X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-ASG-Orig-Subj: RE: FreeBSD boot menu is missing MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 26 Nov 2008 14:46:44 -0800 Message-ID: <2ACA3DE8F9758A48B8BE2C7A847F91F240CE99@polaris.maxiscale.com> In-Reply-To: <20081126153510.6062cd55@bhuda.mired.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: FreeBSD boot menu is missing Thread-Index: AclQBrHcdieaNHa0Sy6ujKbDjzqPNQAAjwkg References: <2ACA3DE8F9758A48B8BE2C7A847F91F240CE6B@polaris.maxiscale.com> <20081126153510.6062cd55@bhuda.mired.org> From: "Peter Steele" To: X-Barracuda-Connect: polaris.maxiscale.com[10.100.1.24] X-Barracuda-Start-Time: 1227739608 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at maxiscale.com Subject: RE: FreeBSD boot menu is missing X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2008 22:46:50 -0000 >The phrase "and copy the file systems over to the mirror" worries >me. Do you actually copy the file systems, or do you let the mirror >system do it for you? In particular, are you mirroring file systems or >the entire disk? Because the boot blocks aren't part of any file >system, so you won't have copied them over, hence you'll be getting >whatever boot software the second drive has installed. I'm more or less using the approach described here: http://people.freebsd.org/~rse/mirror/ This assumes you have an existing OS installed on one drive of a multi-drive system. You then use gmirror to create mirror devices on a second drive to match the partitions of the boot drive, transfer the data to the newly established mirror, adjust /etc/fstab on the mirrored root partition to mount the appropriate mirrored devices, then reboot, telling the boot loader to boot from the mirrored drive instead of the original boot drive (via an entry in boot.config). After it comes up, you can then add the original boot drive to the mirror (and any other drive if there are more than two drives that you want to mirror) using gmirror insert. This all works fine, except I'm not getting the boot menu. I know this isn't part of the mirroring, but it is a step I need to perform as part of the whole process. The question is what do I need to do to make sure the appropriate boot loader is setup? >My recommendation for gmirror is to set up one drive to boot from, >then us gmirror label to create a gmirror device on each partition >(excluding swap). Edit /etc/fstab to use the gmirror devices thus >created, and reboot to make sure it's working properly. It will >initially boot from the disk device (pretty much required until >gmirror is started), then switch to the mirrored root partition. Now >use gmirror insert to add the matching partitions on the second disk, >and let gmirror update the bits on the second drive. You'll need to >copy the boot blocks from the first drive to the second drive by hand >if you want to boot off the second drive. I think you are describing more or less the same process here. >FWIW, these days I use ZFS on 64 bit systems in preference to UFS and >gmirror. We plan to switch our application over to ZFS, but not this close to a release. >Final comment: if you didn't ask on -questions first, this would have >been more appropriate there than here. My bad. I'm new in this arena and didn't know where the appropriate place to post. I'm use -questions in the future.