From owner-freebsd-geom@FreeBSD.ORG Tue May 17 13:57:50 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 077A716A4CE for ; Tue, 17 May 2005 13:57:50 +0000 (GMT) Received: from mx.seanet.com (mx.seanet.com [199.181.164.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DBD143D49 for ; Tue, 17 May 2005 13:57:49 +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 j4HDv5gd005451 for ; Tue, 17 May 2005 06:57:41 -0700 (PDT) (envelope-from lapo@seanet.com) Mime-Version: 1.0 (Apple Message framework v728) In-Reply-To: <4289DC41.5020105@gaiahost.coop> References: <4289DC41.5020105@gaiahost.coop> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <623D750C-7437-4AB1-BCB6-051E44E42CC1@seanet.com> Content-Transfer-Encoding: 7bit From: Lapo Nustrini Date: Tue, 17 May 2005 06:58:01 -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 13:57:50 -0000 On May 17, 2005, at 4:57 AM, Mark Bucciarelli wrote: > Lapo Nustrini wrote: > > > >> May 16 15:58:19 kernel: Mounting root from ufs:/dev/da0s1a >> May 16 15:58:19 kernel: GEOM_MIRROR: Device gm0 created >> (id=2862162848). >> >> > > Figure out why it is mounting root from da0s1a. > > That is the problem. I don't understand why it is mounting root from da0s1a, when /etc/ fstab is telling the system to mount it from mirror/gm0s1a > > >> Am I missing something obvious? Any ideas? >> >> > > At which step in the howto was this--the first reboot? If so, what > are the contents of /boot.config? > > I originally tried to follow the how-to to the letter, but I was unable to make the system re-boot automatically onto the second disk after setting up first mirror device. The following entry into /boot.config did not work as advertised: 2:da(1,a)/boot/loader (I can put pretty much anything in the boot.config file. The system seems to just ignore it.) To proceed with the how-to, since booting from the second device is only needed during configuration, I typed the same entry manually on the console during the boot process. This successfully booted from the second drive, so that I could add da0 to the mirror and let gmirror synch it up automatically. > And if it is the first reboot, why is da0 already in the mirror array? > > Its not. This is on any reboot after both drives were added to the mirror. The mirror worked predictably as soon as da0 was synched up after being added to gm0. This issue occurs only on subsequent reboots. In fact, if I manually force the system to boot from da1 by entering "2:da(1,a)/boot/loader" on the console, all partitions are mounted from gm0, but the mirror device only includes da0, not da1... > If it's not the first reboot, then you should have succesfully > mounted root from gm0s1a before. > > The only time I was able to have all partitions in the mirror mounted was when I added da0 to the mirror after booting manually from gm0 with only da1 in the mirror. This is the problem as I see it. The system is mounting root from da0s1a instead of gm0s1a. Why this happens is beyond me... My suspicion is that the GEOM_MIRROR module is not loaded early enough in the boot process when the boot loader is read from da0s1a, but I don't know enough to be able to check this... > Regards, > > Mark > > Thanks for the response. Any other ideas? Regards, Lapo