Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 8 Oct 2009 21:41:05 -0600
From:      Tim Judd <tajudd@gmail.com>
To:        David LeCount <snailboy1@yahoo.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Trouble getting new raid array to boot
Message-ID:  <ade45ae90910082041i5a3d8ff1j7dd2ac295bfed28a@mail.gmail.com>
In-Reply-To: <362967.59148.qm@web57007.mail.re3.yahoo.com>
References:  <ade45ae90910081950v55d04e85p63dd6a4adc4b8624@mail.gmail.com> <362967.59148.qm@web57007.mail.re3.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/8/09, David LeCount <snailboy1@yahoo.com> wrote:
>> Is the aac driver in the kernel, or loaded as a kld before
>> you get
>> past the boot blocks, and loader?
>
> It's built into the kernel.

Then my answer would be missing MBR or boot blocks, an active
partition alone won't make a system boot.  it's just a flag to say
which partition is bootable, but doesn't mean that the boot flag
itself makes the partition boot.


fdisk(8) and bsdlabel(8) -- see the -B option to both.


If you have a dangerously dedicated disk, ignore fdisk.  If you don't
have a bsdlabel, ignore bsdlabel.

I do both on any standard install.


--TJ



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ade45ae90910082041i5a3d8ff1j7dd2ac295bfed28a>