From owner-freebsd-geom@FreeBSD.ORG Tue May 17 18:32:11 2005 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A200516A4CE for ; Tue, 17 May 2005 18:32:11 +0000 (GMT) Received: from mx.seanet.com (mx.seanet.com [199.181.164.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A0F943D2F for ; Tue, 17 May 2005 18:32:11 +0000 (GMT) (envelope-from lapo@seanet.com) Received: from [199.181.168.92] (wallace.osd.com [199.181.168.92]) by milkyway.seanet.com (8.13.2/8.13.2) with ESMTP id j4HIW6tV046313 for ; Tue, 17 May 2005 11:32:06 -0700 (PDT) (envelope-from lapo@seanet.com) Mime-Version: 1.0 (Apple Message framework v728) In-Reply-To: <428A1559.8060600@gaiahost.coop> References: <4289DC41.5020105@gaiahost.coop> <23D17D53-2F04-4E4F-BE7E-643FB3CFD263@seanet.com> <428A1559.8060600@gaiahost.coop> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Lapo Nustrini Date: Tue, 17 May 2005 11:32:26 -0700 To: freebsd-geom@freebsd.org X-Mailer: Apple Mail (2.728) Subject: Re: gmirror load problem on startup X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 May 2005 18:32:11 -0000 On May 17, 2005, at 9:01 AM, Mark Bucciarelli wrote: > >> The following entry into /boot.config did not work as advertised: >> 2:da(1,a)/boot/loader >> > > Are you sure you put this on the root partition on da0s1a and not > the mirrored root partition? > Well, what do you know... Although I did have the correct entry in da0s1a, this is not the first drive the system looks at when booting. The system I'm working on has a fiber channel external raid which once booted, FreeBSD sees as device da2. The BIOS however sees it as drive 0. Consequently, as da2 still contained an old slice with a bootable partition (da2s1a), all the changes I made to /boot.config on da0s1a were not being read and the boot process was being started from da2s1a, which told the system to mount da0s1a as root. Once I straightened everything out and started from scratch, things seem to be working as expected. Thanks for the help, and apologies for the 'noise'. Lapo