Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 May 2005 11:32:26 -0700
From:      Lapo Nustrini <lapo@seanet.com>
To:        freebsd-geom@freebsd.org
Subject:   Re: gmirror load problem on startup
Message-ID:  <ECF00BC5-5836-42C5-822B-8B7BB16A61AD@seanet.com>
In-Reply-To: <428A1559.8060600@gaiahost.coop>
References:  <F808F590-C71C-4A90-8876-435E927DEBD3@seanet.com> <4289DC41.5020105@gaiahost.coop> <23D17D53-2F04-4E4F-BE7E-643FB3CFD263@seanet.com> <428A1559.8060600@gaiahost.coop>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ECF00BC5-5836-42C5-822B-8B7BB16A61AD>